Skip to content

New: AI agents now qualify, answer and route your WhatsApp leads around the clock.See how it works.

Parlo

Automation

How to design a chatbot that hands off to humans gracefully

When a WhatsApp chatbot should hand over to a person, how to pass context, set wait-time expectations, handle after-hours chats and measure the result.

Parlo Editorial · · 4 min read

A chatbot that answers order-status questions at midnight is useful. A chatbot that traps a frustrated customer in a loop of menu options does real damage to how people see your brand. The difference rarely comes down to how clever the bot is. It comes down to whether the bot knows when to step aside, and how cleanly it passes the conversation to a person.

This guide covers how to design that handoff on WhatsApp, where customers are used to talking to real people and notice quickly when they aren't being heard.

Decide when the bot should hand off

Write your handoff triggers before you build a single flow. Most fall into a few groups:

  • The customer asks for a person. Words like “agent”, “human” or “call me” should work at every step. Customers should never have to fight for this.
  • The bot is stuck. Two failed attempts to understand the same message is a sensible limit. Asking the customer to rephrase a third time rarely helps.
  • The topic is sensitive. Refunds, complaints, damaged goods, medical or financial questions and anything involving an upset customer belong with a person.
  • The stakes are high. A large B2B enquiry or a long-standing customer deserves a person early, even if the bot could technically cope.
  • The tone turns negative. Capital letters, repeated messages and phrases like “this is ridiculous” are worth routing on.

Pass the context along

The most irritating thing a customer can read after a handoff is “How can I help you?” They've already explained. When the conversation moves into your team inbox, the agent should see:

  • The full bot transcript, not just the last message
  • Everything the bot collected, such as name, order number, issue type and photos
  • The reason for the handoff, for example “asked for an agent” or “refund above threshold”
  • Customer history: past orders, previous conversations and tags

Have the bot gather key details before it hands off, so the agent can open with something specific: “Hi Priya, I can see order 4821 arrived damaged. I'll arrange a replacement now.”

Set honest expectations

A handoff message should tell customers what happens next and roughly when. Compare these:

VagueClear
Please wait, an agent will be with you shortly.I'm passing you to our support team. The current wait is about 10 minutes, and you'll get a reply right here.
Your request has been noted.Our team is offline until 9 am tomorrow. Your message is saved, and you'll be first in line when we open.

If you show a wait time, base it on real queue data and adjust it during busy periods. An optimistic estimate that turns out wrong annoys people more than an honest long one.

Plan for after hours

Customers message whenever it suits them. Outside business hours, the bot should:

  1. Say clearly that the team is offline and when it will be back.
  2. Offer whatever it can handle alone, such as order tracking or answers to common questions.
  3. Collect the details an agent will need, so the morning reply resolves the issue instead of asking more questions.
  4. Route genuinely urgent cases to an on-call person, if you offer that.

Use AI for the middle ground

Rule-based chatbots are dependable for structured tasks like tracking orders or booking appointments. AI agents can answer open-ended questions from your help content, which cuts handoffs for routine queries that don't fit a menu. The same rules still apply: an AI agent should recognise when a question is beyond it and pass the conversation on, with context, instead of guessing.

Measure containment and satisfaction together

Containment rate, the share of conversations the bot resolves without a person, is the metric most teams watch. On its own it misleads. A bot that never hands off has excellent containment and unhappy customers.

Track it alongside these:

  • Customer satisfaction for bot-only and handed-off conversations, collected with a one-tap rating at the end
  • Repeat contacts: customers who return within a few days about the same issue weren't really helped the first time
  • Time to first human reply after a handoff
  • Handoff reasons, reviewed weekly to find flows worth fixing

If containment rises while satisfaction falls, the bot is blocking people instead of helping them. Aim for a bot that resolves what it can, hands over everything else quickly, and tells the agent enough that the customer never has to repeat themselves.

Keep reading

Start your first WhatsApp campaign today

Connect your number, import your contacts and send your first message in an afternoon.

14-day free trial · No credit card required