Launching a website or system is the beginning of operational ownership. Managed support keeps content, security, performance, integrations and growth activity under active review.
Dalmut separates preventive maintenance, support requests, incidents and planned improvements so clients know what is covered, who owns access and how operational work is prioritized.
This guide is educational and commercial planning content. It does not replace legal, financial, security or regulatory advice specific to your organization.
- Define preventive and reactive scope.
- Document access and escalation.
- Monitor backups, updates and performance.
- Review improvement priorities regularly.
Begin with an asset and access inventory
Record domains, hosting, websites, applications, repositories, databases, analytics, advertising accounts, email services, integrations, certificates, licenses and responsible owners. Confirm which credentials are controlled by the business.
Without an inventory, support becomes reactive and dependent on individual memory. Identify expired accounts, unknown vendors, shared passwords and missing backups during onboarding.
Separate maintenance, support, incidents and projects
Maintenance covers scheduled preventive work. Support handles user or content requests. Incidents address unexpected service impact. New features, redesigns and campaigns are planned projects.
Define what is included, available capacity, priority levels, response targets and approval. This protects both the client and delivery team from an unlimited “everything digital” promise.
Manage updates, access and backups as verifiable tasks
Review software dependencies, certificates, server health, user access and logs. Remove access when roles change. Test that backups can be restored rather than assuming a successful notification means recovery is possible.
High-risk findings should be escalated with a clear business explanation, containment recommendation and owner. Security guarantees are not credible; disciplined risk reduction is.
Monitor speed, availability and critical journeys
Track uptime, server resources, errors, Core Web Vitals and third-party failures. Test forms, payments, logins, search and other critical routes after changes.
Performance degradation can come from oversized media, plugins, scripts, campaigns or content changes. Use evidence to locate the cause before adding infrastructure.
Prevent content, SEO and tracking decay
Contact details, services, careers, metadata, schema, internal links, redirects and sitemap records become inaccurate if nobody owns them. Schedule reviews based on business risk.
Monitor search-console coverage, analytics changes and campaign tags. A website can remain online while becoming commercially unreliable.
Use a structured request and escalation route
Requests should include affected asset, business impact, evidence, urgency and requester. The support team classifies priority and communicates status. WhatsApp can be used for alerts, but important work should be recorded in a ticket or approved system.
Emergency priority should be reserved for serious operational impact. Clear classification prevents routine updates from delaying critical incidents.
Report decisions, risks and next priorities
A useful report shows completed work, unresolved issues, incidents, performance signals, content and campaign actions, access changes and recommendations. It should distinguish evidence from opinion.
Review the backlog with business owners and approve the next period. Reporting without a decision meeting often becomes an unread activity list.
What a managed support agreement should state
Include assets, coverage hours, channels, priority definitions, response and resolution approach, included capacity, exclusions, third-party costs, access responsibility, backups, security boundaries, reporting and termination.
Clarify that response time is not always resolution time, especially when a vendor, hosting provider or external platform controls the fix. Define an orderly handover and export process.
Frequently asked questions
Is website maintenance the same as managed support?+
Maintenance is one part. Managed support may also cover incidents, content, SEO, analytics, integrations, campaigns, access and improvement planning.
Should support include unlimited changes?+
Usually no. Capacity, request types and exclusions should be defined. Larger features and redesigns are planned separately.
How often should backups be tested?+
Frequency depends on risk and change rate. Backups should be monitored and restoration tested on a documented schedule.
Can Dalmut support a website built by another supplier?+
Potentially, after an audit of code, hosting, access, licenses, documentation and current risk. Stabilization may be required before ongoing support.
Sources and further reading
External sources support market, policy or technical statements. Commercial recommendations remain Dalmut’s editorial interpretation and should be assessed against your own business data.