TL;DR: Customer service metrics fall into five groups: how customers felt (CSAT, NPS, CES), how well your team performed (IQS, negative response rate, escalation rate), how fast you were (first reply time, resolution time, backlog), how effectively problems died (FCR, reopen rate, comments to solve, automated resolution rate), and what the work cost (volume by channel, workload). Track five to seven, pair every speed metric with a quality metric, and know the trap built into each number. Formulas and benchmarks below.
Most metric guides hand you a list of twenty acronyms and wish you luck. The result is dashboards nobody reads and targets that fight each other.
This guide is built differently: each metric comes with its formula, a realistic benchmark, and the trap it hides, because every support metric lies a little when you optimize it in isolation. At the end: how to pick the five that fit your team.
What are customer service metrics?
Customer service metrics are the measurements that tell you whether your support operation is working: for customers (experience), for the business (efficiency and retention), and against your own standards (quality). KPIs are the subset you commit to moving this quarter, the difference is commitment, not math.
Leading vs. lagging indicators: read this before picking KPIs
Most teams track outcomes: CSAT, churn, resolution numbers. Those are lagging indicators, they tell you what already happened, after you can do anything about it.
Leading indicators move first: quality scores, first reply time, backlog growth, escalation rate. When quality dips this week, satisfaction dips next month. A dashboard made only of lagging indicators is a rearview mirror; you want a windshield too. Mix both, and when a lagging number moves, your leading indicators should already have told you why.
Experience metrics: how customers felt
1. Customer Satisfaction Score (CSAT)
Formula: satisfied responses ÷ total responses × 100.
The default pulse of support. Sent after a conversation closes, usually as a 1-5 rating where 4-5 counts as satisfied. Healthy benchmark for most industries: 75-85%.
The trap: response bias. Typically 5-15% of customers answer, and they’re disproportionately the delighted and the furious. CSAT also punishes agents for product problems they didn’t cause. Our guide on how to measure customer satisfaction covers the design details that reduce the bias.
2. Net Promoter Score (NPS)
Formula: % promoters (9-10) minus % detractors (0-6) on the “would you recommend us” question.
NPS measures the whole relationship, not one conversation, which makes it a company metric more than a support metric.
The trap: using it to evaluate support. A customer who loves your service but hates your pricing is a detractor anyway. Track it, but don’t hang agent performance on it.
3. Customer Effort Score (CES)
Formula: average of “how easy was it to get your issue resolved” (1-7).
The research behind CES (Harvard Business Review’s “Stop Trying to Delight Your Customers”) found effort predicts loyalty better than delight: customers don’t leave because you failed to amaze them, they leave because you were hard work.
The trap: effort often lives in what customers did before reaching you (searching, waiting, repeating themselves), so pair the score with journey data or you’ll fix the wrong step.
Quality metrics: how your team actually performed
4. Internal Quality Score (IQS)
Formula: quality points earned ÷ points possible × 100, scored against your own QA scorecard.
The one metric on this list you fully control, and the only one that separates “customer was unhappy” from “we performed badly.” Most teams target 75-85%. Full breakdown in our Internal Quality Score guide.
The trap: sample size. Scored on 3-5 tickets per agent per week, IQS is mostly noise (a ±16-point margin of error at 25 reviews a month). Kaizo removes the sampling problem by scoring 100% of conversations against your scorecard automatically; whatever tool you use, know your coverage before trusting the number.
5. Negative Response Rate (NRR)
Formula: negative customer ratings ÷ all ratings.
The mirror of CSAT, and often more informative: negative ratings cluster around specific issues, agents, or days, which makes them a debugging tool rather than a vanity number.
The trap: small volumes swing hard. Three bad ratings in a slow week isn’t a trend; look for the cluster before reacting.
6. Escalation rate
Formula: escalated conversations ÷ total conversations × 100.
Rising escalations signal either a knowledge gap on the front line, an authority gap (agents can’t resolve), or a product regression generating harder tickets. All three are fixable, but they’re different fixes.
The trap: pushing the rate down by discouraging escalation. That converts visible escalations into invisible bad answers.
Speed metrics: how long customers waited
7. First Reply Time (FRT)
Formula: total wait time before first response ÷ number of inquiries.
The metric customers feel most. A fast, human first touch buys patience for everything after it. Benchmarks vary wildly by channel: minutes for chat, hours for email.
The trap: auto-acknowledgments that game the clock. Customers know the difference between a reply and a receipt.
8. Average Resolution Time (ART)
Formula: total resolution time ÷ cases resolved.
The end-to-end promise: how long from “I have a problem” to “it’s solved.”
The trap: averages hide the disasters. Track the 90th percentile alongside the mean, because the customer who waited nine days doesn’t care that the average was nine hours. And never target resolution time without a quality pair, or agents will close tickets that aren’t done.
9. Backlog
Formula: open conversations older than your SLA threshold, counted daily.
The earliest early-warning metric in support. Backlog growth predicts every other number on this list going bad two weeks later.
The trap: heroic backlog burndowns that trade quality for closure. Watch reopen rate during every backlog push.
Effectiveness metrics: did the problem actually die?
10. First Contact Resolution (FCR)
Formula: issues resolved on first contact ÷ total issues × 100.
The best single proxy for “our answers are complete.” Industry benchmark hovers around 70-75%.
The trap: channel mix distorts it. Chat resolves simple things instantly; email carries the complex cases. Compare FCR within channels, not across them. Our chat metrics guide covers the chat-specific numbers.
11. Reopen Rate (RR)
Formula: reopened tickets ÷ tickets solved × 100.
The lie detector for your speed metrics. If resolution time falls while reopens rise, you didn’t get faster, you got sloppier.
The trap: none, honestly. This is the most under-tracked honest metric in support. Keep it under 5% and investigate anything above 10%.
12. Comments to Solve
Formula: total messages exchanged ÷ tickets resolved.
How much conversation each resolution costs. Rising comments-to-solve usually means unclear first answers, missing information gathering, or a knowledge gap. In Kaizo this is tracked per agent out of the box, which makes it a precise coaching signal: the agent whose resolutions take eight messages instead of four has a specific, fixable habit.
The trap: some ticket types legitimately need long threads. Segment by issue type before comparing agents.
13. Automated Resolution Rate
Formula: issues fully resolved by self-service or AI without human touch ÷ total issues × 100.
The newest metric on the list and increasingly the one executives ask about. As AI agents handle more volume, you need to know what share of demand they truly resolve, not just deflect.
The trap: counting deflection as resolution. A bot that made the customer give up isn’t a resolution, it’s a silent failure. Audit automated conversations with the same quality standard as human ones; this is exactly where automated QA across 100% of conversations stops being optional, because nobody manually samples ten thousand bot chats.
Volume and workload metrics: what the work costs
14. Handled Tickets by Channel
Formula: count of resolved conversations, split by channel, per period.
The staffing map. Channel mix shifts slowly and then suddenly (a product launch, a new market), and teams staffed for last year’s mix produce this year’s backlog.
The trap: treating all tickets as equal work. Weight by handle time when planning capacity.
15. Agent workload and utilization
Formula: productive conversation time ÷ available working hours.
Sustained utilization above ~85% looks efficient on paper and produces burnout, sick leave, and quality decay in practice. This is the metric that protects all the others.
The trap: using it to rank agents. Workload is a management outcome, not an agent choice.
How to choose your 5 (not track all 15)
Fifteen metrics is a reference, not a dashboard. Pick one per question:
| The question | Pick one of |
|---|---|
| How do customers feel? | CSAT, CES |
| How well did we perform? | IQS, NRR |
| How fast are we? | FRT, ART (with a P90) |
| Did problems actually die? | FCR, reopen rate |
| Is the workload sustainable? | Backlog, utilization |
Two pairing rules that prevent most dashboard lies: every speed metric needs a quality partner, and every satisfaction metric needs an internal-standard partner. Gartner’s research found 52% of QA leaders now see their program’s main value as voice-of-the-customer insight, which is what a well-paired dashboard becomes: not a scoreboard, an early-warning system.
Review the set quarterly against your goals; our guides on customer experience metrics and improving customer satisfaction help when the goal shifts from measuring to moving the numbers.
Putting the metrics to work with scorecards
Numbers change behavior only when someone owns them. A team scorecard assigns each KPI an owner, a target, and a review cadence, and turns “the dashboard exists” into “the dashboard gets acted on.” Weekly for leading indicators, monthly for lagging ones.
Related reading
- What is CSAT?
- What is NPS?
- What is CES?
- What is FCR?
- What is AHT?
- What is First Response Time?
- CSAT vs NPS vs CES
- What is conversation intelligence?
- Customer service QA glossary
- What is DSAT?
- CSAT vs DSAT: the difference
- How to reduce DSAT
- The call center QA metrics that predict CSAT
Frequently asked questions
What are the 4 most important metrics of customer service?
If you can only track four: CSAT (experience), IQS (quality), first reply time (speed), and first contact resolution (effectiveness). That set catches most problems from at least one angle.
What are the 5 key performance indicators for customer service?
The same four plus reopen rate, which keeps the speed and resolution numbers honest. Add backlog as a sixth if your volume is spiky.
What’s the difference between customer service metrics and KPIs?
Metrics are everything you can measure; KPIs are the few you’ve committed to moving this quarter, with an owner and a target. Every KPI is a metric, not every metric deserves to be a KPI.
What is a good CSAT score for customer service?
Most established teams land between 75 and 85%. Above 90% consistently, check your survey design for bias; below 70%, look at quality scores and staffing before blaming agents.
How many customer service KPIs should a team track?
Five to seven. Fewer misses whole categories; more dilutes ownership. One per question you need answered, plus a pairing metric for anything speed-related.
The dashboard is the easy part
Every metric here can be assembled in an afternoon. What separates teams is what happens when a number moves: whether anyone notices, whether they can find the why, and whether the fix gets verified. That loop, notice, diagnose, fix, re-measure, is the actual product of a measurement culture.
If you want your quality, speed, and coaching metrics calculated across 100% of conversations instead of a sample, book a demo and we’ll show you on your own data.
