First response time on WhatsApp: what it is and why it matters
What first response time is, how to measure it properly, which target makes sense for each kind of conversation and what to do to bring it down without hiring more people.
IntegraWhats team · October 13, 2026 · 7 min read
Someone who messages a business on WhatsApp almost always has the phone in hand, waiting. It might be a person trying to book an appointment, check whether a product is in stock or ask for a quote. While nobody replies, that person keeps looking. Often they send the same question to two or three other businesses.
First response time is the measure of how long the customer waits before hearing anything from your team. It's one of the simplest numbers to track and one of the most telling about your customer service.
What first response time is
It's the time between the customer's first message in a conversation and the first reply from a person on your team.
Two details matter when you measure it:
Automatic replies don't count as a first response. The welcome message or the chatbot menu help, but the customer is still waiting for someone to sort things out. If you count the automatic part, the number looks good and says nothing.
Separate business hours from the rest. A message that arrives at 11 p.m. and gets answered at 8 a.m. isn't the same as one that arrives at 10 a.m. and gets answered at noon. Measure the two separately, or measure only within opening hours.
Why this number matters
Customers compare. On WhatsApp, the competition is one chat away. Whoever answers first has a better chance of being heard.
Waiting changes the tone of the conversation. A customer who waited a long time starts out annoyed, and the conversation gets longer and harder.
It reveals bottlenecks. If the time always goes up at the same hour or in the same sector, you know where you're short-staffed or where the process is stuck.
It's easy to understand. Everyone on the team understands "reply within fifteen minutes". That makes targets easy to agree on.
Which target makes sense
There's no single right number for every business. The target depends on what the customer needs and how much waiting costs them. Some reference points:
| Type of conversation | What the customer expects | Reasonable starting target |
|---|---|---|
| Booking at a clinic or salon | To know if there's a slot | Minutes, within opening hours |
| Product question at a store | Price, stock, delivery | Minutes, within opening hours |
| Service quote | A first reply, even if the price comes later | Up to an hour |
| Billing and invoice copies | A resolution, without extreme urgency | A few hours |
| After-sales support | To know someone has seen the problem | Up to an hour, with a deadline for the fix |
Start by measuring where you are today, for a week or two, before setting a target. A target far from what the team can actually do only creates frustration. Improve step by step.
A target per sector, not one for the whole company
Each sector has its own pace. Booking needs to reply fast. Billing can take longer. With a single target, it's either too loose for booking or too tight for billing.
Ideally, set a first response target for each sector and track how many conversations stayed within it. When a conversation goes past the deadline, someone needs to see it right away, not in the end-of-month report.
After hours: tell the truth
Nobody expects a small clinic to reply at 3 a.m. What annoys people is sending a message and not knowing whether anyone will see it.
A good after-hours message has three parts:
- It says the message arrived.
- It says when the team is back.
- It says what the customer can share in the meantime.
Example:
Hi! We got your message. We're open Monday to Friday, 8 a.m. to 6 p.m., and Saturday until noon. If you like, tell us what it's about and which day and time you prefer, and the team will reply as soon as we're back.
The next morning, the overnight conversations should be first in the queue.
How to bring first response time down
Organize a queue per sector. A new chat can't depend on someone remembering to check the phone. It goes into the sector's queue and stays visible until someone takes it.
Triage automatically. A short menu at the start separates topics and sends each conversation to the right sector. That way nobody wastes time reading messages that aren't theirs.
Keep quick replies for the start of the conversation. Many first replies are similar: confirming available times, asking for a detail, sending the address. Keep those answers saved.
Reply with something useful, even if it's not everything. "I'll check the schedule and get back to you in ten minutes" is already a first response. It's not an excuse to stall: give a deadline and keep it.
Look at peak hours. If most messages arrive between 11 and 1, don't schedule everyone's lunch break then.
Spread the load. If one person has twenty open chats and another has two, the queue moves slowly. Review each agent's workload.
Flag conversations that are running late. Chats close to missing the deadline should stand out. An alert in the moment solves more than a report the following week.
What not to do
- Don't use an automatic message to pretend someone replied.
- Don't reply fast with wrong information just to hit the target.
- Don't leave a chat without an owner "because someone will pick it up".
- Don't look only at the average. Look at the conversations that waited a long time too: those are the ones that turn into complaints.
How to track it in IntegraWhats
In IntegraWhats, conversations go into sectors and queues, and each sector can have its own first response time target. The no-code chatbot handles the welcome message, the triage menu and the after-hours message, and hands the conversation to a person when the customer asks.
In the shared inbox, the team sees what's waiting, uses quick replies and transfers conversations to another sector when needed. On paid plans, the AI copilot suggests replies and summarizes long conversations, which helps whoever picks up a case halfway through.
Frequently asked questions
Does the automatic welcome message count as a first response?
It shouldn't. It tells the customer the message arrived, but they're still waiting for someone. For the number to be useful, measure until the first reply from a person on the team.
How can I measure first response time without a tool?
You can take a sample: for a few days, write down the time of the first message and the time of the first reply for about twenty conversations. That already shows the size of the problem. To track it every day, per sector, it's better to use a tool that records it automatically.
What's a good first response time for a clinic?
It depends on volume and staff. For booking, patients usually want a reply within minutes during opening hours. Start by measuring where you are today and set a target a little better than that, reviewing it every month.
Doesn't replying faster hurt quality?
It can, if the only goal is speed. That's why the first reply has to be useful: confirm you understood the request, share what you already can and say when the rest is coming. Fast and right beats fast and wrong.