In short
An SLA (Service Level Agreement) is a promise about how quickly you’ll respond to and resolve support requests. In a helpdesk, SLAs turn that promise into automatic timers, priorities and alerts - so urgent work never quietly slips.
“We’ll get back to you as soon as we can” isn’t a support policy - it’s a hope. An SLA replaces the hope with a number: a first reply within 4 hours, a resolution within 2 business days. That number is what lets a team prioritise fairly, set customer expectations, and actually measure whether support is working.
The definition
A Service Level Agreement is an agreed commitment between a support team and its customers (or between departments) that defines the time targets for handling requests. In customer support, an SLA usually covers two clocks:
First response time vs resolution time
- First response time - how long until a customer gets a first human reply. This is the one customers feel most.
- Resolution time - how long until the issue is actually fixed and the ticket closed.
A good SLA sets both, because a fast reply followed by a week of silence isn’t really good support.
How SLAs work inside a helpdesk
On paper an SLA is just a target. A helpdesk makes it operational by starting a countdown the moment a ticket is logged:
- Priorities. Different targets for different urgencies - a “system down” ticket gets a tighter SLA than a “how do I…” question.
- Business hours. The clock should count your operating hours and holidays, not run overnight when nobody’s working.
- Reminders & breach alerts. The system nudges an agent before a target is missed, and flags it if it is.
- Escalation. If a target is about to be missed, the ticket can be reassigned or raised to a manager automatically - see escalation management for how to structure that.
- Reporting. You can see your SLA compliance rate - the single clearest measure of whether the desk is keeping its promises.
What does SLA mean on a ticket?
When you see an SLA on a ticket, it is the deadline the helpdesk is tracking for that one request: when the first reply is due, and when it should be resolved. Most helpdesks show it as a due time or a countdown, and colour it by state:
- Within target - there is still time on the clock.
- At risk - the deadline is close, and a reminder has usually gone to the agent.
- Breached - the target was missed. The ticket still needs finishing, and the miss counts against your SLA compliance rate.
The clock can also pause, for example while you wait on the customer to reply, so you are not penalised for time outside your control.
SLA examples by priority
If you are setting targets for the first time, a table like this is a reasonable starting point. Adjust it to what your team can actually hit, measured in business hours:
| Priority | Example | First response | Resolution |
|---|---|---|---|
| Urgent | System down for everyone | 30 minutes | 4 hours |
| High | A team cannot work, or a key customer is blocked | 1 hour | 1 business day |
| Medium | Standard request or a single-user problem | 4 hours | 3 business days |
| Low | Questions and minor issues | 1 business day | 5 business days |
How the clock runs on one ticket
Say your team works 9:00 to 17:00, Monday to Friday, and a Medium ticket arrives at 16:30 on a Friday with a 4-hour first-response target. Thirty minutes count on Friday, the clock stops at 17:00, and the remaining three and a half hours count from Monday at 9:00. The reply is due at 12:30 on Monday - not at 20:30 on Friday, when nobody is there. That is why business hours matter: without them, every weekend would show up as a breach.
SLA vs SLO vs OLA
- SLA (service level agreement) - the promise to the customer, such as “first reply within 4 business hours”.
- SLO (service level objective) - an internal goal, often stricter than the SLA, such as “95% of first replies within 3 hours”, so you have headroom before you break the promise.
- OLA (operational level agreement) - an agreement between internal teams, such as engineering responding to support within 2 hours, so the SLA can be met.
SLOs and OLAs are planning terms rather than helpdesk settings. Raiseaticket tracks SLAs - response and resolution targets per priority - and you can use its SLA reports to check yourself against an internal goal.
Ready to set one up? Our SLA management guide walks through creating an SLA policy step by step, with operating hours, holidays, multiple SLAs and pausing the timer.
Why SLAs matter
Three reasons: accountability (work is prioritised by a rule, not by whoever shouts loudest), trust (customers know what to expect and you can be held to it), and measurement (you can’t improve response times you don’t track). For teams with any kind of paying or contractual customer, SLAs aren’t optional - they’re the definition of the service.
Common SLA mistakes
- Targets that are too aggressive. A 15-minute resolution SLA you always breach is worse than an honest 1-day one you keep.
- Ignoring business hours. Counting nights and weekends makes every Monday look like a failure.
- One SLA for everything. Without priorities, a password reset and an outage compete for the same clock.
Start simple: one or two priorities, realistic response and resolution targets, counted against your business hours. You can tighten them once you’re hitting them consistently - which, with the timers doing the watching, you will.