Core metrics

What is first response time?

Also known as: FRT, first reply time

Published September 10, 2026 · Reviewed by the Fidiora team

Definition

First response time is the elapsed time between a customer submitting a request and receiving the first meaningful reply. Automated acknowledgements do not count. It is usually reported as a median or a percentile rather than a mean, because a handful of very slow tickets distort the average badly.

Why it matters

First response time is the moment a customer decides whether anyone is listening. Long waits generate follow-up messages, which add volume, which lengthens waits further. It is the metric most likely to spiral, and the one most often broken by coverage gaps rather than by team capability.

What to know

  • Report the median and the ninetieth percentile. A mean hides the tail where your worst experiences live.
  • Exclude auto-acknowledgements. Counting them makes the number look excellent and tells you nothing.
  • Segment by channel. Chat expectations are measured in seconds, email in hours, and one blended number serves neither.
  • Most breaches cluster overnight, at weekends, and during volume spikes, not during a normal Tuesday afternoon.
  • Business-hours-only clocks are legitimate but must be stated, or your number is not comparable to anyone else.

How to calculate it

FRT = timestamp of first meaningful reply - timestamp of customer request

An example

Example: a ticket arrives at 22:10 and gets an automated confirmation immediately, then a human reply at 09:20 the next morning. First response time is eleven hours and ten minutes on a round-the-clock clock, or a few minutes on a business-hours clock. Say which one you are using.

Common mistakes

  • Reporting the mean instead of the median and the ninetieth percentile
  • Counting the auto-reply as the first response
  • Blending chat and email into a single average
  • Chasing the metric by sending fast but empty holding replies
Where Fidiora fits

Fidiora answers on contact, around the clock, grounded in your own help content. That collapses first response time for the repetitive share of volume and leaves your team free to reply quickly to the rest, so the number stops depending on who happens to be online.

See Pricing
FAQ

Questions

What is a good first response time?
It depends entirely on channel. Live chat customers expect a reply in under a minute, email customers usually accept a few hours. The more useful target is consistency: a median your customers can rely on, with a ninetieth percentile that is not embarrassing.
Do automated replies count toward first response time?
They should not. An auto-acknowledgement tells the customer their message arrived, not that anyone has looked at it. Counting it produces an excellent number and a frustrated customer base.
Why does first response time spike at night?
Because the clock keeps running when nobody is working. Overnight tickets accumulate and are all breached by the time the team logs on, which is why round-the-clock resolution of routine questions moves this metric more than hiring does.
Get Started

See Fidiora resolve a ticket in 60 seconds.

No credit card, no sales call required. Connect your docs and watch it work.

No credit card · Live in under an hour