Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Customer Experience, Retention & Loyalty › CX Measurement

Customer Service Metrics and How to Read Them

Which customer service metrics to track and how to read them: first reply, resolution, repeat contacts, contact rate, backlog age and satisfaction by reason.
Guideintermediate13 min readUpdated

Why service metrics mislead when read alone

Service metrics are attractive because they are fast, precise and owned by one team. The measurement hub lists them as the operations side of experience evidence, beside perception and behaviour, with the warning that they measure the business rather than the customer. That warning is the whole problem. A support team can make most operational numbers look better without any customer being better served.

Take the most common headline, average time to first reply. It improves if agents send a quick acknowledgement that answers nothing, if difficult contacts are left until the easy ones are cleared, or if the clock is stopped by an automatic message. Each of those makes the customer wait longer for an answer. The support channels and self-service guide makes the point directly: a fast reply that does not solve the problem starts the clock again, and repeat contacts are the clearest sign of a channel answering quickly but badly.

This is Goodhart's law at work. The Goodhart's law framework explains that a measure stops measuring once it becomes a target, because effort flows to whatever moves it most cheaply, and that the counterweight is a guardrail metric: a measure that must not get worse while the target is pursued. Service metrics need that design more than most, because they are reported weekly, often per agent, and sit close to people's reviews.

Two other traps sit beside gaming. Averages hide the customers who waited longest, who are the ones most likely to complain or leave. And totals hide mix: a week dominated by simple questions looks faster than a week dominated by complaints, whatever the team did. Both are fixed by reading the metrics the right way, which the rest of this guide sets out. No figure on this page is a target or a benchmark. The site cites no response, resolution or satisfaction benchmarks, and the guides read experience measures against the business's own baseline.

The core metrics: a definitions table

A small, stable set covers most decisions. The table defines each metric, what it hides and how it is usually gamed.

MetricWhat it countsWhat it tells youWhat it hidesHow it is gamed
Time to first replyTime from the customer's first message to the first reply from a personHow long customers wait to hear backWhether the reply helped; the longest waits, if read as an averageHolding replies that say nothing; answering easy contacts first
Time to resolutionTime from the first message to the point the problem is solvedHow long the problem lasts for the customerContacts closed before they were really solvedClosing contacts early; splitting one problem into several contacts
Resolved in the first exchangeContacts solved without any further message from the customerWhether the first answer was completeContacts where the customer gave up rather than came backCounting a contact as resolved because no reply arrived
Repeat contactsCustomers who get in touch again about the same problem within a set windowWhether answers actually solved the problemCustomers who left instead of coming backTagging the second contact as a new reason
Contact rateContacts per order, per active customer or per bookingHow often customers need help at allProblems customers solve alone or abandonMaking it harder to get in touch
Backlog and its ageOpen contacts waiting, and how long the oldest have waitedWhether work is piling up and who is stuckContacts parked in a pending statusMoving contacts to "waiting on customer" to stop the clock
Volume by reasonContacts per reason from the reason listWhere demand comes from and who can remove itReasons tagged inconsistentlyTagging into broad reasons that blame no team
Satisfaction or effort by reasonPost-contact survey answers, split by contact reasonWhich kinds of contact leave customers unhappyCustomers who did not answerSurveying only contacts that ended well
Handle timeTime agents spend working on a contactWhich reasons take effort, often because a process is brokenQuality of the answerRushing contacts to finish them

Contact rate is the metric most teams lack and most need, because it connects support to the rest of the business. It turns a rise in volume into a question: did the business grow, or did something make customers need help more often?

Contact rate = contacts in the period ÷ orders (or active customers, or bookings) in the same period(ratio)

Volume by reason depends on a reason list agents apply consistently, which the tutorial on tagging support contacts by reason builds. Satisfaction and effort questions, their wording, timing and sampling, belong to the voice of the customer guide; this guide only reads their answers by reason. Where an AI assistant answers or drafts some contacts, the AI in customer service guide adds accuracy and handover measures and warns against judging an assistant by deflection. If that figure climbs while customers keep asking the assistant for a person, the diagnosis for an AI assistant not resolving customer questions reads the conversations behind it and traces each to its cause.

Definition decisions to settle once

