Customer Support Metrics Every Business Should Track
The customer support metrics that matter (volume, backlog, first response time, resolution time, SLA compliance, reopen rate and satisfaction), how to calculate them and common traps.
Support metrics exist to answer practical questions: Are we keeping up? Are people waiting too long? Where should we improve? You do not need dozens of indicators to answer them. A small set of well-defined metrics, reviewed regularly, is far more useful than a dashboard nobody reads. This guide covers the metrics that matter for most teams, how to calculate them and the traps to avoid.
Volume metrics
Tickets created
The number of new tickets in a period. Break it down by category, channel, department and day of the week. Volume tells you what people need and when.
Tickets resolved
The number of tickets marked resolved in the period. Compare it with tickets created: if you resolve fewer than you receive for several weeks, the backlog grows.
Backlog
The number of open (not resolved) tickets at a point in time. Track it weekly. A stable backlog is healthy; a growing one is an early warning. Split it into tickets waiting on your team and tickets pending on the customer or third parties.
Speed metrics
First response time
The time from ticket creation to the first public reply from staff.
first response time = first public staff reply − ticket opened
Report the median, not only the average. A handful of tickets answered after a long weekend can distort the average. Also report it by priority.
Resolution time
The time from ticket creation to resolution.
resolution time = resolved at − opened at
Decide whether you include time spent waiting for the customer and say so in the report. Looking at the distribution (under 1 day, 1-3 days, over 1 week) often reveals more than a single number.
SLA compliance
The share of tickets that met their target.
SLA compliance = tickets within target ÷ tickets with a target
Measure first response and resolution separately and break them down by priority. See What Is SLA in Customer Support?.
Quality metrics
Reopen rate
The share of resolved tickets that were reopened because the problem was not actually solved.
reopen rate = reopened tickets ÷ resolved tickets
A high reopen rate suggests rushed resolutions or misunderstood problems.
Replies per ticket
The average number of public replies needed to resolve a ticket. Many replies often mean missing information at the start or unclear answers.
Customer satisfaction (CSAT)
A short survey after resolution ("How satisfied are you with the help you received?"). It is useful when response rates are reasonable and you read the comments, not only the score. Collecting it requires a survey process; if your tool does not offer one, a simple form linked in the closing message works.
Workload metrics
Tickets per agent
Resolved tickets per agent in a period. Use it to balance workload, not to rank people: agents handling complex categories will naturally resolve fewer tickets.
Tickets by department and category
Shows where demand comes from. A sudden increase in one category often points to a product problem, a confusing process or a change that was not communicated.
All metrics at a glance
| Metric | Question it answers | Review |
|---|---|---|
| Tickets created | How much demand? | Weekly |
| Tickets resolved | Are we keeping up? | Weekly |
| Backlog | Is work piling up? | Weekly |
| First response time (median) | How long until someone answers? | Weekly |
| Resolution time (median) | How long until the problem is solved? | Monthly |
| SLA compliance by priority | Are we meeting commitments? | Monthly |
| Reopen rate | Are solutions real? | Monthly |
| Tickets by category | What should we fix or document? | Monthly |
Common traps
- Optimizing one number at the expense of others. Pushing first response time down with empty replies ("we are looking into it") improves the metric and annoys customers.
- Using averages only. Medians and distributions tell the true story.
- Comparing agents without context. Categories differ in difficulty.
- Counting automated messages as replies. This inflates speed metrics.
- Measuring without acting. Every metric reviewed should lead to a decision, even if the decision is "no change needed".
- Inventing benchmarks. Industry "standards" quoted without a source are not a reliable target. Your own history is the best baseline.
A simple monthly review
- Compare created vs resolved and look at the backlog trend.
- Check median first response and resolution times by priority.
- Check SLA compliance and read a sample of breached tickets.
- Look at the top five categories and decide on one action (fix, document or automate).
- Write down the decisions and check them next month.
In Luradesk
The Luradesk dashboard shows open, in-progress, resolved and overdue tickets, distribution by priority, department and agent, SLA indicators, the latest tickets and recent activity, calculated from each company's own data. Reports add date filters and SLA compliance. When there is no data yet, the dashboard says so instead of showing sample numbers. Learn more on the features page.
The few numbers worth watching
Track volume, backlog, first response time, resolution time, SLA compliance, reopen rate and demand by category. Use medians, segment by priority, read the tickets behind the numbers and turn each review into a decision.