Most support tools will happily show you twenty charts. For a lean team, that is the problem, not the solution. A wall of widgets feels like insight but rarely changes what you do on Monday morning. The teams that actually improve track a handful of customer support metrics, know what “good” looks like for each, and act on the trend.

This guide covers the customer support metrics and KPIs worth knowing, how to calculate each, what a healthy benchmark looks like, and which few genuinely predict retention and revenue. Treat the benchmarks as directional: the right target depends on your channel, your customers, and your price point.

Speed metrics: how fast you respond and resolve

First response time (FRT)

The time from a customer’s first message to your first human reply. It is the metric customers feel most, because waiting in silence is what turns a small question into frustration.

Track the median, not the average. One ugly weekend ticket can drag an average into meaninglessness while the median tells you what a typical customer actually experiences. Good looks like under a minute for live chat during active hours, and under a few hours for email. The exact number matters less than the consistency.

Average resolution time

The time from first message to “resolved.” First response time gets attention; resolution time delivers the outcome. Watch the long tail here, not just the average. The handful of tickets that drag on for days are usually the ones that become bad reviews or churned customers, so segment them out and ask why they stalled.

Quality metrics: how well you solve problems

Customer satisfaction (CSAT)

A direct “was this helpful?” or 1 to 5 rating after a resolution. CSAT is your cleanest quality signal. Calculate it as the percentage of positive responses out of all responses. Above 90 percent is strong for most software teams. At low volume it is noisy, so watch the trend across weeks rather than obsessing over a single bad day.

First contact resolution (FCR)

The share of issues solved in a single interaction, with no back and forth and no reopen. High FCR is the quiet driver of both satisfaction and low cost: every reopened ticket is a customer re-explaining themselves and an agent re-loading context. Around 70 to 75 percent is a healthy target. If FCR is low, the fix is usually better macros, clearer docs, or surfacing more context to the agent up front.

Customer effort score (CES)

How hard the customer had to work to get helped, usually a “this was easy” agree/disagree prompt. Effort predicts loyalty better than delight does: customers rarely reward you for low effort, but high effort reliably pushes them toward the exit. Lower is better.

Volume and efficiency metrics: can you scale?

Ticket volume

The raw count of incoming conversations. On its own it means little. More tickets is not inherently bad, slow tickets are. Volume becomes useful when you normalize it (tickets per customer, per account, or per 100 active users) and watch the direction. A spike in tickets-per-customer after a release is a product signal, not a staffing problem.

Ticket deflection rate

The share of customers who get an answer without ever opening a conversation, usually through a help center or in-product content. Deflection is what lets support volume grow slower than your customer base. If conversations rise while your team stays flat, deflection is doing the work. We go deep on this in how to reduce support tickets.

Backlog and average ticket age

How many conversations are open and how old they are. A growing backlog is the earliest warning that demand is outrunning capacity, well before it shows up in CSAT. Watch the age of the oldest open tickets, because those are where quiet frustration compounds.

Loyalty: the long-game metric

Net promoter score (NPS)

“How likely are you to recommend us?” on a 0 to 10 scale, scored as the percentage of promoters minus detractors. NPS is a relationship metric, not a ticket metric, so survey periodically rather than after every interaction. It is most useful as a slow-moving trend line and as a prompt: read the comments behind the scores, that is where the actual product and support insight lives.

How to choose which KPIs to track

You do not need all of these. Tracking twelve metrics usually means acting on none. Pick three or four that map to your current bottleneck:

Customers complaining you are slow? First response time and backlog.
Solving things but customers still churn? FCR, CES, and resolution time.
Drowning as you grow? Deflection rate and tickets-per-customer.

Choose, watch the trend, and move the number. Then revisit the set as your constraint changes.

The metric most teams miss: support’s effect on revenue

Here is the one that almost no support dashboard shows, and the one that matters most for a software business: what support is doing to retention and revenue. For a broader view of how to build the support function around these outcomes, SaaS Customer Support: A Practical Guide for Lean Teams covers the full picture.

A fast, high-quality support interaction is not just a closed ticket. It is a renewal you kept, a downgrade you prevented, a five-star review you earned. The reverse is also true: a slow or unresolved issue is often the quiet first step toward a cancellation. If you can connect support activity to revenue outcomes, support stops being a cost center on a spreadsheet and becomes a retention lever you can actually manage.

For SaaS and Shopify app teams specifically, the highest-leverage move is to put each customer’s revenue context, their plan, monthly value, and churn risk, beside the conversation, so you can see which slow tickets are actually expensive. Then close the loop: when a customer does leave, look back at whether support was the cause. That feedback is what tells you which metric to fix next. We cover the playbook in how to reduce customer churn, and the link between fast support and ratings in how to get more reviews.

How to track these without building reports

You should not have to wire up a data pipeline to know your first response time. Convot tracks first response and resolution time automatically, groups activity by customer so you see a complete history in one place, and shows live revenue intelligence, plan, value, and churn risk, beside every conversation. Its AI can also attribute churn back to support after a customer leaves, which turns your metrics from a scoreboard into a to-do list.

Pick the few metrics that predict retention, watch the trend, and improve the worst one. First response time is almost always the right place to start.

The takeaway

Customer support metrics are only useful when they change what you do. Skip the vanity dashboard. Track speed (first response, resolution), quality (CSAT, FCR), and efficiency (deflection, backlog), pick the three or four that map to your current bottleneck, and connect them to the outcome that pays the bills: retention. Answer fast, resolve completely, deflect the easy questions, and watch the numbers that tell you whether you are doing exactly that.

Try Convot free and get first response and resolution tracking, with revenue context, out of the box.

Customer Support Metrics & KPIs: The Ones That Actually Matter