WhatsApp created a tough expectation: the message arrives instantly, so the reply should too. Anyone who handles customers feels it every day. WhatsApp response time is the number customers notice before any other, and the easiest one to let slip without realizing.
This guide shows how to measure it, why the wait grows even when the team is working hard, and what brings it down without turning your support into canned replies.
The two numbers that matter
First response time. How long passes between the customer's message and the first reply from anyone. It decides whether someone feels "helped" or "ignored".
Time to resolution. How long until the issue is actually solved. That depends on the problem, so it is less fair to compare across customers.
Start with the first one. It weighs most on how customers feel, and it is the one you control best.
How to measure it without a tool
Once a week, for a month:
- Pick ten customer chats that arrived at different times of day.
- Write down the time of the customer's message and the time of the first reply.
- Take the median, not the average. One chat forgotten for two days skews the average and hides everything else.
- Separate business hours from after hours. Mixing them makes daytime look worse than it is and nighttime look better.
Within a few weeks you know where you stand and whether your changes are working.
Why the wait grows even when everyone is busy
The usual culprit is the order of the chat list. WhatsApp puts the chat with the most recent message on top, not the one that has waited longest. In practice:
- The noisy group where everyone keeps talking stays on top and gets attention.
- The customer who asked one clear question at 10 a.m. and then went quiet slides down the list.
- By 4 p.m. they are below twenty chats, and nobody notices.
And when several people share the same number, each one assumes someone else answered. The result is the message nobody saw. We go deeper on shared numbers in one WhatsApp number, multiple users.
Five things that cut response time
1. Sort by wait time. Every time you sit down to answer, start with whoever has waited longest. Without a tool, labels or marking pending chats as unread can approximate this. With a tool, a queue sorted by wait time does it for you.
2. Reply in two steps when you need to think. If the answer requires digging, send something short that shows you saw it and are on it, then the full answer. Careful that the first step doesn't become a promise: "looking into it" is safer than "I'll fix it today".
3. Transcribe voice notes. Long voice notes are the messages most likely to wait, because they force you to stop and listen. With a transcript you read them in seconds. See how to transcribe WhatsApp voice messages.
4. Keep quick replies for the repetitive stuff. Payment details, a booking link, the documents you need. WhatsApp Business quick replies cover this.
5. Set expectations on hours. Answering at 11 p.m. teaches customers to expect answers at 11 p.m. A clear away message and the hours on your profile align what "fast" means for both sides. The setup is in WhatsApp away message.
Too fast is also a problem
There is an opposite mistake. A reply that lands two seconds after the question, long, polished and obviously pre-written, gives the bot away. The customer feels there is nobody on the other end and starts writing less, or keeps insisting "I want to talk to a person".
The right pace is that of an attentive person: quick in a conversation that is happening right now, a little slower in a cold one, and always answering what was actually asked. AI tools that reply instantly tend to err on this side. The habits that make AI replies sound robotic are covered in the tells that make AI text read like a bot.
Checklist
- Do you know the median of your first response time?
- Is your working list sorted by who has waited longest?
- Does every customer have an owner, so nobody assumes someone else replied?
- Do voice notes become text before anyone has to listen?
- Are your hours on your profile and in your away message?
FAQ
What is a good first response time? It depends on what you promised the customer and on your type of business. Being predictable matters more than being fast: keeping the hours on your profile beats replying instantly some days and disappearing on others.
Does an automatic "we got your message" count as a first response? For the customer, only if it says something useful, like when they will hear back. A generic acknowledgment doesn't change how long the wait feels.
How do I measure it with a team? Also write down who replied. You will quickly see whether the wait concentrates at a certain hour, on a type of customer or on one overloaded person.
Where WACrew fits
WACrew is an open-source agent for WhatsApp customer service. It puts groups and chats into a queue sorted by wait time, transcribes voice notes and shows first response time and who answered each customer in a panel. When the AI replies, the message goes out at a human pace, with read receipt, typing and pauses. The code is on GitHub.



