Connecgen Global

Metrics

Customer Support Metrics: A Complete Guide To What To Measure

Formulas, worked examples and honest limits for every core metric: CSAT, NPS, effort, first contact resolution, response time, handle time, quality and cost. How to pair them, set targets, diagnose problems and write them into a contract.

  • By the Connecgen Global team
  • Published 5 November 2026
  • Updated 12 November 2026
  • Reading time about 40 minutes
  • Jump to the FAQ

Almost every support team tracks numbers. Far fewer know what those numbers really mean, which ones to trust, how to read them together, and how to stop them from quietly changing the behaviour of the people being measured. A dashboard full of green figures can sit on top of unhappy customers. A single red figure can send a good team chasing the wrong problem.

This guide explains customer support metrics from the ground up. You will learn what each metric is, the exact formula, when to use it, how many survey responses you need before a score means anything, what each metric hides, how metrics should be paired, how to set targets when you have no history, and how to diagnose problems from the pattern of your numbers. There are worked examples, charts, a calculator you can use with your own figures, and a glossary of every term at the end.

It is written for support managers, founders who now own a support team, and anyone who has to read a support report or sign a contract that includes service targets.

What Are Customer Support Metrics, and Why Do They Matter?

A metric is a measurement. "We answered 412 chats yesterday" is a number. It becomes useful when it is defined precisely, measured the same way every time, and compared with something: last month, a target, another team, another channel.

Support metrics matter for three reasons that pull in different directions, which is why measurement is harder than it looks.

  1. For customers, metrics are a proxy for whether they were helped quickly, correctly and kindly.
  2. For agents, metrics are a signal of what the organisation values. People do what is measured. If you measure speed, you get speed.
  3. For the business, metrics justify budgets, show where the product causes pain and decide whether to hire, train, automate or outsource.

Leading and Lagging Indicators

Some metrics tell you what has already happened. Others warn you about what is about to happen.

A healthy scorecard has both. If you only watch lagging indicators, you find out about trouble weeks too late. If you only watch leading ones, you may polish activity that does not help customers.

The Four Families of Support Metrics

Most customer support metrics fall into four families. Keeping them in mind stops you from collecting random numbers and helps you notice what you are not measuring.

1. Customer experienceHow did customers feel? CSAT, NPS, effort, complaints.
2. ResolutionWas the problem actually solved? FCR, reopens, time to resolution.
3. SpeedHow fast did we respond and finish? First response, handle time, service level.
4. Quality and efficiencyWas it done right, at what cost? QA score, occupancy, cost per resolved contact.
Figure 1. The four families of support metrics. Use at least one from each so that no single family can mislead you.
Four families of customer support metrics. A good scorecard draws from every family.
FamilyQuestion it answersExamples
Customer experienceHow did customers feel?CSAT, NPS, customer effort score, complaints
ResolutionDid we actually solve the problem?First contact resolution, reopen rate, time to resolution, escalation rate
SpeedHow quickly did we respond and finish?First response time, handling time, wait time, service level, abandon rate
Quality and efficiencyDid we do it right, and at what cost?QA score, occupancy, cost per resolved contact, backlog, attrition

The most common mistake is to over-weight the speed family because it is the easiest to measure from system data. Speed matters, but it is the cheapest to improve in ways that hurt customers: answer faster with a useless reply, close tickets before they are solved, rush calls. The families keep each other honest.

Customer Experience Metrics

These come from asking customers. They are the closest you get to the truth about how support felt, and also the easiest to misread.

CSAT: Customer Satisfaction Score

CSAT measures how satisfied a customer was with a specific interaction. After a chat, call or ticket, you ask a question such as "How satisfied were you with the help you received today?" and offer a scale, most often 1 to 5.

CSAT=Responses scoring 4 or 5All survey responsesx 100
NPS=% promoters (9 to 10) minus % detractors (0 to 6)
CES=Sum of all effort ratingsNumber of responses= average rating
Figure 2. The three experience formulas. CSAT is a percentage, NPS is a difference between two percentages (from -100 to +100), and CES is an average.

A worked example. Suppose 200 customers answered your survey after a support interaction. Their scores were: 5 stars, 90 people; 4 stars, 74; 3 stars, 22; 2 stars, 8; 1 star, 6. The positive responses (4 or 5) number 90 + 74 = 164. So CSAT is 164 divided by 200, or 82%.

Example survey results from 200 responsesColumn chart of 200 survey responses. One star 6, two stars 8, three stars 22, four stars 74, five stars 90. Four and five stars together are 164, or 82 percent.025507510061 star82 stars223 stars744 stars905 starsNumber of responses
Swipe sideways to see the whole figure
Figure 3. Worked example: 200 responses. The 164 who scored 4 or 5 are the positive group, so CSAT is 164 / 200 = 82%. Example numbers.

Choices you must make, and write down.

  • The scale. Five points is common. Some teams use thumbs up or down, a 1 to 10 scale or smiley faces. Changing the scale changes the numbers, so keep it fixed or restart your trend line.
  • What counts as positive. The usual choice is the top two boxes (4 and 5). Counting only 5 gives a much lower figure. Neither is wrong. Be consistent.
  • When you ask. Immediately after the interaction captures a fresh memory but may catch customers before their problem has really been fixed. Asking a day later measures the outcome, but fewer people reply.
  • What you ask about. "How satisfied were you with the agent?" measures the person. "How satisfied were you with the help you received?" measures the outcome. Customers often blame the agent for a policy they dislike. Decide which you want.

