Two support teams get the same ticket. One replies in twenty minutes and tells the customer it'll be fixed by tomorrow. The other goes quiet for a day, then a week. Same fix, wildly different experience — and the difference has a name. It's the SLA: the promise about how fast you respond and resolve, made measurable.
What is an SLA?
A service level agreement (SLA) is a documented promise about your support response — typically how fast you'll first reply and how fast you'll resolve, broken down by how urgent the ticket is. For the customer it sets a clear expectation. For your team it sets a clear target, and a yardstick to see whether you're meeting it.
In one line: an SLA is a measurable promise — how fast you respond, how fast you resolve — that you can hold yourself to.
The anatomy of a support SLA
First-response target
How long the customer waits to hear from a human at all. It's the promise that someone has the ticket — even if the fix takes longer. Usually the tightest target you set.
Resolution target
How long until the issue is actually closed. It's looser than first-response and scales with complexity, but it's the one customers feel most when it slips.
Pause & resume
When you're waiting on the customer for info, the clock should pause — their delay isn't your miss. It resumes the moment the ball is back in your court, so the target measures your team, fairly.
Escalation
When a timer elapses, an action fires — reassign, notify a lead, raise priority — so a slow ticket gets attention before it becomes an angry one.
First-response vs. resolution time
The two targets do different jobs. First-response time is how long the customer waits to hear from a human at all — it's the promise that someone has the ticket, even if the actual fix takes a while. It's usually your tightest target, because silence is what frustrates people most. Resolution time is how long until the issue is actually closed. It's looser and scales with complexity — a password reset and a data migration shouldn't carry the same target — but it's the one customers feel most when it slips. Set both, per priority, so a P1 outage and a P3 question aren't held to the same stopwatch.
Why a fair SLA pauses the clock
Here's the part teams forget: an SLA should measure your responsiveness, not the customer's. If you've asked for a screenshot and they take two days to send it, those two days shouldn't count against your resolution target. A well-run SLA pauses the timer while you're waiting on the customer and resumes it the moment the ball is back in your court. Without pause/resume, your metrics punish your team for the customer's inbox — and people stop trusting the number.
How SLA escalation works
A target is only useful if something happens when you're about to miss it. That's escalation: when a timer elapses, an action fires — reassign the ticket to someone free, notify a team lead, or raise the priority — so a slow ticket gets attention before it becomes an angry one. Escalation is what turns an SLA from a number you review after the fact into a live commitment that protects the customer in real time.
SLAs in KudosCRM
In KudosCRM you set first-response and resolution targets per priority. Timers run automatically and pause when you're waiting on the customer, then resume when you're back on the hook. When a timer elapses, an automated escalation fires so the ticket gets seen. A dedicated “breach” flag is on the roadmap; today, automated escalation is how you stay ahead of a missed target — and because tickets live on the customer record, you see the SLA in the full context of the relationship. See it on the Customer Support stage.