Customer support SLA: targets, examples and how the clock works
A support SLA is a promise of how fast you reply and resolve. Set three targets, count in business hours, and pause the clock while you wait on the customer.
By Andreas Du Rietz, founder of Replyful ·
The three targets
- First response. How long until the customer hears back.
- Next response. How long each later customer message waits for an answer. Teams often skip this one, and it's where long threads go quiet.
- Resolution. How long until the case is solved.
Example targets
Starting points, not benchmarks. Tighten them for customers who pay for it.
- Standard. First response in 8 business hours, resolution in 5 business days.
- Priority. First response in 2 business hours, next response in 4, resolution in 2 business days.
- Urgent, such as an outage. First response in 1 hour, around the clock.
How the clock counts
Fri 16:00–17:00
Clock runs1 of 4 hours
Fri 17:00–Mon 09:00
Closed for the weekendPaused
Mon 09:00–10:00
Clock runs2 of 4 hours
Mon 10:00–11:00
Waiting for the customer's answerPaused
Mon 11:00–13:00
Clock runs until it's due4 of 4 hours
- Count business hours, with holidays. On a 24/7 clock, every Friday-afternoon ticket breaches over the weekend.
- Pause while you wait on the customer. You can't be late with an answer that depends on theirs.
Set it per customer, not per agent
In B2B, customers pay for different promises. Attach the SLA to the customer account so every ticket from that account gets its targets, whoever picks it up. Use urgency for the exceptions, like an outage.
Act before the breach
A breach report tells you what already went wrong. Look at cases close to their deadline instead, every morning, and move them up the queue.
How Replyful does it
Replyful applies SLA policies by customer account, inbox, urgency or tag, and counts and pauses the clock as above. The inbox groups tickets that are due soon, so your team sees them before they breach. SLAs are on the Pro and Enterprise plans.