What CSAT hides. CSAT only counts people who answered. Very happy and very unhappy customers reply more often than people in the middle. A score based on a small, self-selected sample can be badly off. CSAT also says nothing about customers who gave up and never contacted you again. And it can be pulled around by things outside support's control, such as a price rise or a product outage.

NPS: Net Promoter Score

Net Promoter Score asks one question: "On a scale of 0 to 10, how likely are you to recommend us to a friend or colleague?" It was developed by Fred Reichheld with Bain & Company and Satmetrix, and it measures overall loyalty to a company rather than satisfaction with one interaction.

The NPS scaleEleven boxes from 0 to 10. Scores 0 to 6 are detractors, 7 and 8 are passives and 9 and 10 are promoters. NPS equals the percentage of promoters minus the percentage of detractors.012345678910DetractorsScores 0 to 6Passives7 and 8Promoters9 and 10How likely are you to recommend us to a friend or colleague? (0 = not at all likely, 10 = extremely likely)
Swipe sideways to see the whole figure
Figure 4. The NPS scale. Only promoters and detractors enter the calculation, but passives count in the total.

A worked example. Out of 200 answers, 100 are promoters, 60 are passives and 40 are detractors. Promoters are 50% of the total, detractors 20%. NPS is 50 minus 20, which is +30. Note that NPS is a number between minus 100 and plus 100, not a percentage, and the "+" sign is part of the convention.

Why NPS is easy to misuse in support.

  • It measures the whole relationship (product, price, brand, support), so a support team cannot fully control it.
  • It is often collected on a different schedule (quarterly, after purchase) from support contacts, which makes it a poor measure of one agent or one week.
  • It is very sensitive to sample size. Moving a few customers from passive to detractor swings the score noticeably.
  • Scores differ greatly between industries and countries because of cultural habits in how people use the scale. Comparing yourself with an average from another sector can mislead.

Some companies send a "transactional" NPS survey after support contacts to look at support's effect on loyalty. That is reasonable, as long as you label it as such and do not compare it with a company-wide figure.

CES: Customer Effort Score

Customer Effort Score asks how easy it was for the customer to get their problem solved. A typical form is a statement, "The company made it easy for me to handle my issue", with agreement on a seven-point scale from "strongly disagree" to "strongly agree".

CES rests on an idea supported by customer service research: customers care less about being delighted than about not having to work hard. Repeating information, being transferred, switching channels and waiting for callbacks all increase effort. A support team can lower effort directly, by fixing handovers, improving self-service and solving problems on the first contact.

Use CES after interactions where the customer had a task to complete, such as fixing a problem or changing an account. It is less useful for conversations that are only informational.

CSAT, NPS and CES Compared

The three main experience scores side by side. They answer different questions, so use more than one.
CSATNPSCES
Asks aboutOne interactionThe whole relationshipThe effort of one task
Typical scale1 to 50 to 101 to 7 agreement
Answer to"Were you happy with this help?""Would you recommend us?""Was it easy?"
Best forJudging contacts, coaching, qualityTracking loyalty over timeFinding friction in processes
RespondsFastSlowlyFast
Main riskSmall, self-selected samplesBlamed on support for things it cannot controlMeasuring only simple tasks

If you can only run one survey, run CSAT after the contact and add one optional free-text question: "What could we have done better?" The comments will teach you more than the number.

How Many Responses Do You Need?

This is the question that most guides skip, and it matters more than almost anything else on a survey. A score from a handful of responses is noise.

When you survey a sample of customers and compute a percentage, the true figure for all customers could be a little higher or lower. The size of that uncertainty is the margin of error. For a percentage, a standard approximation at 95% confidence is:

How margin of error shrinks as survey responses growLine chart. Margin of error for a score near 80 percent falls from about 15.7 points at 25 responses to 11.1 at 50, 7.8 at 100, 5.5 at 200, 3.9 at 400, 2.8 at 800 and 2.0 at 1600.048121625501002004008001600Margin of error (percentage points)Number of survey responsesPlus or minus, points200 responses: about5.5 points
Swipe sideways to see the whole figure
Figure 5. Calculated with the standard 95% formula for a result near 80%. Quadrupling the responses only halves the uncertainty, so small gains are costly to prove.

Two lessons follow. First, do not celebrate or panic over small movements in survey scores unless you have many responses. Second, never rank individual agents on a handful of surveys. An agent with 12 responses and an agent with 90 are not comparable. If you must show agent-level scores, show the number of responses beside them and withhold the score below a minimum.

Survey Bias and Response Rates

  • Non-response bias. People who reply differ from those who do not. Encourage replies from everyone: short surveys, one tap, sent promptly.
  • Selection by the agent. If agents decide when a survey is sent, they will send it after the good conversations. Send it automatically, to a random or complete set.
  • Leading wording. "How great was your experience?" pushes answers up. Use neutral wording.
  • Survey fatigue. Asking after every contact annoys loyal customers. Cap how often one person is surveyed.
  • Coaching to the score. Agents who ask "please give me five stars" are measuring their charm, not service. Make this a coaching point.

Try It: Three Core Metrics Calculator

The numbers below are examples. Replace them with your own and the results update as you type. Nothing you enter is sent anywhere.

Customer satisfaction score (CSAT)
Net Promoter Score (NPS)
First contact resolution (FCR)
CSAT-
NPS-
FCR as reported-
FCR with reopens removed-

Resolution and Effectiveness Metrics

Experience scores tell you how customers felt. Resolution metrics tell you whether the problem actually got solved, which is the strongest driver of how customers feel.

First Contact Resolution (FCR)

