An SLA is written into an agreement, not implied by a website.
Words like coverage, response, and priority get used loosely in marketing copy. Here is what each one actually has to define before it means anything enforceable.
Six terms, defined precisely.
Vague versions of these words are how a marketing claim quietly becomes an unmet expectation. Precise versions are how they become useful contract language.
- Coverage window
- The hours and days a lane is expected to operate, including time zone and any excluded dates.
- Response expectation
- How quickly a request is acknowledged by an authorized person — separate from when it is resolved.
- Resolution expectation
- How quickly a request is completed, which varies by request family and cannot be a single blanket number.
- Priority level
- A named scheme, however many tiers, that decides which requests are worked first when more than one is open.
- Scope boundary
- The request families and conditions that are actually included, with named exclusions rather than an implied "everything."
- Exception class
- Work classified out of the recurring lane at intake and estimated separately, per the escalation matrix.
Why this page will not give you a number.
A defensible response or resolution target depends on the specific client group, request mix, coverage window, and tooling in the written agreement. Publishing one generic number on a marketing page would be either meaningless or misleading — the real target belongs in the agreement for that lane, not a homepage claim.
- Tied to a specific, written scope — not "everything," which cannot honestly carry a single target.
- Different for different request families — not one number applied to all work regardless of complexity.
- Measured against a defined coverage window — not read as always-on by default.
- Reviewed on a cadence — not fixed permanently at the moment of signature.
Who proposes each mechanic, and who approves it.
| Coverage and priority scheme | Delivery proposes, based on the lane; the selling practice approves. |
|---|---|
| Response and resolution targets | Negotiated jointly once the request mix is understood. |
| Exclusions and exception classes | Delivery proposes from the catalog; the selling practice confirms against client expectations. |
| Final SLA language | Written into the agreement — never the website. |
Ask a candidate partner these before trusting a claimed SLA.
- Does the number apply to every request family, or only some?A single blanket number is often a sign it applies to none in practice.
- What coverage window does it assume?Confirm it matches your clients' actual expectations, not a generic default.
- What happens when a target is missed?Look for a defined remedy, not just an apology.
- Is the number reviewed as the lane changes?A fixed number on a changing lane eventually stops meaning anything.
Put real numbers where they belong — in the agreement.
Use the evaluation guide to ask any candidate partner how they actually define these mechanics.