First Response Time
Definition
First Response Time
First response time is the interval between a customer submitting a request and receiving the first meaningful human reply to it. It is the wait that shapes the whole interaction, because customers judge responsiveness long before they judge the answer.
The word meaningful carries the definition. An automated acknowledgement confirms receipt but answers nothing, so counting it as a first response makes the metric useless.
Channel expectations differ enormously. A two-hour email reply reads as prompt while a two-minute chat reply already feels slow.
Key takeaways
- First response time measures the gap between request submission and the first human reply.
- Automated acknowledgements must be excluded, or the metric measures nothing.
- Targets belong per channel, since expectations differ by an order of magnitude.
- Median and 90th percentile beat the mean, which a few outliers can distort badly.
How it works
First response time is calculated by measuring the elapsed time between a request arriving and the first substantive human reply being sent, then summarising those intervals across a period using a median and a percentile.
The formula is: sum of first-reply intervals ÷ number of requests, for the mean.
The mean is the weakest summary available, and most mature teams report distribution instead.
| Summary | What it shows | Use it for |
|---|---|---|
| Mean | Average wait | Headline reporting only |
| Median | Typical wait | Day-to-day operations |
| 90th percentile | The bad tail | Service level design |
| Within-target percentage | Share meeting the promise | Contract compliance |
The 90th percentile is where complaints live. A median of four minutes hides the 10% of customers waiting two hours — and those are the ones who escalate.
Business hours have to be defined explicitly. A request arriving at 11pm should not count the overnight gap unless the service is genuinely staffed around the clock.
Reach expectations follow device habits. Pew Research Center’s Mobile Fact Sheet, updated 20 November 2025, reports that 91% of U.S. adults own a smartphone, up from 35% in 2011.
Public digital services publish practical guidance on this. Digital.gov shares guidance on building better digital services in government and runs communities of practice focused on a more user-friendly public experience.
The measure is documented in more depth under first response time (FRT), which is the same metric under its common acronym.
Report it beside resolution time rather than alone — fast acknowledgement followed by a slow fix scores well and satisfies nobody.
Never let auto-replies stop the clock. That single design choice is the most common way a support dashboard becomes fiction.
Examples
Response expectations vary sharply by channel, contract, and how urgent the underlying issue actually is. Five cases show where targets land and how they get enforced.
Live chat operations target seconds, not minutes. Because the customer is present and waiting, a 30-second target is standard on staffed live chat support.
Email support targets hours. Consumer teams commonly promise a first reply within four business hours and measure compliance against that promise.
Enterprise software contracts tier response by severity. A production outage carries a 15-minute target while a cosmetic bug carries two business days.
Public services publish response targets openly. Because the promise is in writing, the within-target percentage matters more than the average.
Outsourced help desks report response by channel and by severity. Buyers should confirm whether the clock pauses outside business hours — since that assumption changes the figure completely.
Related terms
First response time sits at the front of the support timeline, ahead of the resolution measures that follow it. The terms below cover the acronym form, the neighbouring intervals, and the channels it is measured on.
- First Response Time (FRT): the same measure under its widely used acronym.
- Average Response Time: the mean interval across all replies, not just the first.
- Internal Response Time: the equivalent measure for internal support requests.
- Resolution Time: the end-to-end interval first response is only the opening of.
- Service Level Agreement (SLA): the contract that sets the response promise.
- Support Ticket: the record the clock runs against.
- Live Chat Support: the channel with the tightest response expectations.
FAQ
How is first response time calculated?
Measure the elapsed time between the request arriving and the first substantive human reply, then summarise with a median and a 90th percentile.
Do automated replies count?
No. An acknowledgement confirms receipt without answering anything, so counting it makes the metric meaningless.
What is a good first response time?
It depends on channel. Chat targets seconds, phone targets under a minute, and email commonly targets four business hours.
Should the clock run overnight?
Only if the service is genuinely staffed around the clock. Otherwise define business hours and pause outside them.
Why report the 90th percentile?
Because the median hides the long tail, and the long tail is where complaints and escalations come from.
Is fast response the same as good service?
No, because response time must be read beside resolution time or quick acknowledgements will mask slow fixes.
See how response-time commitments are structured across the outsourcing sector at Outsource Accelerator.
Independent