FCR=Issues resolved at first contactAll issues handledx 100
Reopen rate=Solved tickets that were reopenedAll tickets marked solvedx 100
AHT=Talk + hold + after-contact workContacts handled= minutes per contact
Figure 6. Resolution and handling formulas. The hard part is not the arithmetic but agreeing what counts as resolved.

FCR sounds simple, and it is the metric most often measured badly, because "first contact", "resolved" and "same problem" all need definitions. Here are the four common ways to measure it, from easiest to most accurate.

Four ways to measure FCR. The further down the table, the more reliable, and the more work.
MethodHow it worksWeakness
Agent marks itThe agent ticks "resolved on first contact"Agents are measured on it, so it drifts upwards
Closed with no reopenTicket closed and never reopenedCustomers may simply give up or phone instead
No repeat contact in a set periodNo new contact from the same customer on the same topic within, say, 7 daysNeeds good topic matching, and customers may call about a different topic
Customer confirmsThe customer is asked "Was your issue fully resolved?"Needs survey responses, and some customers do not reply

None of these three figures is dishonest. They measure different things. The danger is mixing them: reporting the agent-marked 78% this month and the stricter 69% next month and seeing a "fall" that never happened. Pick one definition, write it down, and keep it. For contract and board reporting, prefer the stricter ones.

Why FCR matters. Every repeat contact costs money, frustrates the customer and clogs the queue. A support team that improves FCR usually improves satisfaction and lowers cost at the same time, which is rare.

What FCR hides. A team can raise FCR by refusing to escalate when it should, or by closing tickets that were not solved. A high FCR must therefore be read next to the reopen rate and customer satisfaction.

Reopen Rate and Repeat Contact Rate

Reopens are an honest signal, because customers vote with their behaviour. A rising reopen rate points to rushed closing, thin knowledge, poor handovers or incomplete fixes.

Resolution Rate and Time to Resolution

Resolution time is a clock from the customer's point of view, so it includes waiting for the customer to reply. Many teams measure two versions: elapsed time, which includes the waits, and handling time, which counts only active work. Know which one you are quoting.

Escalation Rate

The share of tickets passed up to a higher tier. As covered in our guide to L1, L2 and L3 support, a very high rate points to training or permission gaps, and a very low one may mean agents are hanging on to problems. Always split it by reason.

Backlog and Ticket Age

Look at age, not only count. Ten tickets that are a day old are fine. Ten that are six weeks old are a quiet disaster. Report the oldest ticket and the number older than your promised time.

Speed and Responsiveness Metrics

First Response Time (FRT)

Three traps:

  1. Automatic replies do not count. An auto-acknowledgement is useful but is not a response. Count the first reply from a person that moves the case forward.
  2. Averages mislead. A few very long waits drag an average up, and a flood of instant replies drags it down. Use the median (the middle value) and a percentile (for example, "90% of customers get a first reply within X").
  3. Business hours versus clock hours. A reply to a message sent at midnight is quick if your clock starts at nine the next morning, and slow if the customer was awake. State which you use.

Average Handle Time (AHT)

AHT is useful for staffing: more minutes per contact means more agents needed. It is risky as a performance target, because a lower AHT is not better by itself. Agents who feel timed will rush, avoid asking the question that would reveal the real problem, or end contacts before they are solved, and repeat contacts rise. Use AHT to plan capacity and to find process problems (a step that makes every contact slow), not to rank people.

Service Level, Wait Time and Abandon Rate (Voice and Live Chat)

These matter for live channels, where the customer is waiting right now. Service level is more informative than ASA because it tells you what share of customers got an acceptable wait.

Why staffing is not a straight line. Here is a result that surprises many managers. Suppose a phone line receives 120 calls an hour and each call takes 4 minutes of agent time. That is 8 hours of work arriving every hour, which queueing theory calls a workload of 8 "Erlangs". You might guess that 8 agents are enough. They are not, because calls arrive at random and queues form whenever the next call finds everyone busy. A standard queueing formula called Erlang C estimates how many agents you need for a given service level. Using it for this example:

Service level and occupancy as agents are addedLine chart for 120 calls an hour at 4 minutes each. With 9 agents about 40 percent of calls are answered within 20 seconds, with 10 agents 65 percent, 11 agents 81 percent, 12 agents 90 percent and 16 agents 99.5 percent. Occupancy falls from 89 percent at 9 agents to 50 percent at 16.0255075100910111213141516Calls answered within 20 seconds (%)Agent occupancy (%)Agents on dutyPer cent9 agents: about 40% in20 seconds11 agents: about 81%
Swipe sideways to see the whole figure
Figure 7. Calculated example using the Erlang C formula: 120 calls an hour, 4 minutes per call, 20-second target. It ignores breaks and leave, so real rosters need more people.

Notice three things. With 10 agents, service falls to about 65% answered within 20 seconds. With 9, it collapses to about 40%. Going from 11 to 12 agents helps a lot, but going from 14 to 16 hardly changes the result. Being one agent short can be far worse than being one agent over, and each extra agent after the first few has less effect than the one before.

Contact Rate

Contact rate is one of the most valuable measures a support lead can give to the rest of the company. If contacts per 100 orders rise after a product change, support is telling you that something confusing or broken was shipped.

Quality Assurance (QA) Scores

Surveys tell you what customers thought. Quality assurance tells you whether the conversation met your standards, whether or not the customer filled in a survey. It is done by reviewing a sample of conversations against a scorecard.

A typical scorecard rewards:

  • Accuracy: correct information, correct steps, correct policy.
  • Resolution: the problem was solved or properly escalated.
  • Process and compliance: identity checks, required statements, correct notes.
  • Communication: clarity, tone, empathy, plain language.
  • Ownership: next steps clearly stated, customer left informed.

