Service level agreement
A written promise about how fast and how reliably you will respond — a boundary as much as a commitment.
A service level agreement is a written statement of the service you will provide in measurable terms: response within four business hours, resolution within two days, availability of 99.5%. It usually names what happens if you miss.
Most operators read it as a commitment they are taking on, which is half the picture. It is equally a boundary. Without one, the expectation defaults to whatever the client imagines, and what a client imagines is immediate — so every unanswered hour is a small failure against a standard nobody agreed. A stated four-hour response converts an anxious client into a patient one, at no operational cost, because the anxiety came from not knowing.
The rule for setting one is to promise what you can hit on your worst week, not your average. An SLA you breach twice a year is worse than a slower one you never breach: the first teaches clients to chase you, and chasing costs you more hours than the faster promise ever saved.
Worked: a practice with no stated response time fields four "any update?" emails per project, each costing 15 minutes plus the interruption. Publishing a next-business-day response removes most of them — roughly two hours a week returned, in exchange for a promise the practice was already meeting.
Also known as
- SLA
- service levels
- response times
Relevant for
- Founders
- It is a boundary before it is a promise: with no stated response time, the expectation defaults to immediate and you fail against it silently every day.
- Business owners
- Promise what you can hit in your worst week — an SLA you breach twice a year teaches clients to chase you, and chasing costs more than the faster promise saved.