Responsibilities
Clear ownership,
before onboarding.
The proposed scope separates platform maintenance from application work. Any service requires an agreed responsibility schedule.
Platform work to agree
- Supported OS, runtime and database-engine lifecycle.
- Web-service configuration and platform fault handling.
- Certificate lifecycle for hosted websites.
- Recovery scope and agency communication.
Your agency
- Code, content, plugins, themes and integrations.
- Application changes and functional checks.
- Domain ownership and agreed DNS changes.
- An application owner, substitute and client communication.
Explicit exclusions
Application, plugin, theme, content and database-query work would remain with the agency. Mailboxes and transactional email, domain registration and customer DNS administration are outside this candidate. The domain owner would apply agreed DNS records; Novasean would supply the required values if a service were agreed.
Onboarding and incident handover
Before onboarding, both sides would inventory each site, versions, defects, licences and resource needs, then agree migration scope, cutover, rollback and agency acceptance. In an incident, Novasean would need an assigned owner for platform triage and agency communication; the agency owner would diagnose and validate the application and communicate with end clients. Ambiguous faults require a joint handover rather than an unowned gap. No direct end-client helpdesk is included.
Review the proposed service scope and admission checks
This enquiry route offers no hosting package, support schedule, response time, backup retention, recovery objective or SLA. Existing customer entitlements remain governed by their effective agreements.
Do not send patient information, medical records, credentials or payment details. This applies to enquiry replies and attachments as well as the proposed workload. If the answer is Yes or Unsure, stop before submitting.