Ask a support manager how the team is performing and you usually get an average. Average first response time, average resolution time, both trending in the right direction, both on a dashboard somebody screenshots for the monthly review. Then a customer escalates over a ticket that sat for two days and nobody can explain how the numbers stayed green.
They stayed green because an average is the wrong instrument. It answers “how fast are we usually” when the commitment you actually made was “no ticket waits longer than this”. Those are different questions, and only one of them is an SLA. This guide covers the help desk SLA metrics worth reporting, the ones that mislead, and the setup decisions that quietly determine whether any of the numbers mean anything.
Why this matters more in 2026
Support teams are under unusual pressure to change how they work. In a Gartner survey of 321 customer service and support leaders, 91% reported executive pressure to implement AI in 2026, with customer satisfaction, operational efficiency, and self-service success named as the top priorities. Gartner has also predicted that agentic AI will autonomously resolve 80% of common customer service issues by 2029.
Whatever you make of the forecast, the practical consequence is immediate. If your support process is about to change, you need a baseline that will still be readable afterwards. A blended average will not do it. Something that deflects easy tickets will improve your average resolution time on day one while your hardest cases carry on breaching, and you will not be able to tell the two effects apart. Compliance measured per priority survives that change. Averages do not.
Set the target before you measure anything
A compliance percentage only exists if there is something to comply with. Before any metric is worth looking at, you need a written target per priority level, and it has to be a target the team agreed to rather than one somebody inferred from last quarter’s performance.
In ISO Mate that lives in an SLA policy. Each policy sets a first response target and a resolution target, in minutes, for every ticket priority: Urgent, High, Medium, and Low. A reasonable starting point looks like this, and you adjust from there rather than treating it as gospel:
- Urgent: first response in 60 minutes, resolution in 240 minutes.
- High: first response in 240 minutes, resolution in 480 minutes.
- Medium: first response in 480 minutes, resolution in 1440 minutes.
- Low: first response in 1440 minutes, resolution in 2880 minutes.
Two rules of thumb. Set targets you can hit on a bad week, not a good one, because a target you breach routinely stops functioning as a signal. And keep the gap between Urgent and Low wide enough to actually change agent behaviour, since four bands that all resolve inside a day is really one band with extra labels.
The clock rules decide the number
This is the part teams skip, and it moves compliance by more than any process improvement you are likely to make this year. The same tickets, the same replies, and two different clock configurations will produce two very different compliance figures. One of them is honest.
Two decisions matter.
Do you count time outside working hours. An ISO Mate SLA policy takes a start time, an end time, a timezone, and the days of the week you operate. With business hours configured, target due times are calculated from working hours only, so a ticket arriving at 9pm starts its clock when you open. Leave business hours empty and the clock runs continuously as plain calendar minutes. Neither is wrong, but if you promise a four hour response and measure it around the clock while staffing one timezone, you are recording failures you never had a chance to prevent.
Do you count time you spent waiting on the customer. A ticket blocked on a customer reply is not a ticket you are failing to work. In ISO Mate the SLA clock pauses when a ticket moves to Pending or On Hold, and resumes when it returns to an active status like Open or In Progress. Paused time is excluded from elapsed response and resolution time. That single behaviour is the difference between a resolution metric that measures your team and one that measures your customers’ email habits.
The mechanics are covered in detail in Configuring SLA Policies. Set one policy as the default so it applies to new tickets automatically, because a ticket with no policy attached is a ticket that can never breach, and a queue full of those flatters every number you report.
The four metrics worth reporting
Support reporting suffers from abundance. Once a tool exposes twenty charts, the temptation is to review all twenty and act on none. Four measures carry most of the signal.
1. First response compliance rate, by priority. The percentage of tickets where the first agent reply landed inside the target. This is your responsiveness commitment expressed as a pass rate, and it is the number to lead with. ISO Mate’s SLA Compliance report breaks it down for each of Urgent, High, Medium, and Low, alongside the ticket count for that priority so you know how much weight each row carries.
2. Resolution compliance rate, by priority. The percentage of tickets resolved before the resolution deadline, reported the same way. Keep it visually next to first response compliance, because the two failing together and one failing alone point at completely different problems. Weak response with strong resolution is a triage and coverage issue. Strong response with weak resolution means the team is acknowledging quickly and then stalling, usually on a dependency outside support. ISO Mate charts response against resolution compliance side by side for exactly this comparison.
3. CSAT, overall and by agent. Speed metrics on their own are trivially gameable. A fast, unhelpful reply satisfies a first response target while making the customer’s day worse. In ISO Mate a satisfaction survey goes to the requester when a ticket is resolved, rated 1 to 5 with an optional comment, and the CSAT report gives you the average score, the distribution across all five ratings, the score per agent, and the trend over time. Read the distribution, not just the average: a 4.2 made of fours is a healthy team, while a 4.2 made of fives and ones is two very different experiences averaged into a comfortable looking number.
4. Current breach exposure. The three metrics above are lagging. They tell you what already happened, which is useful monthly and useless on a Tuesday afternoon. What you need during the week is the count of tickets at risk right now. ISO Mate assigns every ticket an SLA standing of On Track, Breaching, or Breached, and you can filter the ticket list by it. There is a built in SLA Breaching preset, an Urgent Unassigned preset for the worst combination in any queue, and every Kanban card carries its SLA indicator so the board doubles as a risk view.
The metrics that mislead
Some numbers are worth tracking but not worth managing to. Others actively distort behaviour. Both categories tend to end up on dashboards because they are easy to produce.
- Average first response and average resolution time: useful as a trend, dangerous as a target. An average cannot tell you how many customers were failed, and a handful of very slow tickets can hide behind a large volume of quick ones. Track the trend, report the compliance rate. ISO Mate shows both averages on the Overview report, which is the right place for them: context, not scoreboard.
- Tickets closed per agent: reward volume alone and you will get volume, delivered by whoever cherry picks the easy queue. ISO Mate’s Agent Performance report deliberately puts tickets handled, average resolution time, and average CSAT score on the same row, which makes the trade off visible instead of letting throughput stand alone.
- A single blended compliance figure: aggregate compliance is arithmetic, not insight. If 90% of your volume is Low priority and comfortably inside target, an overall 88% can coexist with Urgent tickets breaching every week. Always segment by priority.
- Ticket volume as a performance measure: volume is demand, not output. It belongs in capacity planning. ISO Mate reports volume over time and breakdowns by status, priority, and category, plus volume and average resolution time by channel across Email, Web, Phone, Chat, and Internal, which is genuinely useful for staffing and for spotting a channel that is quietly slower than the rest.
Read the numbers together, not in sequence
Individually these metrics are ambiguous. In combination they usually name the problem outright.
- High compliance, low CSAT: you are hitting the clock and missing the point. Replies are arriving on time without resolving anything. Look at the CSAT comments and at how often resolved tickets come back.
- Low compliance on Urgent only: usually a routing problem rather than a capacity problem. Urgent tickets are landing in the general queue and waiting their turn. Auto-assignment rules with round robin rotation or category based routing address this before the clock does.
- Compliance that collapses on specific days: a coverage gap. Compare against your configured business days and the volume trend before concluding the team is underperforming.
- Strong averages, weak compliance: the classic long tail. Most tickets are fast and a minority are abandoned. This is the pattern averages exist to hide, and the one customers remember.
Resolved tickets that come back deserve a specific look. In ISO Mate a reply from the requester portal reopens a Pending or Resolved ticket to Open automatically, and the audit log records every status change on the ticket, so a case that was closed prematurely leaves a visible trail rather than disappearing into the resolved count.
Make the leading indicators reach people
A monthly report changes next month. Breach exposure has to reach an agent while the ticket is still recoverable, which means the signal cannot live only in a reporting tab.
ISO Mate pushes it in three places. Agents receive notifications for SLA breach warnings alongside assignments, new replies, and status changes, and each user can tune their preferences under the Help Desk notification category. The dashboard has a Help Desk Overview widget with SLA breach tracking, so the risk sits on the screen people already open. And the ticket list presets put SLA Breaching and Urgent Unassigned one click away, which is the difference between a check somebody remembers to run and one they actually do.
What ISO Mate reports out of the box
Everything above runs on the standard ISO Mate Help Desk reporting, reachable from the Reports group in the sidebar and filtered by date range across six views:
- Overview: total tickets, open tickets, average resolution time, and average first response time for the period.
- Trends: ticket volume over time, with breakdowns by status, priority, and category.
- Agent Performance: tickets handled, average resolution time, and average CSAT score per agent.
- SLA Compliance: ticket count, first response compliance percentage, and resolution compliance percentage for each priority, with a chart comparing response against resolution.
- CSAT: average score out of 5, the full rating distribution, scores by agent, and satisfaction trends over time.
- Channels: volume and average resolution time per channel, with the export adding resolved ticket counts and average first response per channel.
Export any of it to CSV or PDF for a board pack or an audit, and export the ticket list itself with your current filters applied. Help Desk Reports and Analytics walks through each view. Because tickets can link to issues, tasks, incidents, and emails, a resolution metric that looks bad because support is waiting on engineering is traceable to the development work rather than left as an unexplained number.
A review you can run in half an hour
You do not need a reporting project to get a straight answer about your support performance. Confirm you have a default SLA policy with targets per priority and business hours that match how you actually staff. Then open the SLA Compliance report over the last 90 days and read one row: Urgent.
If Urgent first response compliance is below the rest, you have a routing problem, and auto-assignment is the fix. If Urgent resolution compliance is the weak one, you have a dependency problem, and the linked issues on those tickets will usually say who you are waiting on. Then glance at the CSAT distribution for the same period. If the ones and twos cluster on tickets that met their targets, your targets are describing something your customers do not care about, which is the most useful thing a metric can tell you.
Two numbers and a distribution, and you know more about your support operation than a page of averages will ever tell you. If you want to see this against your own queue, explore ISO Mate Help Desk or start a trial. Every account begins with a 14-day free trial, which is enough time to set a policy, run a fortnight of tickets through it, and read your first honest compliance number.