A help desk SLA (service level agreement) is a target for how fast you'll first reply to a ticket and how fast you'll resolve it, set for each priority. The help desk then measures every ticket against that target on a clock, and the clock you pick decides whether your SLA report tells the truth.
When SLAs go wrong, the clock is usually the reason. If yours counts nights and weekends, every ticket that lands late on a Friday shows up as missed, and after a few weeks nobody trusts the report. For how Cayzu does it, see help desk SLAs with business hours.
First reply and resolution are two separate clocks
Every ticket gets two targets, and they measure different things.
The first response target runs from when the ticket arrives to the first reply. It's the promise that a person has read it and is on it.
The resolution target runs until the ticket is solved. It's the promise that the problem goes away.
They need different numbers. A first reply can take two minutes. A fix might need a part shipped, a call to a vendor, or the customer to try something and write back. A team can hit every first response target and still miss its resolution targets, so watch both.
One thing to check in any help desk: does the resolution clock keep running while the ticket waits on the customer? If it does, a customer who takes three days to write back makes you late.
How to set SLA targets by priority
Targets go by priority because not every ticket needs the same speed. A whole office that can't log in can't wait as long as a question about next month's invoice.
Here are suggested starting settings for a small team. They're our suggestion, not an industry benchmark. Change them to fit what you've promised your customers.
Priority First response Resolution Example ticket Urgent 1 business hour 4 business hours Nobody can log in High 4 business hours 1 business day One person can't work Normal 1 business day 3 business days Something's broken, but there's a workaround Low 2 business days 5 business days A question, or a request for later
Suggested starting settings, not benchmarks.
A few things make the table work:
- Start with what you already do. Look at last month's tickets and set each target a little slower than your usual time. It's better to start with a promise you keep and tighten it than to start with one you miss.
- Write down what each priority means, with an example like the last column, so two agents file the same ticket the same way.
- Let a rule set the priority. An assignment rule can mark anything with "down" in the subject as urgent the moment it arrives, and that priority's clock starts on its own.
The priority matters as much as the target. An urgent request filed as normal runs on the normal clock until someone fixes it.
Why business hours change the clock
An SLA clock can count every hour on the calendar, or only the hours you're open. Unless someone's answering at 3am, count business hours.
Here's the difference on one ticket. Your team works Monday to Friday, 9 to 5. A normal ticket arrives at 5pm on Friday. The target is a first reply within eight hours (one business day). An agent replies at 10am on Monday.
- Counted in calendar hours, the reply was due at 1am Saturday. It landed 57 hours late. The report says missed.
- Counted in business hours, the clock didn't start until 9am Monday. The reply used one hour of its eight. The report says met, with seven to spare.
Same ticket, same reply. Only the second one tells the truth about your promise. If your report shows a pile of misses every Monday morning, check the clock before you blame the team.
Holidays work the same way. Say that Monday is a public holiday. With the holiday in your business hours, the clock skips it, and the first reply on that ticket is due at 5pm Tuesday. Leave it out, and that ticket goes red on a day nobody was working. If you run IT for a school, here's how SLAs follow the school calendar.
In Cayzu, you set your working days, hours and time zone once, as a business hours schedule. Add your holidays to the same schedule and the clock skips them. If you never close, turn on Open 24/7/365. Set the time zone to the one your team works in. If it's wrong, every target is off by the same few hours.
Business hours have a catch. An urgent ticket that comes in at 5:01pm on Friday, with a one business hour target, isn't due until 10am Monday. If that's fine for your customers, you're done. If it isn't, you need someone on call, and urgent tickets need a clock that keeps running on weekends. In Cayzu, each priority in an SLA policy can have its own schedule. So Urgent can run around the clock while the others follow business hours.
What happens when a ticket is about to miss its target
A target only helps if someone sees the miss coming. In Cayzu, every ticket shows how long it has until it breaches, and the queue flags tickets that are close to missing. Agents work the queue in the order that matters instead of the order tickets arrived. The agent dashboard has a Coming due tile for what's due next and a Past due tile for what's already late.
When a ticket does go past its target, escalation rules tell someone. You set them for the first reply target and for the resolution target. A rule fires a set time after the breach and notifies the agent you choose. Add more rules and they run in order, each one a set time past the breach.
We'd keep it short. Send the first step to the person who can fix the ticket, and the second to whoever covers for them.
Can different customers get different SLAs?
Sometimes they need to. A client who pays for faster support should get a faster clock than everyone else, and an IT team may promise one department more than another.
In Cayzu, you can do that with more than one SLA policy. Each policy has conditions, a bit like a rule, and a ticket gets the policy whose conditions it matches. A policy can be limited by team, brand, company or when the ticket was created. So one client's company can have its own policy with faster targets, and so can one brand.
SLA policies are on Pro and Enterprise. Brand conditions need more than one brand, and the multi-brand help desk is on Enterprise. On Pro, a policy can still go by team, company or when the ticket was created.
You could get close with priority instead, by having a rule bump one client's tickets up a level. We'd use a policy. The rule bends what a priority means: that client's small questions get a faster clock too, and your numbers for each priority mix their tickets with everyone else's.
The SLA report has a Company column, so you can see which client's tickets are slipping.
How to report on SLAs and when to change the targets
Watch two numbers for each priority: how many tickets got their first reply on time, and how many were solved on time. Cayzu's SLA report shows which tickets met their targets and which missed, and the This week panel on the dashboard counts SLA breaches. The help desk reports page shows how they're laid out. You can filter exports by priority, team and brand, and schedule one to arrive by email every month.
Change a target when the numbers tell you to:
- You beat it every week by a wide margin. Tighten it. A promise you always beat by hours isn't telling customers much.
- You miss it most weeks. Either the target or the staffing is wrong. The help desk load analysis shows when tickets arrive. If the misses stack up at the same hours, fix the shifts before you loosen the target.
- The misses are all one priority. Check that tickets are being filed at the right priority before you touch the number.
We'd look at targets once a quarter, not every week. One slow week is noise. Three slow months is a pattern.
One limit to keep in mind: an SLA measures time, not quality. A fast wrong answer passes. Read some of the tickets behind the numbers too.
When you don't need an SLA yet
If you're one person answering a few tickets a day and everyone gets a reply the same afternoon, you don't need an SLA. You need one when there are enough tickets that some wait, enough people that nobody's sure who's on what, or a customer who asks what you've promised.
SLAs and business hours are on Cayzu's Pro and Enterprise plans. If you'd like to set up a policy and watch the clock on your own tickets, the 15-day free trial has every feature, and no card.