Some items are critical (an "auto-fail"): giving wrong financial information, breaking a privacy rule, being rude. A single critical failure should fail the whole review no matter how good the rest was.

Sampling. Review a random sample across agents, channels, times of day and contact types, plus extra samples of escalations, complaints and new starters. Reviewing only the "best" or "worst" conversations distorts the picture.

Calibration. Two reviewers can score the same conversation differently. Calibration sessions, where reviewers score the same contacts and compare, keep scoring consistent. Without them QA scores say more about the reviewer than about the agent.

Fairness. Share the scorecard in advance, explain it, let agents see their reviews and challenge them, and use QA to coach rather than punish. Our quality and compliance support service covers this work in more detail.

Efficiency, Capacity and Cost Metrics

Cost Per Contact Versus Cost Per Resolved Contact

This is why in-house or outsourced customer support comparisons should always use cost per resolved contact, not cost per hour.

Metrics That Keep Each Other Honest: Pairing Rules

Every metric has a cheap way to improve it that hurts customers. The defence is to pair each metric with its counter-metric.

Pair every speed or volume metric with a quality metric. A rise in one with a fall in its pair is a warning.
If you push thisPeople may do thisPair it with
Faster first responseSend empty replies to stop the clockResolution time, CSAT, reply quality in QA
Lower handle timeRush calls, skip checksFCR, repeat contact rate, QA accuracy
Higher FCRClose tickets early, avoid escalatingReopen rate, CSAT, escalation quality
Higher CSATAsk for five stars, send surveys after good calls onlySurvey coverage, response counts, QA
Fewer escalationsHold on to problems too longTime to resolution, customer effort
More tickets closedSplit one problem into many, close without fixingReopen rate, resolved-by-customer-confirmation
Lower cost per contactUnderstaff, cut trainingCost per resolved contact, attrition, QA
Speed versus qualityA two by two grid. Horizontal axis is speed, vertical axis is quality. Top right is fast and careful, the aim. Bottom right is fast but careless, which speed-only targets tend to produce.Careful but slowFast and careful: theaimSlow and carelessFast but careless:rushingWhere to aimWhat speed-only targets produceOver-cautious teamsSpeed (faster to the right)Quality (better upward)
Swipe sideways to see the whole figure
Figure 8. Speed-only targets push teams towards the bottom right. Pairing speed with quality measures keeps them aiming for the top right.

How to Set Targets When You Have No Benchmark

New teams ask: "What is a good CSAT?" or "What FCR should we aim for?" The honest answer is that published figures come from many different definitions, industries and customer mixes, so they are shaky. A better path is to build your own baseline.

  1. Define each metric exactly, in writing, with the formula, the data source and what counts as in or out.
  2. Measure for four to eight weeks without targets. You will learn the normal range and find data problems.
  3. Look at the distribution, not only the average: best and worst weeks, differences between channels, priorities and teams.
  4. Set three levels: a floor (below this, we act), a target (where we aim to be) and a stretch (excellent). Targets are usually set a little above your normal range, not far above it.
  5. Set targets by channel and priority. A chat target should not equal an email target, and a critical issue should not share a target with a how-to question.
  6. Review quarterly. When a metric is comfortably met for several periods, raise it or move your attention to the next constraint.
  7. Use external benchmarks as context only, after checking that their definitions match yours.

Building a Scorecard and Dashboard

The aim of a scorecard is to let someone understand the health of support in two minutes. Fewer, better chosen numbers beat a wall of charts.

One page per audience.

  • Executives: five or six numbers with trend arrows: CSAT, FCR, time to resolution, cost per resolved contact, contact rate, and one line on risks.
  • Support leaders: the above, plus backlog age, QA, escalation reasons, staffing and service level.
  • Team leads and agents: their own QA and customer comments, response counts, coaching notes, and team trends.

Cadence. Daily for queue health (backlog, service level, oldest ticket). Weekly for quality and trends. Monthly for scorecards and contract reviews. Quarterly for targets and definitions.

CSAT84%
612 responses, margin about 3 points. Up 1 point.
FCR (customer confirmed)71%
Reopens within 7 days: 6%.
First response9 min
Median. 90th percentile: 42 min.
Time to resolution5.2 h
Median, business hours. Oldest open: 6 days.
Contact rate4.1
Contacts per 100 orders. Down from 4.6.
QA score91%
120 reviews, 2 critical fails.
Figure 9. An example one-page scorecard layout. Every number here is made up to show the format: each figure carries its sample size, its definition and a counter-measure.

Dashboard hygiene.

  • Show the definition next to each number, or one click away.
  • Show sample sizes beside every survey score.
  • Use trend lines over a few months, not single-month bars.
  • Use medians and percentiles for time measures.
  • Always include comments. Numbers say what happened. Customers' own words say why.

Metrics by Channel

Different channels need different emphasis. Do not hold email to a phone target or the reverse.
ChannelMost useful speed measureResolution measureExperience measure
PhoneService level, wait time, abandon rateFCR, repeat contactsCSAT, CES
Live chatWait time, first response, concurrent chats per agentFCR, chat reopenCSAT
EmailFirst response (median, percentile)Time to resolution, touches per ticketCSAT, comments
Social mediaFirst response, time to move to private channelResolution rateSentiment, CSAT
Self-serviceSearch success, time to find an answerContacts avoided, article helpfulnessEffort, feedback

Reading the Pattern: Five Worked Diagnoses

