Support metrics glossary
First response time. The wait your customers remember.
First response time is the time between a customer's first message and the first reply that addresses the question. It is also one of the easiest support metrics to misreport. Here is the math, and the honest way to run it.
Last updated 14 August 2026
What first response time means
The clock starts when the ticket, chat or email arrives. It stops when your side sends a reply that addresses the question. Everything after that, the back and forth and the fix itself, belongs to other metrics. It measures the wait before anyone engages.
Three words do the heavy lifting: addresses the question. An automated acknowledgement is not a first response. It is a receipt, and a receipt is not a response, any more than a waiter saying be-right-with-you is dinner. Count receipts and the number drops to three seconds and means nothing.
The mean is the wrong average
Here's the thing most dashboards get wrong. They report the mean. Most tickets get answered fast and a few wait days, and those few drag the mean away from anything a real customer lived. The median, the middle ticket, is the typical wait. Report that as the headline. Track the slow tail separately.
| Ticket | Minutes to the first reply |
|---|---|
| Ticket 1 | 3 minutes |
| Ticket 2 | 4 minutes |
| Ticket 3 | 4 minutes |
| Ticket 4 | 5 minutes |
| Ticket 5 | 5 minutes |
| Ticket 6 | 6 minutes |
| Ticket 7 | 7 minutes |
| Ticket 8 | 8 minutes |
| Ticket 9 | 9 minutes |
| Ticket 10 | 149 minutes |
| Median | 5.5 minutes |
| Mean | 20 minutes |
The arithmetic: the waits sum to 200 minutes, and 200 divided by 10 is a mean of 20. The middle pair is 5 and 6, so the median is 5.5. The mean describes nobody on the list. Not the nine answered inside nine minutes. Not the one who waited two and a half hours.
Business hours or calendar hours
Pick one clock and label it. A ticket that arrives Friday at 6 pm and is answered Monday at 9 am waited 63 calendar hours. To a weekday team it waited one staffed hour. Neither is wrong. Mixing the two is, because the trend stops meaning anything.
What a good first response time looks like
There is no honest universal benchmark, because the right number depends on the channel. Live chat customers expect minutes. Email customers expect hours, and a business day is the outer edge. The benchmark that matters is your own median by channel, beaten month over month. A number you computed beats a number you found on a blog.
A fast reply is not a fix
First response time measures the wait for the first reply. It says nothing about whether the reply helped. A team can post a one-minute median with holding messages and still solve nothing on the first pass. Speed of hello and quality of answer are different metrics.
First contact resolution and resolution rate are the two siblings: whether one contact was enough, and how much of the queue closes.
How to bring the wait down
Three levers, in order. Staff to the arrival pattern, not the average day, because the wait blows out between shifts. Triage every new ticket within minutes, even when the full answer takes longer. And take the questions with known answers off the queue, so an AI agent answers them at 2 am.
The WISMO page walks through the cost math for the biggest of those categories.
Your questions, answered first
What is first response time?
The elapsed time between a customer's first message and the first reply from your team that addresses the question. It measures the wait for engagement, not the time to a fix.
How do you calculate first response time?
For each ticket, subtract the arrival time from the time of the first real reply. Take the median across the period, and keep the slow tail visible with a p90 beside it.
Does an autoresponder count toward first response time?
No. An acknowledgement is a receipt. A bot reply counts only when it actually answers the question, and you disclose that a bot sent it. Anything else measures how fast your mail server is.
What is a good first response time?
Channel dependent. Live chat is seconds to minutes, email is hours, and a business day is the outer edge. Skip universal benchmarks. Take your own median by channel and beat last month.
Should first response time be measured in business hours?
Either works if you label it. Calendar hours punish nights and weekends; staffed hours hide the customer's real wait. Report one, or both, but never a blend of the two.
What is the difference between first response time and first contact resolution?
The first is the wait for an initial reply. The second is whether that single contact solved the issue, with no follow-up needed. A fast hello paired with a slow fix is still a slow fix.
Measure yours this week
Pull last month's tickets. Compute the median. Look at the slowest ten.
If the median is fine and the tail is ugly, your schedule's edges are the problem. If both are ugly, let an AI agent take the repetitive categories off the queue.