First Response Time · First response time
What is First Response Time and why is the number often too flattering?
First Response Time measures how long a customer waits for your first substantive answer. Automatic acknowledgements make the number look good without the customer knowing anything.
In short
First Response Time is the time between a customer question arriving and that customer receiving your first substantive answer. The word substantive is the whole point: an automatic acknowledgement doesn't count, because afterwards the customer still doesn't know where they stand.
Calculation
FRT = timestamp of first substantive reply - timestamp of arrival
Measure in working hours, not wall-clock time. A question arriving Friday at 4:50pm and answered Monday at 9:10am is 20 working minutes of waiting, not 64 hours. Measure in wall-clock time and you're mainly measuring your opening hours.
Why the average is the wrong measure
An average response time of 3 hours can mean nearly everyone got an answer within 3 hours, or that most were answered within 20 minutes while a handful of customers waited two days. That last group is exactly the group that calls, emails again or leaves a review.
So use a percentile instead of an average. With a 90th percentile of 5 hours you know nine out of ten customers had an answer within 5 hours. That number moves with the outliers, and those outliers are your real problem.
What a fast first response is worth
A fast first answer prevents the second question. A customer who hears nothing sends a chaser after a day, then calls, and sometimes tries a third channel. Those three messages are about the same question and cost your team attention three times.
That's also the reason to send a partial answer when the full answer takes time. "We've received your return and are checking the status, you'll hear from us tomorrow" is a real answer. It gives the customer something to act on, and it saves you the chaser.
First reply or first real answer?
| First reply | First real answer | |
|---|---|---|
| Counts | Any message from your side, including an acknowledgement | Only a message answering the question or asking a follow-up |
| Gameable | Yes, an auto-reply puts it at zero | No |
| What the customer experiences | Someone saw it | Someone is working on it |
Measure both and steer on the second. An acknowledgement is useful for expectation, but the moment it counts in your response time you're measuring your own automation.
Where it goes wrong
Counting the automatic acknowledgement
Many systems stamp the acknowledgement as the first response. Your number then becomes a few seconds and never moves again, while substantively nothing changed. Check in your reporting which message is counted as the first response.
Steering only on response time
A team judged on speed sends short answers that don't finish the question. Response time falls and the number of reopened conversations rises. So always look at response time and resolution in the same view.
What to do this week
Check whether your automatic acknowledgement is counted as the first response, and switch your reporting from average to 90th percentile. Then look at last week's ten slowest conversations. Usually a pattern shows up, for example that questions without an order number stay put because nobody picks them up.
What this looks like in a system
In Cuego the first substantive reply counts, not the acknowledgement, and measurement is in working hours. Questions the AI agent answers on its own get that answer immediately on arrival, including in the evening. What needs a person is waiting with a prepared draft when the team starts, so the first response doesn't have to wait for the lookup work.
Automation & workflowsRelated terms
Abandon rate
Abandon rate is the share of customers who drop off before reaching anyone. Those questions don't disappear, they return by email tomorrow.
Read onSLA
An SLA sets out how fast you respond and how often you meet that. The agreement is only worth something when the timer measures what your customer experiences.
Read onQueue
A queue is the list of conversations waiting on someone. How you sort that list determines which customers you systematically help too late.
Read on