Glossary

First response time (FRT)

First response time is how long a customer waits between sending a message and getting the first reply from your team or your AI. You work it out per conversation as the time of the first reply minus the time the message arrived, then take the median or average across conversations.

Last updated: 19 November 2026 · By

Fyncall wrote this entry. The WhatsApp rule mentioned below links to Meta's own documentation, checked 19 November 2026. Fyncall details come from our product pages and docs.

What is first response time?

First response time (FRT) measures how long a customer waits for the first reply to a new message. It starts when the message reaches you and stops when someone, or something, replies to the customer.

Helpdesks commonly track it alongside resolution time, which runs until the problem is solved. A fast first reply with a slow fix still leaves the customer waiting, so look at both. Targets for either are usually written down as an SLA.

How do you calculate first response time?

For one conversation: FRT = time of first reply minus time the customer's message arrived. For a period, add up the FRT of every conversation that got a reply and divide by the number of those conversations, or take the median.

Here is a worked example for one morning:

ConversationMessage arrivedFirst replyFRT
A09:0009:1010 minutes
B09:0509:2015 minutes
C09:3012:30180 minutes

The average is (10 + 15 + 180) ÷ 3, about 68 minutes. The median is 15 minutes. One slow reply pulls the average up a long way, which is a reason to report the median as well. The average still shows that someone waited hours.

Decide a few rules before you compare numbers over time:

  • New conversations only. A follow-up on an open thread is not a new wait.
  • Leave out spam. Messages that need no reply flatter the number.
  • Count unanswered messages separately. They have no FRT yet, so they drop out of the average and the backlog hides.

Should you measure business hours or calendar hours?

Measure both if your tool allows it. Business-hours FRT shows how well the team performs while it is working. Calendar FRT shows how long the customer actually waited.

Take a store whose team works Monday to Friday, 09:00 to 17:00. A customer writes at 18:00 on Friday, and the team replies at 10:00 on Monday.

MethodWhat it countsFRT
Calendar hoursEvery hour from Friday 18:00 to Monday 10:0064 hours
Business hoursOnly working time: Monday 09:00 to 10:001 hour

Both are true. The 1-hour figure is fair to your team; the 64-hour figure is what the customer lived through. High weekend calendar FRT is a coverage question, not a sign that people are slow.

On WhatsApp, a customer's message opens a 24-hour customer service window. Outside it, Meta only lets you send template messages, so a weekend gap changes how you can reply, not just how fast. See the WhatsApp 24-hour window.

How do auto-acknowledgements distort first response time?

An automatic "we have received your message" reply can stop the FRT clock within seconds, so the number looks excellent while the customer still has no answer. It measures how fast your software is, not how fast you help.

To keep the metric honest:

  • Leave automatic acknowledgements out of FRT, or report them separately.
  • Report AI answers separately from first human replies. Both are real replies, but they tell you different things.
  • Check what stops the clock in your tool. In Fyncall, the ticket first response timer stops when an agent sends the first reply or comment on the ticket.

How do you improve first response time?

Answer common questions faster and make sure urgent conversations are seen first. Sorting and preparation matter more than typing speed.

  1. Sort the queue by urgency, not arrival. A queue that ranks by risk puts a breaching ticket above a simple pre-sales question.
  2. Prepare replies for repeat questions. Canned responses cover order status, returns and delivery times. Start with the WISMO reply templates.
  3. Let an AI agent answer the simple ones. An AI agent can answer common questions such as "where is my order?" as they arrive. Start with drafts your team approves.
  4. Publish your hours. Telling customers when you reply sets fair expectations for out-of-hours messages.
  5. Check FRT per channel. One slow channel hides inside a healthy overall average.

How does Fyncall track first response time?

On the Pro plan, Fyncall tickets track first response and resolution time against targets set by priority. The defaults are 1 hour for Urgent, 4 hours for High, 8 hours for Normal and 24 hours for Low, and you can edit them.

SLA timers start when a ticket is created, and each ticket shows whether it is on track, at risk or breached. Reassigning a ticket does not reset the timer, and the SLA At Risk queue puts the tickets closest to breaching their deadline at the top. See the helpdesk and plans.

Each channel's AI agent can run in Auto-Reply, Draft & Review or Off, and outside your working hours it can carry on, suggest a ticket or open one.

Common questions

Does an AI reply count as a first response?

It can, if it actually answers the customer. A plain acknowledgement should not count.

What is a good first response time?

There is no single right number. Set a target your team can meet on its busiest day, by channel and priority, then tighten it once you meet it reliably.

Does first response time include weekends?

Calendar FRT does; business-hours FRT does not. Report both so you see the team's speed and the customer's wait.

Ready to try Fyncall?

Install it tonight, let the AI draft your first replies, and switch it on one channel at a time as you start to trust it.

  • Free plan, no credit card
  • 14-day free trial on Pro
  • Unlimited human replies on every plan