# First response time: how to measure it and bring it down

Source: https://frosvo.com/blog/first-response-time
Published: 2026-10-24

**Short answer:** first response time is how long a customer waits between sending a message and getting the first real reply from your team or your assistant. Measure it from the customer's first message to the first reply that is not an automatic receipt, report the median as well as the average, and bring it down with routing, saved replies, clear hours and an assistant for the easy questions.

## What counts as the first response?
The first response is the first reply that actually helps the customer. An automatic message that says the request was received does not count, because the customer is still waiting. A helpful answer from your AI assistant counts, and so does a human reply that asks a useful follow-up question.

Count the first reply that actually helps. An automatic "we got your message" does not count, because the customer is still waiting. A reply from your AI assistant that answers the question does count, and so does a human reply that asks a useful follow-up.

## How do I measure first response time fairly?
Start the clock at the customer's first message and stop it at the first helpful reply. Measure inside your office hours so a 2 a.m. message does not count as a failure, report the median as well as the average, and look at each channel separately, because people expect different speeds.

- **Start the clock** when the customer's first message arrives.
- **Stop the clock** at the first helpful reply.
- **Use office hours.** A message sent at 2 a.m. to a team that opens at 9 should not be counted as a seven-hour failure. Measure inside your hours and say so.
- **Look at the median and the slow tail.** The average hides the few customers who waited a day.
- **Measure by channel.** People expect chat to be answered in minutes and email in hours.

To see how many people you need to hit a target, try the [live chat staffing calculator](/tools/live-chat-staffing-calculator). Frosvo's [team report](/docs/reports) shows first-reply and resolution times by day and by person, and you can set first-reply and resolution targets under [Automation](/docs/automation). Frosvo warns your team before a target is missed and records every miss.

## How can I make customers wait less?
Set realistic hours, route conversations automatically, switch on notifications, reuse saved replies, let an assistant take the repeat questions, watch the unassigned view, schedule follow-ups and review the slowest conversations every week. These eight habits shorten waits without asking your team to type faster.

1. **Set realistic office hours** per website, so the chat tells visitors when to expect an answer. See [office hours](/docs/office-hours).
2. **Route new conversations** to the right person automatically, with round robin among whoever is online, so nothing sits unassigned.
3. **Turn on notifications** on the phone and desktop, and set your status so the right people are available. See [notifications and your status](/docs/notifications-and-presence).
4. **Use saved replies** for the answers you send every day, so a reply takes seconds.
5. **Let an assistant answer the repeat questions** so your team's first reply goes to the conversations that need a person.
6. **Show who is waiting.** The inbox has an Unassigned view. Keep that list short.
7. **Follow up on a schedule.** Use reminders for conversations that need a second step, so they do not come back as angry first messages.
8. **Review the slow ones.** Every week, open the five longest waits and ask what delayed them: no one on shift, a hard question, or a missed notification.

## What is a good first response target?
A good target is one your team can keep. A first reply within a few minutes during chat hours and within a few hours for email is a common starting point. Watch the misses for a month, then tighten the number once you are meeting it comfortably.

It depends on your channel and your hours, so set a target you can keep and improve it. A first-reply target of a few minutes for chat during your hours and a few hours for email is a common starting point. Pick numbers your team can actually meet, watch the misses for a month, then tighten them.

## Is faster always better?
No. A fast wrong answer is worse than a slightly slower right one. Track first response time together with customer ratings and how many conversations were resolved. If speed rises and ratings fall, your team is rushing and the target needs a second look.

A fast, wrong answer is worse than a slightly slower right one. Track first response time together with customer ratings and how many conversations were resolved. If speed goes up and ratings go down, your team is rushing.

Frosvo's live chat, shared inbox, reports and assistant are built for this. [Start free](/signup) and set your first target in Automation.