Most arguments about service numbers are arguments about definitions. Settle each of these once, write it down and hold it in a shared metrics layer, as the metrics layer and definitions guide describes, with a formula, filters, a time rule, an owner and a version.

  • Business hours or elapsed time. A contact that arrives on a Friday evening can wait a whole weekend on elapsed time and almost no time on business hours. Choose one per channel, state it in the report and keep it. Customers experience elapsed time, so many teams report both.
  • What counts as a reply. Decide whether automatic acknowledgements count. A reply that only confirms receipt should not stop the first-reply clock. Writing that rule into the definition of time to first reply keeps the figure comparable when the help desk's automatic messages change.
  • What counts as resolved. Decide whether resolution is when an agent closes the contact, when the customer confirms, or when no further message arrives within the window. Each gives a different figure; the last is the hardest to game.
  • The repeat window. Choose the window within which a second contact about the same problem counts as a repeat, set from how long problems in your business normally take to show they are fixed, and record it.
  • Reopened and merged contacts. A contact reopened by the customer is a repeat, not a new contact. Contacts merged because the customer wrote twice, or in two channels, count once.
  • Pending statuses. Decide whether time spent "waiting on customer" or "waiting on a supplier" stops the clock, and report the time spent in those statuses separately so they cannot hide work.
  • The base for contact rate. Choose orders, active customers or bookings, whichever best represents the demand for help, and count it on the same dates as the contacts.
  • Channels. Measure each channel on its own definitions and report them side by side. A chat reply and an email reply are not the same promise.

Put the definitions where the report is read. A note under each chart saying which clock and which window it uses saves a meeting.

Pairs that keep each other honest

Every metric that could become a target needs a partner that would expose it if it were gamed. The pairs below are the ones that matter most for service.

If you watchRead it besideBecause
Time to first replyRepeat contacts, by reasonFast replies that do not solve the problem come back
Time to resolutionReopened contacts and repeat contactsClosing early shortens resolution and creates repeats
Resolved in the first exchangeSatisfaction or effort by reason, and contact rateCustomers who gave up look resolved
Contact rateComplaints and reviews about getting help, and repeat contactsHiding contact options lowers the rate and raises frustration
Backlog sizeAge of the oldest open contacts, and time in pending statusesA small backlog can still hold customers waiting a long time
Handle timeRepeat contacts and quality reviewShort contacts that do not solve the problem cost more later
Satisfaction by reasonResponse rate and unprompted complaintsA score from the happiest customers stops warning of problems

A guardrail does not need its own target. It needs a limit, an owner and a place in the same view as the metric it protects. Keep the definitions out of the hands of whoever is judged on the number, so the clock rules and the repeat window change only through a recorded decision. When a spike has already left a backlog far beyond the standard, the tutorial on clearing a support backlog works through the customers waiting under these same rules, with merged contacts counted once, pending time reported apart and nothing closed to stop the clock. Metrics read per agent deserve extra care: they are useful for coaching when read beside quality, and harmful when they become a league table.

Reading metrics by reason, channel and customer

Totals and averages answer few questions. Three splits answer most of them.

By reason. Read every metric by contact reason. The same team can answer delivery questions quickly and completely and struggle with billing questions that need another department. A reason with high repeat contacts points to an answer or a process that does not work; a reason with a high contact rate points to a page, an email or a promise that leaves customers unsure. That second kind is often marketing's to fix, and the reason list sends it to the right owner.

By channel. Read each channel against its own standard. Moving customers from one channel to another changes the mix and can make every channel's average move without any change in service. The support channels guide sets standards per channel; read the metrics against them, not against each other.

By customer. Read waits and repeats for groups of customers as well as for contacts. New customers in their first weeks, customers with a complaint already open and high-value customers deserve their own view, because the same wait means more to them. The churn and retention metrics guide puts contact rate per customer, first-contact resolution and complaint volume by cause on the retention dashboard as service indicators; reading them by customer group is what lets them act as a Leading Indicator for churn.

Distributions, not only averages. Report the median and the longest waits beside any average, or the share of contacts answered within the business's own standard. One customer who waited far longer than the rest disappears in an average and reappears in a complaint.

Small numbers. A reason with a handful of contacts will jump around from week to week. Show the counts behind every rate and read movements with the caution the reading small numbers guide recommends, pooling weeks where volumes are low.

A weekly service report that leads to decisions

A weekly report earns its time when every section can lead to an action. A row of averages, each a little better or worse than last week, is a set of vanity metrics however operational it looks. A report that works usually has five parts, in a fixed order.

  1. Demand. Contacts and contact rate against the chosen base, by reason, with the reasons that moved most highlighted. This is the section other teams need, because it shows what is generating work.
  2. Speed. Time to first reply and time to resolution per channel, against the business's own standards, with the oldest open contacts listed.
  3. Effectiveness. Resolved in the first exchange and repeat contacts, by reason. This section tells you whether speed was bought with quality.
  4. Customer view. Satisfaction or effort by reason, with response counts, and a few anonymised comments.
  5. Decisions. A short list of actions with owners and dates, and last week's actions checked. A reason with rising repeats might go to the help centre owner; a reason with a rising contact rate after a campaign might go to marketing; a growing backlog might lead to a change in routing.

