By KYN AI Advisory Team — AI implementation specialists, Singapore
We could not find a verified, sector-by-sector benchmark for WhatsApp response time, so we do not publish one. Figures that circulate usually come from vendors selling messaging software, and they rarely state sample size or method. A reliable target comes from your own data: measure median time to first reply by enquiry type, find the point where conversion drops, and set the target just inside it. This article gives the method and the rules that keep a target achievable.
Why do generic response-time numbers mislead?
Three reasons.
- Customers differ by task. Someone asking whether a shop is open tolerates a different wait than someone asking for a quote on a fit-out.
- Channel norms differ by market and by customer. A buyer who uses WhatsApp for everything expects conversational pace. A buyer who uses it alongside email and phone may accept a slower reply. Your four markets may behave differently, so split your data by country.
- The clock starts at different times. Does it start at the customer's first message, at the start of business hours, or at the first human message? Without a stated start, two numbers cannot be compared.
Our view: pick a definition, publish it to your team, and hold to it.
How do you define response time?
Use two measures.
- Time to first reply. From the customer's first message to the first message from a person or an approved automated acknowledgement. Measure in clock minutes during staffed hours.
- Time to useful answer. From the first message to the reply that answers the question or sets a next step with a date. This is the one the customer feels.
An instant acknowledgement lowers the first measure and does nothing for the second. Track both, and do not let the first hide the second.
Also define "staffed hours". A message at 22:00 that gets a reply at 09:05 is a 9-hour wait in clock time, and a 5-minute wait against business hours. Report both, and tell customers the hours.
How do you find your own tolerance point?
You need three months of enquiry data, which most teams already hold in the WhatsApp inbox or the CRM. For each enquiry record:
- enquiry type (price, availability, complaint, booking, other);
- timestamp of first message;
- timestamp of first reply and of useful answer;
- outcome (booked, quoted, lost, no reply from customer).
Then split by type and bucket by wait: under 5 minutes, 5 to 30, 30 to 120, over 120. For each bucket calculate the share that ended in a booking or a quote.
Look for the step where that share drops. For a booking enquiry it may be at 30 minutes. For a complaint it may be later. Set the target at the bucket edge before the drop, and measure again after a quarter.
Warnings on small samples: with 40 enquiries a month, a bucket may hold five records. Treat the pattern as a hint, not a rule, and keep collecting.
What response targets work in practice?
Targets should vary by type. A structure we use as a starting point, not as a benchmark:
| Enquiry type | Reply target | Owner | |---|---|---| | Price or availability | Short, inside staffed hours | Sales | | Booking or order change | Same working day | Operations | | Complaint | Acknowledged same working day, named owner | Manager | | Out of hours | Auto-acknowledge with opening hours | System |
Treat the figures as yours to fill in from your data. Writing "5 minutes" because a vendor said so sets the team up to miss it.
What routing rules keep the target achievable?
A target fails when messages sit in a shared inbox that nobody owns. Four rules help.
- One owner per conversation. The first person to reply owns it until closed or handed over by name.
- Assign on arrival. Round-robin or by type, within a minute, not at the next glance.
- Escalate silence. If an owned conversation passes the target, the manager sees it.
- Show the queue. A single view of unanswered messages, oldest first.
For more on running a multi-person inbox see managing WhatsApp enquiries across a sales team.
What should an automated first reply say?
Say what you did, what happens next and when. For example: the message was received, a named person will reply, and the expected time based on your hours. Do not imitate a person. Do not promise a time you cannot meet.
An automated reply can also sort the enquiry. Asking "Is this about a quote, an existing order or something else?" lets you route in the first minute. Keep it to one question.
Rules for outbound messages differ from replies. Replies to a customer who messaged first sit inside the conversation the customer opened. Messages you start, such as promotions, fall under the marketing rules of the recipient's country. The page on WhatsApp Business API cost in Singapore covers the platform side.
What do you do about after-hours messages?
You have three options:
- Acknowledge and queue. Tell the customer the opening hours and reply first thing.
- Triage by keyword. Flag urgent words, such as "urgent", "cancel" or "damaged", to an on-call person.
- Cover with an agent for simple questions. The agent answers from a set of approved facts, hands anything else to a person, and logs the conversation.
The third needs care. An agent must not quote prices below a list, promise delivery dates it cannot see, or give advice outside its brief. Our article on custom WhatsApp systems versus off-the-shelf tools compares the options.
How do you keep the target honest?
Targets drift when nobody looks. Put three numbers on one screen and review them weekly for ten minutes:
- median time to first reply, by enquiry type;
- number of conversations past target, with their ages;
- number of conversations with no owner.
The third number is the most useful. An unowned conversation is a missed reply that has not happened yet. Fix ownership and the other two numbers usually follow.
Once a quarter, redo the bucket analysis from the earlier section. If the drop-off point has moved, move the target. Customers change, and so do your offers and your competitors. A target set once and never revisited becomes a number the team ignores.
Where KYN fits
KYN builds WhatsApp inbox and reply systems with the routing and logging above. For an insurance brokerage, a reply desk sorts each reply at about S$0.01. For a manufacturer, each department receives a report on WhatsApp at 06:30, at about S$0.05 a report. Every action is logged with the actor, and messages that quote terms or carry money wait for a named person.
The first 14 days are a review of your current inbox, response data and team. A full build ships in under 90 days, on cloud infrastructure in your name. See sales and integrations.
Frequently asked questions
What is a good WhatsApp response time for a business?
We do not know of a verified, sector-wide figure. Set a target from your own enquiry data, by enquiry type, and revisit it each quarter.
Does an auto-reply count as a response?
It counts as an acknowledgement. Track it separately from the first human reply and from the useful answer, so a fast auto-reply does not hide a slow answer.
Should I reply to WhatsApp messages outside business hours?
Acknowledge them with your opening hours and reply when staffed. Add a flag for urgent keywords if a late message can cause a loss, such as a cancellation.
Checked 30 October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.
