Customer Support Metrics That Matter: FRT, Resolution Time, CSAT

You can't improve what you don't measure, but you also don't need a wall of dashboards. Most support teams can run on a handful of numbers, as long as they're the right ones and calculated the right way.

This guide covers the 8 customer support metrics that matter, how to calculate each one, the most common mistakes (like averaging response times), and what actually moves each number.

The 8 metrics at a glance

If you only track four, track first response time, resolution time, CSAT and open tickets.

1. First response time (FRT)

First response time is how long a customer waits between sending a request and getting the first reply from a person.

How to calculate it: for each ticket, take the time of the first agent reply minus the time the ticket was created. Then report the median across all tickets in the period.

A few rules make the number honest:

• Automatic acknowledgements don't count. "We got your message" is useful, but it doesn't answer anything.
• Decide on business hours or calendar hours. If your team works Monday to Friday, a ticket sent on Saturday shouldn't count as a 48-hour wait. Whichever you choose, use it consistently.
• Use the median, not the average. See the example below.

Why the median beats the average

Imagine five tickets this week with these first response times:

The average is 12 hours. The median is 2 hours. Four out of five customers waited 3 hours or less, so the median describes their experience much better. Track the slow ones separately with the 90th percentile, the time within which 90% of tickets got a reply.

How to improve it:

• Make sure every ticket has an owner fast, so nothing waits in an unassigned pile.
• Use views like "open and unassigned" or "oldest first" so the longest waits are always visible.
• Prepare saved replies for the questions you answer every week.
• Publish help articles for the most common questions, so some customers never need to write.

2. Resolution time

Resolution time (or time to resolution) is how long it takes from the moment a customer writes until the request is resolved.

How to calculate it: time the ticket was marked resolved minus the time it was created, reported as a median. Many teams also track it by priority or topic, since a password reset and a billing dispute aren't comparable.

Keep in mind: time spent waiting for the customer counts too. If your team asks a question and the customer replies three days later, resolution time grows even though your team was fast. Looking at FRT and resolution time together tells the full story.

How to improve it:

• Ask for everything you need in the first reply, so you don't go back and forth.
• Use a pending status while you wait for the customer, so the queue shows only what needs your action.
• Escalate quickly when a ticket needs another team, instead of letting it sit.
• Close stale tickets automatically after a period without a reply from the customer.

3. Customer satisfaction (CSAT)

CSAT measures how customers felt about the help they received, usually with a one-question survey sent after a ticket is resolved: "How would you rate the support you received?"

How to calculate it: on a 1 to 5 scale, the most common formula is:

CSAT = (number of 4 and 5 ratings ÷ total responses) × 100

So 45 positive ratings out of 50 responses is a CSAT of 90%. Some teams report the average rating instead (for example, 4.6 out of 5). Either works, as long as you don't switch between them.

Read the comments, not just the score. The comment field tells you why a customer was happy or unhappy. Low ratings are often about the product or a policy, not the agent, and those are worth sending to the rest of the company.

How to improve it:

• Reply faster and set clear expectations ("we'll update you by Thursday").
• Solve the problem in as few replies as possible.
• Write like a person, not a policy.
• Follow up on every low rating with a short personal message.

Watch the response rate. If only a few customers answer the survey, the score can swing a lot from week to week. One-click ratings directly from the email get more responses than long forms.

4. Open tickets (backlog)

Open tickets are the requests currently waiting on your team. It's the simplest health check you have: if the backlog grows week after week, demand is outpacing your team.

How to read it: look at the trend, not the single number. Split it by status: tickets open (waiting on you) are what matter; pending tickets are waiting on the customer.

5. Unassigned tickets

Unassigned tickets are open requests that nobody owns yet. In a healthy queue, this number is close to zero most of the day. A growing pile of unassigned tickets is usually the first sign that first response times are about to get worse.

6. Ticket volume

Ticket volume is how many tickets you receive per day or week. On its own it's just a number, but broken down it becomes one of the most useful things you can know:

• By day and hour, to plan who's available when.
• By channel (email, forms, help center), to know where customers reach you.
• By tag or topic, to find the questions that should become help articles or product fixes.

If one topic keeps growing, fixing the root cause is worth more than answering it faster.

7. Replies per ticket

Replies per ticket is the average number of agent replies needed to resolve a ticket. Fewer replies usually means clearer answers and a better experience. A related metric is the one-touch resolution rate: the share of tickets resolved with a single reply.

How to improve it: answer every question in the customer's message, ask for all the details you need at once, and include links to step-by-step articles.

8. Reopen rate

Reopen rate is the share of resolved tickets that the customer reopens, usually by replying "it's still not working". A high reopen rate means tickets are being closed before the problem is really solved, often to make other metrics look good.

Reopen rate = (reopened tickets ÷ resolved tickets) × 100

Metrics to be careful with

Some numbers look useful but push teams in the wrong direction when they become targets:

• Tickets closed per agent. It rewards closing fast over solving well, and punishes the people who take the hardest tickets.
• Average handle time on its own. Shorter isn't better if the customer has to write back.
• CSAT without a response rate. Five responses don't tell you much.

Use them as context, never as the only goal.

How to set targets

Published benchmarks for response times and CSAT vary widely by industry, channel and source, so copying someone else's number rarely helps. A more reliable approach:

1. Measure your baseline for four weeks: median FRT, median resolution time, CSAT and open tickets.
2. Set a target slightly better than your baseline, for example a 20% faster median FRT next quarter.
3. Promise customers what you can keep. If your median FRT is 3 business hours, tell customers "within one business day" and beat it.
4. Review weekly. Ten minutes every Monday is enough: what moved, why, and one thing to try this week.

A simple weekly support report

For most small teams, a weekly report with these lines is enough:

Copy it into a shared document and fill it in every Monday. After a month you'll know more about your support than most dashboards can tell you.

Measuring support with TickOS

TickOS gives you the building blocks without extra setup:

• Reports with total, unassigned and unread tickets, plus tickets by status and priority.
• CSAT surveys sent automatically after a ticket is resolved, with a one-click rating from the email, an optional comment, average rating, response rate, rating distribution and a CSV export.
• Help center feedback ("Did we answer your question?") to see which articles work.
• Agent statistics through the API, including average first response time and average resolution time per agent, and ticket counts by tag.

New to tickets? Read what a ticketing system is, or grab our 25 customer support email templates to bring your first response time down this week.