A website maintenance service-level agreement, or SLA, explains what support the client can expect when a website experiences problems. It should distinguish between an alert, the first response, investigation and actual resolution. Without those definitions, a promise such as “24/7 support” can sound stronger than the service delivered.
Response time is not resolution time
Response time measures how quickly a support team acknowledges a ticket or begins triage. Resolution time measures how long it takes to restore service or fix the underlying issue. A third concept, restoration time, can be useful when a temporary workaround brings a critical function back before the final repair.
These clocks should have clear business-hour or after-hours definitions and a named communication channel. “Within four hours” means something different if the support team only works Monday to Friday.
Build severity levels around business impact
- Critical: the site is unavailable or a primary checkout/lead path is unusable.
- High: an important feature fails for many users, but the site is partly operational.
- Normal: a layout defect, individual page error or non-urgent integration issue.
- Low: a cosmetic request or planned content update.
For a law firm dependent on inbound calls, a missing mobile tap-to-call button may be a higher priority than a small visual inconsistency. Classify incidents against revenue, trust and customer impact rather than technical labels alone.
What uptime promises actually mean
Uptime indicates the portion of time a service is reachable during a measurement period. It does not guarantee that forms submit, payments succeed or the site shows accurate content. Ask whether monitoring checks a generic homepage response or also runs functional checks on critical journeys.
An SLA should identify exclusions such as scheduled maintenance, third-party outages and events outside the provider’s control, while still describing how customers will be informed.
Other terms worth negotiating
Specify update frequency, backup retention, restore responsibility, supported plugins, change-request limits and escalation contacts. Request a plain-language monthly report and a documented process for suspected security incidents. A WordPress maintenance checklist turns the agreement into an operational review tool.
What to do before an emergency
Confirm the business owns its domain, hosting and core application accounts. Store access securely, name the person authorized to approve a rollback and establish an alternative contact method if the website or email is down.
Example: how a support SLA should classify a failure
A service firm discovers that its website is online but the main quotation form is broken. A generic uptime monitor reports no outage, yet the business has lost its primary enquiry channel. An effective SLA treats the form failure according to commercial severity, defines when triage begins and explains who can authorize a temporary workaround. By contrast, a small icon alignment defect can wait for a normal maintenance window. The distinction helps the provider allocate time sensibly and keeps expectations realistic.
Frequently asked questions
Does a 99.9% uptime target guarantee leads?
No. Availability percentages measure reachability under defined conditions, not whether forms, phone links or checkout functions successfully create customer enquiries.
What if a third-party provider causes an outage?
The contract should explain exclusions, escalation and communication. Even when the issue is outside the maintainer’s control, the business still needs a clear coordination process.
DigiFly’s ongoing WordPress maintenance service can help define routine care and response responsibilities. The goal is a support agreement that matches the business’s actual risk, rather than an impressive promise with unclear exclusions.
