← All articles

10 Metrics Every Customer Support Operation Should Track (and 3 to Stop Using)

Most support dashboards are full of vanity metrics. Here's the framework for measuring what actually drives business outcomes — and what to deprioritise.

Operations · 6 min read · 11 May 2026

The metrics trap

Customer support generates an enormous amount of data: ticket volumes, response times, resolution rates, CSAT scores, NPS, handle times, reopen rates, escalation rates. Most teams track all of it. Very few use any of it well.

The problem is that most support metrics are measurements of activity, not outcomes. Tracking average handle time tells you how fast agents are — not whether customers are satisfied or whether problems are actually being solved.

The 10 metrics that matter

1. First Contact Resolution (FCR): The percentage of issues resolved without a follow-up contact. This is the single best predictor of customer satisfaction and cost efficiency.

2. Customer Effort Score (CES): How much effort did the customer have to expend to get their issue resolved? Lower effort = higher loyalty.

3. CSAT by issue type: Overall CSAT hides the issues that are dragging it down. Break it down by category to find where to invest.

4. Ticket reopen rate: A reopened ticket means the first resolution failed. High reopen rates indicate quality or process problems.

5. Escalation rate: What percentage of tickets require escalation to a senior agent or manager? High rates indicate training gaps.

6. Agent quality score: From QA reviews — the leading indicator for CSAT.

7. Time to first response (by channel): The standard varies dramatically — 1 hour for email, 5 minutes for chat, 30 seconds for phone.

8. Backlog trend: Is your unresolved ticket count growing or shrinking? The trend matters more than the absolute number.

9. Volume per issue category: Understanding what your customers are contacting you about is as important as how you handle it.

10. Cost per resolution: The total cost of your support operation divided by resolved tickets. Track this over time as you scale.

The 3 metrics to stop using as primary KPIs

Average Handle Time (AHT) as a primary KPI creates perverse incentives — agents rush resolutions to hit their AHT target, resulting in poor quality and higher reopen rates. Track it for staffing modelling, not agent performance.

Raw ticket volume tells you almost nothing useful on its own without normalising for customer base size.

Global NPS as a support metric conflates many things. A customer who loves your product but had a poor support experience will give a NPS that reflects their overall relationship — not the support interaction.