Service level agreements (SLAs) tell your users and customers how quickly you’ll respond to and resolve their requests. Set them well and they build trust, focus your team on what matters and give you the figures you need to justify resources. Set them badly and they become targets nobody believes in.
Here’s a practical approach to setting SLAs that work.
1. Start with priorities, not promises
Before you set any times, agree how you’ll prioritise requests. A common approach, recommended in ITIL, is to base priority on two things:
- Impact: how many people or how much of the business is affected
- Urgency: how quickly it needs fixing to avoid serious problems
Combine them into a simple matrix, usually four or five priority levels. A server outage affecting everyone is high impact and high urgency. A request for a new mouse is low on both.
2. Set response and resolution times for each priority
For each priority level, set two targets:
- Response time: how quickly someone acknowledges and starts working on the request
- Resolution time: how quickly it’s fixed or the request is completed
Look at your current performance before you commit. Targets you can’t hit will only damage confidence.
3. Measure in working hours
If your team works 9am to 5pm, Monday to Friday, a request logged at 4.55pm on Friday shouldn’t breach its SLA over the weekend. Make sure your SLAs are measured in business hours, and that bank holidays are taken into account.
4. Pause the clock when it’s out of your hands
Sometimes you’re waiting on the user to reply, or on a third-party supplier. Your SLA clock should be able to pause, or “defer”, during those periods, so your figures reflect what your team actually controls.
5. Warn before you breach
The most useful SLA feature isn’t the report at the end of the month, it’s the warning before a target is missed. Set escalation points, for example at 75% of the target time, so team leaders can step in while there’s still time.
6. Use different SLAs for different customers
If you support external customers, they may be on different contracts. Gold, silver and bronze SLA profiles let you offer faster service to customers who pay for it, and prove you’re delivering it.
7. Report honestly and review regularly
Track the percentage of requests resolved within SLA for each priority, team and customer. Share the results. Then review your targets every few months and adjust them as your team and tools improve.
How SiteHelpDesk helps
Every SiteHelpDesk product includes SLA priorities with response and resolve times, escalation warnings, traffic-light flags on open calls and reporting on calls inside and outside SLA. Built-in SLA monitoring also gives you:
- SLA times calculated on your working hours and holidays
- The ability to pause the clock on deferred calls
- Email alerts to operators, teams or managers when a threshold is reached
- Scheduled jobs and reports created automatically
As one customer, Magenta Living, put it: “SLA monitor provides a visual representation of all our jobs which are out of priority time on our SLAs.”
Book a demo to see SLAs in action, or see our pricing.