Customer Support KPIs: First Response, Resolution and CSAT
The customer support KPIs that matter: first response time, resolution time, first contact resolution, CSAT and backlog, with formulas and a worked example.
· 4 min read · Summarix team
The customer support KPIs that matter most are first response time, resolution time, first contact resolution (FCR), customer satisfaction (CSAT) and backlog. Speed metrics tell you whether customers are waiting too long; quality metrics tell you whether the wait was worth it. Track both, because improving one at the expense of the other is easy and costly.
The core support KPIs and formulas
| KPI | Formula | Why it matters |
|---|---|---|
| First response time (FRT) | Median time from ticket created to first human reply | Customers judge you on how quickly they hear back |
| Resolution time | Median time from ticket created to solved | Total effort and wait for the customer |
| First contact resolution (FCR) | Tickets solved in one reply ÷ tickets solved × 100 | Fewer back-and-forths means happier customers and lower cost |
| CSAT | Positive survey responses ÷ total responses × 100 | Direct measure of how the customer felt |
| Reopen rate | Tickets reopened ÷ tickets solved × 100 | Catches ‘solved’ tickets that were not really solved |
| Backlog | Open tickets at a point in time (and how old they are) | Early warning that demand exceeds capacity |
| Tickets per agent | Tickets solved ÷ agents (per day or week) | Workload and staffing |
| Contact rate | Tickets ÷ orders or active customers × 100 | Whether product or process issues are generating demand |
Worked example: a five-person support team
Say your team received 1,200 tickets in October and solved 1,150. Of the solved tickets, 690 were fixed in a single reply and 46 were reopened. You sent a CSAT survey on every solved ticket and got 380 responses, 323 of them positive. The business processed 9,600 orders that month.
- FCR: 690 ÷ 1,150 = 60%
- Reopen rate: 46 ÷ 1,150 = 4%
- CSAT: 323 ÷ 380 = 85%
- Tickets per agent: 1,150 ÷ 5 = 230 a month, or roughly 11 per working day
- Contact rate: 1,200 ÷ 9,600 = 12.5% of orders generated a ticket
The most actionable number here is often contact rate. If one in eight orders generates a ticket, look at the top ticket reasons. If a third are ‘where is my order?’, better tracking emails could remove hundreds of tickets a month, which improves every other KPI at once. Tag every ticket with a reason when it is solved, keep the list of reasons short (ten to fifteen), and review the top five each month with the teams who can fix the cause.
Speed KPIs: first response and resolution
Set targets per channel. Customers expect live chat answered in minutes, email within hours, and a formal complaint acknowledged the same day. Measure in business hours if your team is not staffed around the clock, otherwise weekend tickets make Monday look like a disaster. Report the share of tickets meeting target (for example, ‘82% of emails answered within 4 business hours’) alongside the median, because it is easier for everyone to understand.
Quality KPIs: FCR, CSAT and reopen rate
CSAT is simple and useful but has blind spots: response rates are often low, and very happy or very angry customers are more likely to answer. Read the comments, not just the score. Pair CSAT with FCR and reopen rate: if CSAT is high but reopen rate is climbing, agents may be closing tickets too early to look fast.
Capacity KPIs: backlog and workload
Backlog is the most honest capacity metric. Track the number of open tickets and how many are older than your target resolution time. A backlog that grows every week means incoming volume exceeds what the team can solve, and no amount of motivation fixes that. You need fewer tickets (lower contact rate), faster handling (better macros, knowledge base) or more people.
Connect Zendesk or Freshdesk and get a weekly support report with response times, CSAT and top ticket themes written up for you.
Free plan: 5 AI reports a month, no card needed.
A simple weekly support report
- Volume: tickets received and solved, and contact rate.
- Speed: median first response and resolution time, and percentage within target.
- Quality: CSAT, FCR and reopen rate, with two or three verbatim comments.
- Backlog: open tickets and number older than target.
- Top five ticket reasons and one fix to try this week.
If you use Zendesk or Freshdesk, Summarix can connect and produce this report on a schedule, with numbers computed from your ticket data. See our guide to Zendesk and Freshdesk support reports. If much of your support happens by phone, call centre KPIs covers handle time, abandonment and service level, and finding customer complaints in calls shows how to surface themes from conversations.
Conclusion
Good support reporting balances speed, quality and capacity. Watch the median first response and resolution times, check FCR, CSAT and reopen rate together, and keep an eye on backlog and contact rate. The biggest wins usually come from reducing why customers need to contact you in the first place.
Frequently asked questions
What is a good first response time?
It depends on the channel and your customers’ expectations. Live chat is usually measured in minutes and email in hours; set a target per channel and track the share of tickets that meet it.
How do you calculate CSAT?
Divide the number of positive survey responses (for example, 4 or 5 on a five-point scale) by the total number of responses and multiply by 100.
What is first contact resolution?
FCR is the percentage of tickets solved with a single reply or interaction, without the customer having to follow up. Higher FCR usually means lower cost and higher satisfaction.
Should I use average or median response time?
Median is usually better because a few very slow tickets can distort an average. Report the percentage of tickets within target alongside it.