Devtechify
WhatsApp Automation

Bot-to-Human Handoff on WhatsApp: When and How

KarthikFounder & Full-Stack Engineer4 min read

Picture a customer whose order arrived cracked. They message the shop's number, get a cheerful automated menu, type 'broken', get an answer about return policy, type 'speak to someone', and get the menu again. By the third round they are angry, and the person who finally takes over starts the conversation at a disadvantage.

A bot does not need to be clever to be good. It needs to know when to stop. This is a guide to that moment.

Triggers that should hand over immediately

  • The customer asks for a person, in any wording: 'agent', 'human', 'call me', 'manager'.
  • Words showing a problem: refund, complaint, wrong, broken, cancel, not received.
  • Anything involving payment disputes or amounts of money.
  • Two failed attempts by the bot in a row to answer the same question.
  • Sensitive topics such as health details, or anything the customer clearly does not want to type into a form.

Notice that this is a short list, and it leans cautious. We would rather hand over too early than too late. A human can always send the customer back to a form; a bot cannot undo a bad first impression.

What the handover message should say

Tell the customer plainly what is happening: 'I am passing this to our team. Someone will reply here by 11 am.' Give a time, not a mood. If it is outside working hours, say so, as in our post on business hours and out-of-office replies. Do not ask the customer to repeat what they already told the bot.

That last point is the one that matters most. The person taking over should see the whole conversation, including what the bot asked and what was answered, before they type. If your inbox does not show prior messages clearly, fix that before adding any bot logic.

Stop the bot once a human is in

Ensure the bot goes quiet. Few things look worse than a staff member typing a careful reply while the automation fires 'Sorry, I did not understand' underneath it. How you do this depends on your tool: some let you pause rules per contact, some let you mark a conversation, and some need you to build the logic with webhooks and your own code.

Test this one twice

Start a chat, trigger the handover, reply as the human, then send another message as the customer. Confirm the bot stays silent. This is the bug that slips through most often.

With WA Getway you have auto-replies, an inbox on the Meta CRM side and webhooks, so you can combine simple rules with your own logic. Treat the exact pause behaviour as something to verify in your own account, not assume.

Give the human the right context

  1. 1The customer's name and number, and any stage or tag from earlier contact.
  2. 2The topic, even if it is only a one-word label.
  3. 3What the bot has already said, so the agent does not contradict it.
  4. 4How long they have been waiting, since that changes the tone of the first reply.
  5. 5Whether this customer has an open order or invoice you can look up.

A tag at handover, like 'needs human: refund', costs nothing and saves the agent a minute of reading. Our guide on segmenting contacts with tags shows how to keep the tag list from sprawling.

The return trip

Handover is not always one way. Once the agent has resolved the issue, the chat can go back to automation for the next new topic. Decide how: after a timeout of no messages, or when the agent marks it closed. Without a rule here, a bot can reappear mid-resolution or never return at all.

If you only do three things

  • Make asking for a person work every time, in every state of the bot.
  • Pass the history with the chat.
  • Silence the bot while a human is replying.

Everything else is polish. For a deeper look at designing a bot that avoids dead ends in the first place, see building a WhatsApp FAQ bot without any AI.

Finally, keep a short log of handovers for a month. Note why each one happened and whether the bot could have handled it. If the same question keeps landing on a human, either teach the bot that answer or fix the thing that causes the question. A handover is useful information about where your automation or your process falls short, so treat it that way instead of only as an emergency exit.

If your handover needs to talk to your own order system or CRM, that is a small custom build. Describe what you have on the services page or get in touch and we will tell you honestly whether it is worth it.

handoffchatbotcustomer experienceescalation

Talk to us

Have a project in mind? Tell us about it.

Four quick questions and we'll reply within one business day with an honest view on the fastest way to ship it, whether that's our own products, a custom build or an integration.

DevTechify

Start your project

Let’s build something great

1
2
3
4

Which industry does your business belong to?

Pick the closest match — we'll tailor the rest for you.