The real skill is not calculating metrics but reading them together. Here are five patterns that appear again and again, with the questions to ask before you act. In each case, treat the explanation as a hypothesis to test by reading real tickets, not as a verdict.

Pattern 1: Satisfaction Is Falling but First Contact Resolution Is Flat

What it might mean. Customers are getting problems solved at about the same rate, but they are less happy. Look for changes in how they are treated or what they are asked to do: a new policy customers dislike, a tone change after a script update, longer waits that do not show up in FCR, a new self-service step that adds effort, or a product change that makes customers more anxious.

What to check. Read the low-score comments from the last two weeks and tag them by theme. Compare CSAT by contact reason, by channel and by wait time. Check whether CES moved.

Pattern 2: Handle Time Fell and Satisfaction Fell Too

What it might mean. Agents are rushing. A well-run change (better tools, a better knowledge base) lowers handle time without hurting satisfaction. If both move, the saving probably came from shortcuts.

What to check. QA scores for "discovered the real issue" and "explained next steps". Repeat contact rate within seven days. Whether a new target or league table on handle time was introduced.

Pattern 3: First Response Time Is Excellent but Resolution Takes Longer Every Month

What it might mean. The team is working to the clock that is measured. Replies go out fast but do not move the case forward ("We are looking into this"), and the real work waits. It can also mean complexity is rising or the escalation route is slowing down.

What to check. Number of touches per ticket. Time spent waiting in escalation queues. The share of first replies that ask for information already in the ticket. Whether a first-response target exists without a matching resolution target.

Pattern 4: NPS Rose, CSAT Fell

What it might mean. The two answer different questions. NPS may have risen because of a product release, a price change or a marketing campaign, while the support experience got worse. Or the samples differ: NPS surveyed a broad base, CSAT only people who contacted support.

What to check. The survey populations and dates. Whether anything outside support changed. Whether support-driven NPS (asked after contact) tells the same story as CSAT.

Pattern 5: the Escalation Rate Jumped

What it might mean. A new product release with undocumented behaviour, a gap in the knowledge base, a new batch of untrained agents, a change in what L1 is allowed to do, or a genuine incident.

What to check. Escalation reasons split by week. The ticket subjects that make up the jump. Whether a product or policy change shipped the week before. Whether the notes quality changed.

Metrics When You Outsource Support

Outsourcing makes measurement more important, not less, because the people doing the work are no longer in the next room. Three things matter most: agreeing definitions, separating targets from penalties, and seeing the data yourself.

Write the Formula Into the Contract

Most disputes over service targets come from two parties meaning different things by the same word. A good agreement defines each metric with its exact formula, the data source, the time zone, what is excluded (for example, contacts caused by an outage you declared) and who calculates it.

SLA, KPI and Service Credit: Three Different Things

Different jobs for different measures. Mixing them up leads to arguments.
TermWhat it isTypical use
SLAA promised minimum level of serviceResponse and resolution times, availability
KPIAn important measure tracked over timeCSAT, FCR, QA score
Service creditAn agreed reduction in fees when an SLA is missedCompensation, and an incentive to stay on target

Where possible, make SLAs few and clear and keep KPIs for improvement conversations. A contract that punishes every missed number encourages a vendor to hide problems. A contract that mixes a few firm commitments with joint reviews of the wider KPIs encourages honesty. Note that incentives and penalties differ between businesses and should be agreed with your own advisers.

See the Data Yourself

Ask for read access to the helpdesk and survey data, not only a monthly spreadsheet. Agree a shared dashboard, a weekly operational review and a monthly business review. Agree who will run calibration sessions on QA, so that the partner's reviewers and yours score the same way.

Questions to Ask a Partner About Metrics

  1. Which definitions do you use for first response, resolution and FCR? Can we agree ours in the contract?
  2. How do you sample for quality, and how often do you calibrate with us?
  3. How do you stop agents gaming scores? What pairs of metrics do you watch?
  4. What will we see, how often, and can we see raw data?
  5. How do you report problems early, before the monthly review?
  6. What happens to targets in the first ninety days? (See our 90-day transition plan.)

Our guide on how to choose a support outsourcing partner goes into evaluating reporting and governance, and our quality and compliance support and customer care pages describe how we run scoring, calibration and reporting for clients.

Ten Common Mistakes (And Their Fixes)

  1. Changing definitions mid-stream. Fix: version your definitions, and restart trend lines when you change them.
  2. Reporting averages for time. Fix: median and a percentile, plus the worst case.
  3. Scoring agents on tiny samples. Fix: show response counts and set a minimum before showing a score.
  4. Measuring only what is easy. System data is easy; customer truth is harder. Fix: add surveys, QA and comment review.
  5. One target for every channel and priority. Fix: set targets per channel and per priority.
  6. Treating CSAT as a performance rating. Fix: use it for coaching conversations and trend, not league tables.
  7. No counter-metric. Fix: pair each speed or volume number with a quality one.
  8. Ignoring the comments. Fix: tag them, count themes and act on the top three.
  9. Blaming support for company-wide problems. Fix: split metrics by contact reason and feed product issues to product teams.
  10. Reporting without acting. Fix: every review ends with named owners, actions and a date.

A 60-Day Plan to Fix Your Measurement

Days 1 to 10: define. List every metric you report. Write the formula, data source and owner for each. Cut anything nobody uses. Choose one definition of FCR and write it down.

Days 11 to 25: collect. Turn on automatic, complete CSAT surveys with a free-text box. Start a weekly QA sample with a simple scorecard. Record the baseline for each metric by channel.

Days 26 to 40: pair and calibrate. Add counter-metrics. Run the first calibration session. Review twenty tickets behind every metric that moved.

