How to Measure Customer Support Agent Performance

Why ticket count alone is misleading

If you measure agents solely by number of tickets closed, you create perverse incentives: agents rush through tickets without fully resolving them, cherry-pick easy tickets, and close issues prematurely to inflate their numbers. Customers get half-answers and reopen tickets, creating more work for everyone.

Good agent performance measurement uses a small set of complementary metrics — volume plus quality plus speed — so that gaming one metric doesn't inflate the overall picture.

The 6 metrics that matter

1. First Response Time (FRT)

How long from when a ticket arrives to when the agent sends the first reply. This is the metric customers feel most directly — a fast acknowledgement, even if the full answer takes longer, dramatically improves satisfaction.

Target: Under 4 hours for High priority, under 24 hours for Medium, under 48 hours for Low.

2. Resolution Time

How long from ticket open to ticket closed. Measures how efficiently agents get to a complete resolution, not just an acknowledgement.

Watch for: Agents with fast FRT but slow resolution — they're acknowledging quickly but not following through. Also watch for very slow resolution on specific ticket categories, which may signal a process or product problem rather than an agent problem.

3. Customer Satisfaction (CSAT)

A simple "Was this resolved to your satisfaction? Yes / No" sent after ticket close. The most direct measure of quality. An agent can close 100 tickets a day with 60% CSAT, while another closes 30 tickets with 95% CSAT. The second agent is more valuable.

Target: 85%+ across the team. Individual agents below 75% need coaching.

4. Reopen Rate

What percentage of "closed" tickets get reopened because the issue wasn't actually resolved? A high reopen rate means agents are closing tickets prematurely.

Target: Under 10%. Above 15% is a red flag.

5. Ticket Throughput

How many tickets an agent handles per day/week, adjusted for ticket type complexity. This is where volume matters — but only in context of the other metrics. High throughput with high CSAT is excellent. High throughput with low CSAT is a problem.

6. Escalation Rate

What percentage of an agent's tickets do they escalate to a manager or senior agent? A high escalation rate can mean the agent is working beyond their knowledge level (needs training) or is avoiding difficult conversations (needs coaching). A very low escalation rate on a new agent might mean they're not escalating when they should.

How to use these metrics in practice

Review these metrics weekly at the team level, monthly at the individual level. The weekly team review catches systemic problems (SLA breach trend, CSAT dip this week). The monthly individual review is for development conversations, not gotcha moments.

The performance review conversation

Monthly 1:1 with each agent. Structure:

1. Show the metrics for the month — no editorialising, just the numbers
2. Ask the agent what they notice ("How do you feel this month went?")
3. Identify one metric to improve next month and discuss why it might be low
4. Agree on one specific action to take (e.g., "Review your reopened tickets from this month and identify the common thread")

This is a development conversation, not a performance improvement plan. Most agents respond better to coaching than to pressure.

When to escalate to formal performance management

Three consecutive months of CSAT below 70%, or reopen rate above 20%, or consistent SLA breaches despite coaching — at that point the conversation shifts from development to formal performance management. One bad month rarely justifies a formal process; a sustained pattern does.