Support Metrics That Matter

Six support metrics worth reporting, and a warning about what duplicate tickets do to every one of them.

The six support metrics

First response time. What customers feel first. Median, not mean.

Resolution time. Only useful when you control the resolution.

CSAT. Per interaction, asked at close. See the CSAT calculator.

First contact resolution. The quiet indicator of quality. Rising FCR usually means better answers, not faster ones.

Ticket volume per active customer. Raw volume tells you how fast you grew. This tells you whether the product is improving.

Backlog age. Not backlog size. A stable backlog of ageing tickets is a much worse signal than a growing one being worked.

What duplicates do to each

This is the part rarely spelled out. A 12% duplicate rate doesn't add 12% noise evenly, it bends different metrics in different directions.

Volume is inflated, so growth looks worse than it is.

Cost per ticket is deflated, because the denominator grew while total cost rose.

First contact resolution is deflated, since one problem needed two contacts by definition.

CSAT is dragged down by customers who got two different answers.

SLA attainment is inflated by quickly-closed duplicates and dented by the twin that aged quietly.

A dashboard built on a queue with 12% duplicates isn't slightly wrong. It's wrong in five directions at once, which is why teams find the numbers hard to act on.

Report the ratio too

Add duplicate rate to your monthly reporting even if you do nothing about it yet. It contextualises every other number, and the first time you show it to a leadership team the follow-up questions are worth the effort on their own.

FAQ

Frequently asked questions

Which customer support KPIs are worth reporting monthly?

Five help desk metrics carry most of the signal: first response time, resolution time, one-touch rate, CSAT and backlog age. Customer support KPIs beyond those tend to be reported because they're easy to pull rather than because anyone acts on them.

What is the single most important support metric?

First response time for customer experience, first contact resolution for quality. Watching only one of them produces a team that's fast and unhelpful, or thorough and slow.

How do I measure duplicate rate?

Sample manually, count merge-tagged tickets, or connect a detector that reports it continuously.