Service Level Agreement (SLA)
A service level agreement is a documented commitment to deliver a service to a measurable standard. It states what will be delivered, how quickly, how it is measured, and what happens if the standard is missed.
SLAs exist between a provider and a customer (contractual), and internally between teams (operational). Both work the same way; only the consequence differs.
What an SLA specifies
- Response time — how quickly a customer gets a first substantive reply. The most commonly committed metric and the easiest to meet without actually helping.
- Resolution time — how quickly the issue is finished. Harder, more meaningful, usually banded by severity.
- Availability — uptime for a system or service, expressed as a percentage.
- Operating hours — whether the clock runs overnight, at weekends and on public holidays. A "4-hour response" means very different things with and without this.
- Severity definitions — what counts as critical versus routine, agreed in advance rather than argued at the time.
- Measurement method — who measures, from what system, and how disputes about the measurement are settled.
- Remedies — service credits, escalation rights or termination triggers on breach.
Response time is not resolution time
The distinction matters more than anything else in an SLA. An organisation can meet a one-hour response SLA perfectly by auto-acknowledging every case, while resolution drifts for weeks. Customers experience resolution; dashboards often report response.
A well-built SLA commits to both, with resolution banded by severity, and reports them separately.
Severity banding
A single resolution target across all issues is either unachievable for complex cases or trivially loose for simple ones. The usual structure:
| Severity | Typical meaning | Target |
|---|---|---|
| Critical | Service unusable, money at risk, many customers affected | Tightest |
| High | Significant impairment, workaround exists | Tight |
| Medium | Limited impact | Standard |
| Low | Cosmetic, enquiry, request | Loosest |
The arguments come from severity being assigned by whoever opened the case. Defining severity by observable criteria, not by how urgent it felt, removes most of that.
In regulated Nigerian sectors
Financial services operate against supervisory expectations for complaint handling timelines as well as contractual SLAs, and the two are not the same obligation. A bank can be within its own SLA and outside what its regulator expects.
Where that applies, the practical requirement is evidence: being able to show, per case, when it arrived, when it was acknowledged, when it was resolved, and what happened in between — not an aggregate percentage.
Avant One℠ CX tracks response and resolution clocks per case with severity and channel on the record, so SLA performance can be evidenced case by case rather than asserted in aggregate.
Frequently asked questions
What does SLA stand for?
Service Level Agreement.
What is the difference between response time and resolution time?
Response time is how quickly the customer hears back substantively. Resolution time is how quickly the issue is actually finished. Meeting the first says little about the second.
What is an SLA breach?
Failure to meet a committed standard. The agreement should state the consequence — commonly service credits, escalation rights, or termination triggers for repeated breaches.
Do SLA clocks run outside business hours?
Only if the agreement says so. Operating hours, weekends and public holidays should be stated explicitly, because they change what the commitment actually means.