Days 41 to 55: set targets. Set floor, target and stretch from your baseline, per channel and priority. Share them with the team, explaining what each is for and what it is not for.

Days 56 to 60: publish and review. Publish the one-page scorecard. Hold the first monthly review with named owners. Schedule the quarterly definition review.

A 60-day plan to fix measurementFive horizontal bars across 60 days: define metrics in days 0 to 10, collect and baseline from 10 to 25, pair and calibrate from 25 to 40, set targets from 40 to 55, and publish and review from 55 to 60.0102030405060Define metricsCollect and baselinePair and calibrateSet targetsPublish and reviewdays
Swipe sideways to see the whole figure
Figure 10. The 60-day plan on a timeline. Each phase has one clear output.

Putting It All Together

Customer customer support metrics are a language for talking about service. Used well, they show whether customers are being helped, where effort is wasted and where to invest. Used badly, they become a game that people win and customers lose.

The core ideas:

  • Define every metric precisely and keep the definition stable.
  • Use all four families: experience, resolution, speed and quality with efficiency.
  • Respect sample size. A survey score from a handful of responses is noise.
  • Pair speed with quality. Every shortcut has a counter-metric that exposes it.
  • Measure resolution honestly. Prefer customer confirmation and repeat contact over agent opinion.
  • Read tickets, not only charts.
  • Put definitions and data access into any outsourcing contract.
Written by the Connecgen Global team.

We run customer support and sales support for businesses, so we write from the day-to-day work. This guide is general information, not legal, financial, medical or compliance advice. Rules differ by country and change, so check what applies to you with your own advisers. We list our sources at the end. If you spot something out of date, write to info@connecgen.com.

Frequently Asked Questions

42 direct answers to the questions readers ask most about this topic. Tap a question to open it.

The Basics

What are customer support metrics?

Customer support metrics are measurements of how well a support team serves customers. The core set covers experience (CSAT, NPS, effort), resolution (first contact resolution, reopen rate), speed (first response, handle time, service level), quality scores and efficiency (cost per resolved contact).

What are the most important customer support metrics?

If you can only track a few, choose CSAT for quality, first contact resolution for effectiveness and first response time (median and 90th percentile) for speed. Add reopen rate and cost per resolved contact as counter-measures.

What is the difference between a metric and a KPI?

A metric is any defined measurement. A KPI is a metric you have chosen as a key sign of whether you are reaching a goal. A team may track dozens of metrics and treat only a handful as KPIs.

What is the difference between a KPI and an SLA?

A KPI is a measure you track to improve over time. An SLA is a written commitment to a minimum level of service, often with consequences if missed. Few, clear SLAs and a wider set of KPIs usually works best.

What is a leading indicator in support?

A measure that tends to move before results do, such as backlog age, first response time or QA pass rate. A lagging indicator, such as monthly satisfaction, reports what has already happened.

How many metrics should a support team track?

Report five or six on the executive page, and perhaps fifteen in total across the team. Define every one precisely, and drop any metric nobody uses to make a decision.

CSAT, NPS and Effort

What is CSAT and how is it calculated?

CSAT is the share of survey responses that are positive after an interaction, usually the top two boxes on a five-point scale. Formula: responses scoring 4 or 5, divided by all responses, times 100.

What is a good CSAT score?

It depends on your industry, scale, survey timing and customer mix, so published averages are shaky. Build your own baseline over four to eight weeks, then set a floor, target and stretch from it.

What is NPS and how is it calculated?

NPS asks how likely customers are to recommend you on a 0 to 10 scale. It equals the percentage of promoters (9 and 10) minus the percentage of detractors (0 to 6), giving a number from minus 100 to plus 100.

What is the difference between CSAT and NPS?

CSAT measures satisfaction with one interaction. NPS measures loyalty to the whole company. CSAT moves quickly and suits coaching. NPS moves slowly and suits long-term tracking.

What is Customer Effort Score (CES)?

CES measures how easy it was for a customer to solve an issue, often as agreement with a statement on a seven-point scale. It helps find friction in processes such as transfers and repeated questions.

How many survey responses do I need?

More than you think. With 200 responses, a score near 82% is only accurate to about 5 points either way. With 50 it is about 11 points. Do not react to small movements or rank agents on a handful of surveys.

Can I use CSAT to rate individual agents?

Only with care. Agent-level samples are small, and customers often blame agents for policies. Show response counts, set a minimum sample, and use scores for coaching conversations rather than league tables.

Why is my survey response rate low?

Surveys that are long, sent late, or ask too often get ignored. Keep it to one question plus an optional comment, send it straight after the contact, and cap how often one customer is asked.

Resolution and Speed

What is first contact resolution?

FCR is the percentage of issues fully resolved at the first contact, with no follow-up, transfer or repeat contact about the same problem. Formula: issues resolved at first contact divided by all issues, times 100.

Why is FCR hard to measure?

Because 'resolved', 'first contact' and 'same problem' need definitions. Agent-marked FCR drifts upwards. The more reliable methods use repeat contact within a window, or customer confirmation.

What is a good first contact resolution rate?

Published rules of thumb exist but rest on different definitions. Define it strictly, measure it for a few weeks, and aim to improve your own number while watching reopen rate and satisfaction.

What is first response time?

The time between a customer contacting you and a person giving a first meaningful reply. Automatic acknowledgements do not count. Report the median and a percentile, not just the average.

Why shouldn't I use averages for response times?

A few very long waits drag an average up, and a flood of fast replies drags it down. Medians and percentiles show what a typical customer and the unluckiest customers experienced.

