Reply times and escalation for a WhatsApp team: three clocks, who is alerted when they run out, and how they are measured
How to set a service-level agreement for a WhatsApp team: first acknowledgement, human reply and resolution, with realistic times per business type, automatic escalation from the unified inbox to the supervisor, the weekly report that shows who is late and why, and what happens outside hours.
On this page 3
The short answer
Three times, not one: the first acknowledgement in under a minute (the bot's job, not the agent's), a human reply to an enquiry within a working hour, and a resolution for a complaint within a working day — each with an escalator: a thread past its time is coloured in the inbox and auto-assigned to the supervisor with an app alert. The system does not rely on anyone remembering; it relies on the inbox counting.
Also asked as: «وقت الرد على العملاء واتساب» · «مين يتنبه لما الرد يتأخر» · «تصعيد المحادثات للفريق» · «أوقات الرد للفريق واتساب»
Three clocks, not one
"We reply within an hour" is one promise that describes nothing: the customer who sent "in stock?" wants seconds, and the one who sent a complaint wants it acknowledged now and solved by someone today. So three clocks, each with an owner: acknowledgement for the bot, reply for the agent, resolution for the agent or supervisor. On our platform about 47% of Instagram threads hold an unanswered customer — the number these clocks exist to bring down.
| Clock | Starts | Target | Owner | If it runs out |
|---|---|---|---|---|
| First acknowledgement | Message arrives | Under a minute | The bot | It does not — automatic |
| Human reply | Thread assigned | A working hour | The agent | Stays under "Unreplied" until the supervisor assigns it |
| Resolution | The "complaint" tag | A working day | Agent or supervisor | Stays in the "complaint" tag filter until closed |
Building the system in the unified inbox
- Let the bot acknowledge and classify
The agent answers the recurring from your files and acknowledges what it does not know — "we have your message, a teammate will reply within [time]" — and sets the tag: enquiry, order, complaint. The tag is what starts the right clock.
- Write the times where everyone reads them
In the agent's instructions ("a teammate will reply within a working hour") so it promises the customer the same time you promised your team, and in the team rules with the working hours inside which the clock counts. Start with what you can keep.
- Set who receives the handoff
From the agent settings: human handoff → the teammate. When the agent reads a complaint, a request for a person, or whatever you told it to hand over ("damaged", "never arrived", "I want to cancel") it assigns the thread to them at once, stops in it, and they get an app alert — without waiting for the clock. Whatever ran past its time with no handoff, the supervisor picks up from the "Unreplied" filter.
- Read the weekly report
First-reply time and average reply time per agent from the team report, the "Unreplied" count each morning, and the tag that piles up in the tag filter. The last one says where the fault is: in the team, or in the file the bot reads from.
Escalating to someone who does not read alerts. A supervisor who sees twenty threads under "Unreplied" daily and opens none teaches the team that the clock means nothing. Start with a time that keeps the late few, and open every one of them the same day.
Frequently asked questions
What reply time does a customer expect on WhatsApp?
We hold no measurement of customer expectations to publish; what we know is that a customer who sees two read ticks with no reply counts the minutes. So the first acknowledgement — from the bot — in under a minute, after which a human reply within a working hour becomes acceptable, because they know the message was read and someone will answer.
Are the times the same for every business?
No. A store in season: a human reply within an hour, resolution within a day. A clinic: emergencies within minutes, bookings within an hour. Real estate: the serious lead within fifteen minutes, before they call another office. Start with a time you can keep and shorten it month by month — a time breached daily is worse than a longer one that is kept.
What happens outside hours?
The escalation clock pauses: a thread arriving at midnight is answered by the bot from your files, distributed by the supervisor in the morning from the "Unassigned" filter, and its clock starts at opening time. An emergency — whatever you told the agent to hand to a human — is assigned at once to the teammate you set, with an app alert, at any hour.
How do I know who is late without watching manually?
The "Unreplied" filter in the unified inbox shows every thread whose last message is the customer's, with the count on the filter itself; the supervisor opens it twice a day and assigns whatever is late. The team report shows first-reply time and average reply time per agent. Nobody watches anyone; the inbox counts.
Does the bot solve the speed problem on its own?
Half of it: the instant acknowledgement and answering the recurring at any hour. The other half — complaints, exceptions, decisions — stays with the team, and the system above is what gets that half done on time.
Read next
Try the agent before you pay anything
The agent that will answer your customers is the one answering you now: ask it from the chat button here or on WhatsApp. Your account is free with no credit card, and the free trial on your own number or page is activated after you contact our team on customer-service WhatsApp.