Place the service metrics in the wider tree. The KPI tree framework breaks an outcome into drivers with owners, and the KPI tree for retention puts service on the voluntary churn branch beside product and messaging. Service metrics belong there as drivers, read under the retention outcome, not as the outcome itself. Make a service metric a KPI only where an owner can move it and a guardrail stands beside it.

Numbers cannot say whether a reply was right, clear or kind. The tutorial on reviewing support conversations for quality reads a sample of real conversations against the business's own standards, and its findings belong in the effectiveness section of the report beside repeat contacts. When the report keeps pointing at the same weaknesses, the customer service audit scorecard rates the whole operation behind it, from channels and replies to complaints and campaign briefings, and ranks the fixes.

The same discipline applies inside marketing. The guide to setting service levels for marketing requests sets turnaround from the team's own records, conditional on a complete request and reported for the system rather than per person, which is the same approach that keeps customer service metrics honest.

A contact lens retailer rebuilds its service report (illustrative)

Illustrative example — not a real result

Ozbrenna Contact Lenses looks past its average first reply time

Ozbrenna Contact Lenses, an invented online contact lens retailer, has 6 agents answering email and chat. Its weekly report shows one number: average time to first email reply, which has fallen from 9 hours to 4 hours over a quarter. The support lead adds three things: repeat contacts within 7 days, contact rate per 100 orders, and both read by contact reason.

The new view changes the story. Prescription-check contacts, where customers ask why an order is on hold while the retailer confirms their prescription, are answered fastest of any reason, in a median of 2 hours, yet 44% of them come back within 7 days. Contact rate for that reason is 6.8 per 100 orders, against 1.9 for delivery questions. Reading 40 of the repeat contacts shows the cause: the checkout form asks for the prescriber's details in a single free-text box, many customers leave it incomplete, and the hold email does not say what is missing.

The team does not add staff. The web team splits the free-text box into labelled fields and the hold email names the missing detail. Over the following 8 weeks, prescription-check contacts fall to 3.1 per 100 orders and the share coming back within 7 days falls to 18%. Average first reply time barely moves, at 4 hours, which the lead now reports beside the repeats rather than on its own.

Common mistakes

  • One headline average. Average first reply time alone rewards replies that say nothing and hides the longest waits.
  • No guardrail beside a target. Every metric that is watched closely needs a partner that would show if it were gamed.
  • Definitions that drift. Changing what counts as a reply, a resolution or a repeat without recording it makes every trend meaningless.
  • Volume without a base. Contacts rising in a busy month is not a service problem. Report contact rate against orders, customers or bookings.
  • Ignoring repeat contacts. They are the clearest sign that answers are fast but incomplete.
  • Pending statuses that stop the clock. Time parked in "waiting" states is time the customer still waits. Report it.
  • Per-agent league tables. Individual speed targets push agents to close contacts rather than solve problems.
  • Borrowed benchmarks. A figure from another business or an industry survey is not a standard for yours; set standards from your own customers and capacity.
  • Totals instead of reasons. A metric read only in total cannot tell you which process, page or promise to fix.
  • Reports with no decisions. A weekly report that ends without actions and owners becomes a ritual.

Frequently asked questions

What are the most important customer service metrics?

Usually a small set: time to first reply, time to resolution, contacts resolved in the first exchange, repeat contacts on the same problem within a set window, contacts per order or per customer, the age of the oldest open work, and satisfaction or effort read by contact reason. Which matter most depends on the decisions the business needs to make. Each should be read beside another that would expose it if it were gamed, rather than alone.

What is a good first response time for customer service?

This site does not cite any benchmark for response or resolution times, and a figure taken from another business says little about yours. Set standards per channel from what your customers expect and what your team can keep, as the support channels guide describes, then track your own figures against them over time. A fast first reply is only useful if it moves the problem towards a resolution, so read it beside repeat contacts.

Should support agents be given targets on handle time?

Handle time pressure tends to produce short contacts that do not solve the problem, which come back later as repeat contacts and complaints. If handle time is tracked at all, read it for the team and by contact reason, to spot reasons that take long because a process or page is broken, and pair it with repeat contacts and quality review. It works better as a diagnostic than as a target for individuals.

Terms used on this page

Frameworks

Where this page is used

Also related

Related