Guide · Helpdesk
SLA metrics to track in customer support
In short
Track how fast customers hear from a person (first response time), how long until the problem is solved (resolution time, without the time you waited on them), and the share of tickets that met their target (SLA compliance). Then look at where breaches happen, how old the backlog is, and how often solved tickets come back.
Reviewed 9 November 2026. Terms used: SLA (service level agreement), CSAT vs NPS, Ticketing system.
Seven metrics, and how to read each one
Start with the first three. Add the rest once those are in a weekly review.
First response time: average and median
The time from the customer’s message to the first reply from a person. An automatic “we’ve got your message” doesn’t count.
Look at the median as well as the average. A handful of tickets that waited a weekend can drag the average up while most customers were answered quickly; the median shows the typical wait.
Resolution time, without the waiting
The time from the first message until the request is solved. Leave out the time you were waiting on the customer or a supplier, or one slow reply from them makes your team look slow.
SLA compliance
The share of tickets that met their target: met divided by met plus breached. Measure it per policy, because an urgent ticket and a routine one have different promises behind them.
An example week Tickets with a result: 120 (110 met, 10 breached)
SLA compliance = 110 ÷ (110 + 10) ≈ 92%
Where the breaches happen
A compliance figure tells you there’s a problem; breaches by category, team, channel and priority tell you where. If most breaches are warranty tickets on WhatsApp, that’s the queue to staff or the process to fix.
Backlog by age
How many open tickets there are, grouped by how long they’ve been open. A steady backlog that keeps getting older is a warning before compliance drops.
Reopen rate
The share of resolved tickets the customer reopened. Fast resolutions that come back weren’t resolutions. A rising reopen rate next to a falling resolution time usually means tickets are being closed too early.
Satisfaction beside the clock
Put CSAT next to the time metrics. A team can meet every target and still leave customers unhappy; the comments tell you why.
How to set the targets behind the metrics
Targets
- Do
- Set from a few weeks of your own data
- Avoid
- Copying a number from another company
Hours
- Do
- Count business hours for teams that close
- Avoid
- Counting nights against a day team
Priorities
- Do
- Tighter targets for urgent work
- Avoid
- One target for everything
First reply
- Do
- A real answer, or a real next step
- Avoid
- A holding reply to stop the clock
How it works in Axonave
The clocks on every ticket, and the metrics in Reports → Tickets.
Axonave matches each ticket or chat to an SLA policy by priority and channel, warns the assignee before the target and tells their team leaders on a breach. Reports → Tickets shows SLA compliance as met ÷ (met + breached), first response as an average and a median, resolution time without waiting time, the reopen rate and the backlog by age, in business hours or clock time, and every number opens the tickets behind it.
- Waiting on the customer pauses the resolution clock
- Chat reports: first response, abandonment and hand-overs
- Reports → Surveys: CSAT and NPS by agent, team and channel
An urgent WhatsApp ticket in our demo workspace: first response met, the resolution clock still running, and how much of its window has gone.
Common questions
What’s a good first response time?
The one you can keep and your customers are happy with. Measure your own for a few weeks, set the target a little better than today, and tighten it once the team meets it. Chat customers usually expect a faster answer than email.
Should SLA targets count weekends?
Only if someone works them. If your team is off at weekends, count business hours, and tell customers when you’ll reply. In Axonave each policy counts either around the clock or your business hours and holidays.
Does a reopened ticket restart the SLA?
In Axonave, yes: reopening restarts the resolution clock, and the reopen counts in the reopen rate, so a ticket closed too early shows up in the reports.
See it working with your own customers.
We reply within one business day by email or WhatsApp.