rapidFOX Logo
rapidFOX
Smart Helpdesk

Customer service KPIs

Guides · rapidFOX Lesezeit 7 min

Support metrics are easy to produce and easy to game. These are the ones that change decisions, and the ones that quietly do harm.

The four that matter

  • First response time. How long until a person answers. The single best predictor of whether customers feel looked after.
  • Resolution time. How long until it is finished. Read the median, not the mean – one three-week case ruins an average.
  • Clearance rate. Cleared divided by received, over the same period. Below 100 per cent for several weeks means the backlog is growing and no individual metric will show it.
  • SLA rate. The share inside the agreed time. Only meaningful if the agreement is realistic.

Read the median, not the average

Support data is skewed by nature: most cases are quick and a few are enormous. The mean describes neither. The median tells you what a typical customer experienced, which is the question you were asking.

Metrics that mislead

  • Tickets per agent. Rewards closing fast, which rewards closing badly. The reopened ticket does not show up.
  • Total volume. Rising volume can mean a growing business or a broken product. On its own it says nothing.
  • First contact resolution, unless defined very carefully. It is trivially improved by asking fewer clarifying questions.

Count honestly

The most common quiet distortion is counting a resolution on the day it was closed rather than the day it arrived. That makes a catch-up week look like a great week. Attribute the work to the day the request came in and the picture stops flattering you.

How often to look

Weekly for the clearance rate – it is the early warning. Monthly for the rest. Daily reporting in support produces reactions to noise.

What to do with them

A metric that never changes a decision should be deleted. If the SLA rate drops, the question is staffing or target; if resolution time rises, the question is complexity or knowledge. If nobody asks a question, stop producing the number.

How to act on slow response times is in improving response times.

Try rapidFOX free for 7 days

Help desk software with a local AI – GDPR compliant, hosted in Germany. No card, ready in 2 minutes.

Start free now

Common questions

How many KPIs should we track?

Four is plenty. More than that and nobody looks at any of them.

Should we measure customer satisfaction?

If you will act on it, yes. A survey nobody reads costs your customers time and gives you nothing.

Is a rising ticket volume bad?

Unknown without context. Rising volume with a stable clearance rate is growth; with a falling one it is a backlog forming.

What is a good first response time?

It depends entirely on what you promised. Against no promise, most B2B customers find same-business-day acceptable and four hours good.

Read on