What is average handle time (AHT)?

The average time an agent spends on one contact, including talk or typing, hold time and after-contact work. It is useful for staffing, but a lower AHT is not automatically better because rushing raises repeat contacts.

What is service level in a contact centre?

The percentage of contacts answered within a target time, written like 80/20, meaning 80% answered within 20 seconds. It is more informative than average wait because it shows how many customers got an acceptable wait.

What is abandon rate?

The percentage of customers who hang up or leave a chat before an agent answers. A rising abandon rate usually means understaffing at certain times of day.

What is occupancy?

The share of logged-in time an agent spends handling contacts. Very high occupancy leaves no slack and risks burnout and errors, while very low occupancy suggests overstaffing.

What is contact rate?

Contacts relative to your customer base or orders, for example per 100 orders. A rising contact rate after a product change tells you something confusing or broken was released.

Quality, Targets and Reporting

What is a QA score in customer support?

The result of reviewing a sample of conversations against a scorecard covering accuracy, resolution, compliance, communication and ownership, shown as a percentage of available points. Critical failures can fail a review outright.

What is calibration?

A session where reviewers score the same conversations and compare results so that scoring is consistent. Without it, QA scores reflect the reviewer as much as the agent.

How do I set targets without benchmarks?

Define each metric, measure for four to eight weeks, look at the distribution, then set a floor, target and stretch a little above your normal range, separately for each channel and priority.

What is Goodhart's law?

When a measure becomes a target, it stops being a good measure. Pair every speed or volume metric with a quality counter-metric so shortcuts show up.

How often should I report support metrics?

Daily for queue health, weekly for quality and trends, monthly for scorecards and contract reviews, and quarterly for targets and definitions.

What should be on a support dashboard?

Few, well defined numbers with sample sizes and trends: CSAT, FCR, median and percentile response and resolution times, backlog age, QA score, contact rate and cost per resolved contact, plus customer comments.

What is cost per resolved contact?

Total support cost divided by issues actually solved. It is more honest than cost per contact, because repeat contacts add cost without adding resolutions.

Which metrics should I check first when satisfaction drops?

Read the low-score comments and split CSAT by contact reason, channel and wait time. Check first contact resolution, reopen rate, customer effort and any recent policy, tool or product change.

Outsourcing and Metrics

What metrics should I put in an outsourcing contract?

A few clear SLAs, usually first response and resolution times per priority, plus KPIs such as CSAT, FCR and QA score. Define each with an exact formula, data source, time zone and exclusions.

Should I penalise a partner for missed targets?

Few firm SLAs, possibly with agreed service credits, can work. Penalising every missed KPI can encourage hiding problems. Agree the structure with your own advisers and add joint reviews.

Should I have access to the partner's raw data?

Yes, where possible. Ask for read access to the helpdesk and survey data, and a shared dashboard, so you do not depend on a monthly spreadsheet.

How do I know a partner is not gaming the numbers?

Pair metrics, sample conversations yourself, run joint QA calibration, check reopen and repeat contact rates, and read tickets behind any chart that looks too good.

What metrics should I expect in the first 90 days of outsourcing?

Expect reduced volumes, daily reviews and relaxed targets that tighten as the team learns. See our 90-day transition plan.

Working With Connecgen

How does Connecgen report on support?

We agree definitions with you in writing, report weekly on volumes, resolution, escalation reasons and quality, and share the context behind the numbers, including problems we find early.

Do you score and review conversations?

Yes. We review a sample of conversations against a scorecard we agree with you, calibrate with your team and use the results for coaching.

Can I see your data?

We can work in your systems so you see the same data we do, and agree a shared dashboard and review rhythm.

How big can a team be?

From a single seat to as many as 100 agents, growing in steps as results are proven.

How do I start?

Use the form on this page or write to info@connecgen.com. We reply within one business day and propose a small supervised pilot.

Glossary of Terms

Every term explained in this guide, in one place.

