The Response Time You Can Promise
Most SLA targets are chosen by someone picking a round number. This works backwards from your actual capacity.
What first response time can you actually promise?
Queues do not degrade smoothly. Past roughly 80% utilisation, waiting times climb sharply, which is why a target set on average load breaks every time volume spikes.
Stop paying for duplicatesWhy targets break at peak, not on average
Queues do not degrade smoothly. At 60% utilisation, tickets are answered almost immediately. At 85%, waiting times climb steeply. At 95%, a queue that looked fine yesterday has a backlog this morning.
That non-linearity is why a target set on your average week fails every time volume spikes, and why the honest question is not "what is our average capacity" but "what can we still hit on the busiest hour of the busiest day".
Filling it in honestly
What to do when the number is worse than your promise
Three levers, in order of how quickly they work.
Also worth remembering: a slow first response manufactures its own extra volume, because people who wait contact you again on another channel. That second contact is a duplicate, and it makes the queue you are already behind on longer.
Frequently asked questions
What is a good first response time?+
Under an hour is strong for business-hours support, under four hours is acceptable in most B2B contexts. Consistency matters more than the number: an occasional eight-hour reply damages trust more than a steady four.
Does an auto-acknowledgement count?+
No. Counting it makes your dashboard disagree with your customers, which is the worst kind of metric.
Why does my utilisation look fine but replies are slow?+
Because averages hide peaks. Check the busiest hour rather than the daily total.
The fastest lever on response time
Cutting duplicate tickets reduces volume immediately, with no new headcount and no change to what customers experience.
Start free trial14-day free trial. No credit card required.