Customer support metrics: what to track and how each is calculated

First response time is the gap between a ticket being created and the first reply from an agent, which is how Zendesk's first reply time metric measures it. It's the first wait a customer experiences, and it's usually the first target teams put into an SLA policy.

Resolution time measures how long it takes to solve the issue. Zendesk's full resolution time runs from creation to the ticket's latest solve, so a ticket that is reopened and solved again keeps accumulating time. Average resolution time is simply the mean of those durations across tickets resolved in a period. A handful of very old tickets can pull an average up sharply, so it's worth looking at the median alongside it.

Two settings change these numbers a lot: whether you count business hours or calendar hours, and whether automatic replies count as a response. Decide once, write it down and keep it stable, so trends stay comparable from month to month.

First contact resolution (FCR) is the share of issues solved without the customer having to come back. Freshdesk calculates FCR% as the number of tickets resolved or closed after the customer's first contact, divided by all tickets resolved or closed in the selected period. A ticket passes only if the customer sent no further messages after the first one; the initial ticket description doesn't count as a customer reply, and the number of agent replies doesn't matter. Reopened tickets are left out, and so are outbound tickets that an agent started.

Reopens catch the opposite case: a ticket marked solved that comes back. Zendesk records a reopen when a ticket's status moves from Solved back to Open. Watch FCR and reopens together. If your team closes tickets early to hit a resolution target, reopens will rise.

CSAT (customer satisfaction score) asks customers to rate a specific interaction. In Zendesk Explore, the satisfaction score is the number of tickets rated good divided by all tickets with a satisfaction response, shown as a percentage. Because it's tied to one ticket, CSAT is the most direct feedback on your support team's work.

CES (customer effort score) asks how easy it was to get an issue handled. The idea comes from Stop Trying to Delight Your Customers, published in Harvard Business Review in July 2010. It drew on a study of more than 75,000 people who dealt with contact-center representatives or self-service channels, and argued that going above and beyond makes little difference to loyalty, while reducing customer effort does. Survey wording and scales vary between tools, so pick one version and keep it.

NPS (Net Promoter Score) measures willingness to recommend the company, not just one interaction. Fred Reichheld of Bain & Company introduced it in The One Number You Need to Grow, published in Harvard Business Review in December 2003. Customers say how likely they are to recommend the company to a friend or colleague on a 0–10 scale. Scores of 9–10 are promoters, 7–8 are passives and 0–6 are detractors. NPS is the percentage of promoters minus the percentage of detractors, so it ranges from -100 to +100.

Backlog is the unsolved work in front of your team. Zendesk defines the ticket backlog as all tickets currently in New, Open, Pending or On-hold status, both assigned and unassigned. Track it as a daily snapshot so you can see the trend. A backlog that grows week over week means incoming volume is outpacing capacity, even if response times still look fine.

A few habits keep metrics useful:

• Pair a speed metric with a quality metric, such as resolution time with reopens, so one can't improve at the expense of the other.
• Segment by channel and priority. A chat first response and an email first response aren't comparable.
• Keep the same definitions and hours setting over time, and note any change in your reports.
• Turn your most important targets into SLA policies, so the helpdesk tracks them on every ticket.

TascaLab's Automated Reports service ($700, one-time) pulls these metrics from your helpdesk, such as Zendesk, Freshdesk or Jira, and delivers a scheduled summary to email or Slack. Each project includes basic documentation, 30 days of post-launch support and no hidden fees, and most setups take 1–3 weeks. A free 30-minute Health Check call helps decide which metrics are worth automating first.