Abandon Rate
The percentage of customers who hang up or leave the chat before an agent answers.
Adherence
How closely agents follow their planned schedule (log in on time, take breaks when planned). Useful for live channels, harmful if turned into a stick.
AHT (Average Handle Time)
The average time an agent spends on one contact, including talk or typing time, hold time and after-contact work such as notes. Formula: (total talk time + hold time + after-contact work) divided by number of contacts handled.
ASA (Average Speed Of Answer)
The average time customers wait before an agent answers.
Attrition
The rate at which agents leave the team. High attrition is expensive: every leaver takes knowledge with them and every new starter takes weeks to reach full speed.
Backlog
The number of tickets open and waiting for action at a point in time. A backlog that is growing means incoming work is outpacing capacity.
Benchmark
A comparison value from outside your own history, such as an industry average. Benchmarks are useful but dangerous, because companies define metrics differently. We return to this below.
CES (Customer Effort Score)
A measure of how easy it was for a customer to get an issue resolved. It is usually reported either as the average rating or as the share of customers who agreed or strongly agreed.
Concurrency
The number of chats an agent handles at the same time. Higher concurrency lowers cost but can lower quality. Set a cap and watch CSAT.
Contact Rate
The number of support contacts relative to the size of your customer base or orders, for example contacts per 100 orders. It shows whether support demand is growing faster than the business.
Cost Per Contact
Total support cost for a period divided by the number of contacts handled.
Cost Per Resolved Contact
Total support cost divided by the number of issues actually solved. Because repeat contacts add cost without adding resolutions, this is the more honest measure.
CSAT (Customer Satisfaction Score)
The percentage of survey responses that are positive, usually the share scoring 4 or 5 on a five-point scale. It measures satisfaction with one specific interaction.
Erlang C
A standard formula from queueing theory used to estimate how many agents are needed to answer a given share of calls within a target time, given the number of calls and how long each takes. Real planning adds breaks, leave and variations through the day.
FCR (First Contact Resolution)
The percentage of customer issues that are fully resolved during the first contact, without the customer needing to follow up, be transferred or contact you again about the same problem.
First Response Time
The time between a customer contacting you and a person giving a first meaningful reply. For voice it is wait time; for email, chat and social it is the time to the first human answer.
Goodhart's Law
A rule of thumb from economics: when a measure becomes a target, it stops being a good measure. People find ways to hit the number that do not serve the goal behind it.
KPI (Key Performance Indicator)
A metric chosen as an important sign of whether you are reaching a goal. Not every metric is a KPI. A team might track forty metrics and treat five as KPIs.
Lagging Indicator
A measure of results that have already occurred, such as customer satisfaction last month or customers who cancelled. Reliable, but slow.
Leading Indicator
A measure that tends to move before results do, such as backlog age, first response time or the share of conversations that pass a quality review. Less certain, but early.
Margin Of Error
A range around a survey result within which the true value probably lies. For a percentage p from n responses, the 95% margin is roughly 1.96 times the square root of p times (1 minus p) divided by n. More responses mean a smaller margin.
Metric
A defined, repeatable measurement of something that matters, such as the share of customers who say they were satisfied.
NPS (Net Promoter Score)
The percentage of promoters (scores 9 and 10) minus the percentage of detractors (scores 0 to 6). Passives (7 and 8) count in the total but not in either group. The result runs from minus 100 to plus 100.
Occupancy
The share of logged-in time an agent spends actually handling contacts. In the example, 11 agents give an occupancy of about 73%. Very high occupancy (above roughly 85 to 90%) leaves no slack and is a recipe for burnout and errors.
QA (Quality Assurance) Score
The result of reviewing a sample of contacts against a defined scorecard, usually reported as a percentage of available points.
Reopen Rate
The percentage of tickets marked solved that the customer later reopens, usually within a set window such as seven days.
Repeat Contact Rate
The percentage of customers who contact you again about the same issue within a set window. It is the mirror image of FCR.
Resolution Rate
The percentage of all tickets that are solved (not abandoned, merged or left open) in a period. FCR looks only at the first contact. Resolution rate looks at the end result however many contacts it took.
Service Level
The percentage of contacts answered within a target time, written like "80/20" meaning 80% answered within 20 seconds. The thresholds are your choice.
Shrinkage
The share of paid time when agents are unavailable for contacts because of breaks, training, meetings, leave and sickness.
SLA (Service Level Agreement)
A written commitment about service, such as "first reply within one hour for urgent issues", often with consequences if it is missed. Used between a company and a customer, or between a company and an outsourcing partner.
Target
The value you aim for on a metric, for example "at least 85% of survey responses are positive". A target without a clear definition of the metric is just a hope.
Time To Resolution
The elapsed time from when a ticket is created until it is solved. Report it per priority and per channel, not as one average.
Touches Per Ticket
The number of agent replies or actions needed to resolve a ticket. Fewer touches usually means less effort for the customer.

Sources and Further Reading

These pages explain how satisfaction, loyalty and uncertainty are measured. Read them alongside your own data and definitions.

  1. Measuring user satisfactionGOV.UK Service Manual. Practical guidance from the UK government on measuring satisfaction, including asking an open question about how to improve.
  2. Introducing the Net Promoter SystemBain & Company. The firm behind the Net Promoter approach explains promoters, passives and detractors and how the system is used.
  3. Stop Trying to Delight Your CustomersHarvard Business Review. The 2010 article behind the customer effort idea: reducing effort matters more for loyalty than delight.
  4. Margin of errorWikipedia. Background on how sample size affects the uncertainty of survey results.
  5. Erlang (unit)Wikipedia. Background on the Erlang unit and the queueing formulas used to plan call centre staffing.

Links open third-party websites. We list them as reference points. They are not certifications we hold, endorsements of our service or legal advice.

Keep Reading

Why Partner With Us

Reporting That Tells You the Truth

Good numbers are only useful if you trust them. We agree definitions in writing, share the data behind every report and tell you early when something is off.

Team member reviewing performance dashboards on a screen

Ask About Reporting No pressure. Tell us about your goals and we will suggest a sensible starting point for your customer support metrics.

Definitions In Writing

Each metric gets an exact formula, data source and owner.

Built On Live Experience

We run live support and sales conversations ourselves.

From One Seat To A Squad

Start with a pilot and grow to a team of up to 100 agents.

Fair Quality Reviews

Sampled conversations, shared scorecards and calibration with your team.

Shifts For Your Customers

Hours planned around your customers. UK and Ireland shifts are live.

Open Data

We work in your systems so you see what we see.

Talk To Us

Ask Us About Support Reporting

Tell us what you track today and what you wish you could see. We will suggest metrics, definitions and a simple way to report on them.

  • 1We Read Every EnquiryA member of our team reviews your message and replies, aiming for within one business day.
  • 2A Short ConversationWe learn about your customers, products, channels and goals, and answer your questions openly.
  • 3A Clear Written OutlineYou receive a proposed scope, team structure, reporting approach and plan to review.
info@connecgen.com

Tell Us About Your Support Needs

A few details are enough to begin. We will respond personally.

Your details are used only to respond to your enquiry. Please do not include card numbers, passwords or other sensitive information in this form.