12 Customer Support KPIs That Actually Matter
Metrics, formulas, and benchmarks every small-business support team should know. Free reference, no signup.
Pick 4–6, not 12
This page lists 12 because that is the useful universe of support metrics worth knowing. Any single team should pick the 4–6 that match their actual problem — not track all 12 for dashboard porn. A team that reviews four metrics weekly outperforms a team that glances at twelve quarterly.
Speed
First Response Time (FRT)
Time between when a customer sends a message and when they get a real human reply (not an auto-ack).
Healthy range
Email: < 4 hrs. Live chat: < 2 min. Social: < 30 min.
Common gotcha
Do not count auto-replies as first response — the number looks great, the customer still feels ignored.
Average Resolution Time (ART)
Time from ticket creation to ticket closed.
Healthy range
Email: < 24 hrs. Live chat: single session. Complex issues: < 72 hrs.
Common gotcha
Auto-close rules skew this down artificially. Report manually-resolved tickets separately if your system auto-closes after N days of silence.
SLA Compliance %
Share of tickets resolved within the agreed SLA window.
Healthy range
≥ 90% for internal targets, ≥ 95% if the SLA is contractual.
Common gotcha
A 99% compliance rate with a 24-hour SLA tells you less than a 90% rate with a 4-hour SLA. Track both the SLA target and compliance, never compliance alone.
Time-to-First-Touch on New Customers
FRT specifically for first-time senders — how fast new customers get a reply.
Healthy range
Tighter than overall FRT — ideally half of median FRT for the channel.
Common gotcha
First impressions are disproportionately durable. A new customer waiting 6 hours is worse than a repeat customer waiting 6 hours.
Quality
Customer Satisfaction (CSAT)
Post-resolution rating of the support interaction. Usually 1–5 or thumbs up/down.
Healthy range
≥ 85% positive on a thumbs-up/down scale. ≥ 4.5/5 on a 5-point scale.
Common gotcha
If your response rate on the survey drops below 20%, the CSAT number is not statistically meaningful — only the people who felt strongly reply.
Net Promoter Score (NPS)
How likely a customer is to recommend your business, on a 0–10 scale. Company-wide, not per-ticket.
Healthy range
> 30 is good for ecommerce. > 50 is excellent. Negative means you are losing trust.
Common gotcha
NPS is a brand metric, not a support metric. If you are tracking NPS after each ticket you are measuring the wrong moment.
First Contact Resolution (FCR)
Share of tickets resolved on the first human reply, without back-and-forth or escalation.
Healthy range
≥ 70% for simple transactional support. ≥ 50% for product-complex support.
Common gotcha
Teams trying to hit an FCR target push 'this should fix it, let me know' replies that close the ticket prematurely. Pair FCR with reopen rate.
Reopen Rate
Share of closed tickets the customer reopens within 7 days.
Healthy range
< 10% is healthy. > 20% means tickets are being closed too aggressively.
Common gotcha
A low reopen rate plus a low FCR usually means customers are giving up rather than getting resolved.
Volume and load
Ticket Volume
Total tickets received per day, week, and month.
Healthy range
No absolute target — track the trend. Volume growth that outpaces revenue growth signals a product problem.
Common gotcha
Batch-sent marketing emails triggering 200 "wrong email!" replies will spike volume without changing the underlying workload. Exclude those separately.
Backlog
Open tickets older than 24 hours, checked daily.
Healthy range
Near zero by end of each business day. Sustained non-zero means you are underwater.
Common gotcha
Teams that move old tickets to "on hold" or "waiting on customer" to clear the queue are optimizing for the number, not the customer. Count those too.
Business
Cost per Ticket
Fully-loaded support cost divided by tickets resolved in the period.
Healthy range
Varies by business model. Track the trend over time — cost per ticket should fall as the team gets more efficient, or rise for clear reasons (new product, new channel).
Common gotcha
Driving this number down by cutting response quality shows up immediately in CSAT and reopen rate. Optimize as a portfolio, not a single metric.
Support-Driven Retention
Share of customers who contacted support in the last 90 days and are still active customers.
Healthy range
Should be near or above your overall retention rate. Lower means support contact correlates with churn — a sign the issues behind those tickets are not being fixed at the product level.
Common gotcha
This is a correlation, not a causation number. Use it to spot patterns, not to justify the support budget.
How to pick which KPIs to track
- Customers complain about slow replies → FRT, SLA Compliance, Time-to-First-Touch
- Customers complain about unhelpful replies → CSAT, Reopen Rate, FCR
- The team feels drowned → Ticket Volume, Backlog, Cost per Ticket
- Leadership wants to justify the team budget → Cost per Ticket, Support-Driven Retention
Setting targets without making the team miserable
Targets should come from your last 90 days of data, not from an industry blog. Look at what you already do on a good day, set the target around that, and tighten over time. Targets pulled out of a benchmark post — with no connection to what the team is already capable of — become morale problems within a month.
Publish the target internally before tying it to comp. Tying compensation to a brand-new metric without a baseline is how you get gaming: ticket-closing sprees at month-end, reopen-rate games, CSAT survey gaming. Measure for a quarter before anyone's bonus depends on the number.
From cheat sheet to dashboard
The cheat sheet tells you what to measure. A help desk with these KPIs built in tells you where you stand, in real time. Auxx.ai tracks FRT, resolution time, SLA compliance, CSAT, and backlog out of the box — so you do not need a separate dashboard tool.
Frequently asked questions
Related free tools
Stop measuring support in spreadsheets.
Auxx.ai gives you a live dashboard for FRT, CSAT, SLA compliance, and the rest — updated on every ticket.
See how Auxx.ai works