Handing a WhatsApp chat from the bot to a person
The bot keeps answering after your colleague has taken over. Here is why, and the two-step flow that fixes it permanently.
Handover is the moment a conversation stops being handled by an automation and becomes the responsibility of a person. Done well, the customer barely notices. Done badly, the bot keeps talking over your colleague and the customer gets two conversations at once.
Handover is the part of chatbot design that the field covers worst, and it is the part customers judge you on. Nobody minds a bot that cannot answer. Everybody minds a bot they cannot get past.
The bug almost every store has
Here is the sequence. Your automation asks the customer a question and waits for an answer. The customer takes ten minutes. Meanwhile someone on your team sees the chat in the inbox and replies manually. The customer then types something — and it is captured as the answer to the bot's question rather than reaching your colleague.
From the customer's side, they answered a person and a robot replied. From your colleague's side, the customer ignored them.
The fix is a separate two-step automation that sends nothing:
The whole fix
Install it — nothing to configure
Two steps, no settings, no messages sent. If you build one automation from this entire site, make it this one.
Add this automation to my account It installs as a draft. Nothing is switched on and no customer is messaged until you press Publish.One important detail. "Agent sends a message" means a human in your shared inbox. Messages the automation itself sends do not count, so this flow cannot cancel itself — which is exactly what you want.
The three places handover must exist
- The failure branch of every lookup. A Google Sheets or API step that finds nothing should reach a person, not apologise and stop.
- The unanswered branch of every AI step. A knowledge base that does not cover a question is the normal case, not an error, and it belongs with a human.
- An explicit option on any menu. "Talk to a person" should be one tap away from anywhere in the flow.
A flow with no exit generates complaints faster than it absorbs them.
Make the handover useful, not just polite
Assigning a chat is the minimum. What makes the difference to your team is what arrives with it.
| Step | What it does | Why it matters at handover |
|---|---|---|
| Assign Chat | Gives it to a team or person | An unassigned chat is nobody's job |
| Add Internal Note | Leaves a note only your team sees | Carries the answers the bot already collected |
| Update Conversation Status | Sets open / pending / resolved | Puts it in the right queue |
| Update Customer Tags | Labels the contact | Lets you find these conversations later |
The internal note is the underrated one. If the bot has already collected an order number and a reason, a note saying "Return requested. Order 1042 — damaged" means your colleague opens the chat knowing everything. Without it they re-ask, and the customer answers the same question twice.
What to say to the customer
Three rules, all learned the hard way:
- Say a person is coming, not that you are "connecting" them. There is no queue and no connection — someone will reply when they can. Set an honest expectation.
- Give a time if you can. "Someone will reply within the hour" during working hours; "we're back at 9am" outside them.
- Do not make them repeat themselves. If the bot collected details, the human should use them.
Handover outside working hours
Assigning a chat at midnight to a team that is asleep is fine, as long as the customer knows. Combine handover with a business hours check so the message they get matches reality: "someone will reply shortly" during the day, "we're back at 9am" at night.
Set the conversation status to pending so overnight chats form a queue your team can work through in the morning rather than scrolling for them.
Cost: handover is free
Every message in a handover is a reply to a customer who just messaged you, so it sits inside the 24-hour customer service window. Meta's pricing documentation confirms service conversations have been free and unlimited since 1 November 2024 — so there is no cost argument for making handover harder.
The one thing to watch is the window closing. If a customer goes quiet for more than 24 hours and your colleague then tries to reply with free text, it fails with error 131047 and they will need an approved template instead. Handling chats the same day is not just good service; it is the only way to reply freely.
When not to automate at all
Some conversations should go to a person immediately, without a menu:
- Anything where the customer is already angry.
- A photo of a damaged or wrong item — a keyword rule cannot read an image, so use the If Customer Sent condition to detect attachments and route them.
- Anything about money that is not a standard flow: partial refunds, disputes, chargebacks.
- Wholesale and high-value enquiries, which are worth a person's time.
A useful test: if getting it wrong costs more than a person's five minutes, do not automate it.
During a spike
On a sale day or a launch, handover volume rises faster than everything else. Two adjustments worth making in advance: widen the bot's self-service coverage so fewer conversations need a person at all, and be ready to switch off any flow whose handover your team cannot service. A handover to nobody is worse than a bot that politely says you are busy.
Measuring whether any of this works is covered in measuring whether your automation works.
Frequently asked questions
Why does my bot keep replying after a human has taken over?
Because the automation is still waiting for an answer to a question it asked, so the customer's next message is captured as that answer. Fix it with a two-step automation: trigger on Agent Sends Message, then Cancel Pending Question.
Does the Cancel Pending Question step send anything?
No. It only stops the bot waiting for an answer, so the customer's next message reaches your team instead.
Where should a flow always offer a human?
Three places: the failure branch of any lookup, the unanswered branch of any AI step, and as an explicit option on any menu.
Does handing over to a human cost anything?
No. Handover messages are replies inside the 24-hour customer service window, which Meta has made free and unlimited since 1 November 2024.