Human handoff: When automation should pass the chat to your team

Automated replies are only as good as the moment they step aside. Here's when a bot should hand over, what it should pass on, and how fast you reply.

An ink drawing of a shop door with a chat bubble travelling along a dotted arrow to a service bell.

WhatsApp's Business Messaging Policy says that businesses using automation to reply must also offer a prompt, clear and direct way to reach a person. Its examples run from an in-chat transfer to a human agent to a phone number, email or support form. A bot with no way out isn't just annoying. On WhatsApp, it breaks the rules.

The handoff is also where most chatbots lose customers. A bot that answers prices well but traps someone with a complaint in a loop of "Sorry, I didn't understand" does more harm than having no bot at all.

What a good handoff needs:

  • Write the list of topics that always go to a person.
  • Make "talk to a person" work from any message, in plain words.
  • Pass the conversation on with a one-line summary, so nobody asks twice.
  • Promise a reply time you can keep, and keep it.

Some topics should always go to a person

Start with a person-only list. For most service businesses it looks like this:

  • Complaints, refunds and anything that starts "I'm not happy".
  • Health, allergy and injury questions.
  • Discounts or exceptions the price list doesn't cover.
  • Anything about a child's progress, placement or behaviour.
  • Staff matters, such as asking for a specific stylist's personal number.

When a chat touches the list, the bot shouldn't attempt an answer. It should say a person will reply, and pass it on.

"Talk to a person" must work from anywhere

Customers don't use menu buttons when they're frustrated. They type "human", "can call me?", "real person pls" or "我要找人" and expect it to work. A good handoff recognises those messages in English and 中文 at any point, not only from a menu.

It should also notice when the bot is failing: the same question asked twice, an answer the customer rejects, or a long message full of detail. Those are signs to hand over without waiting to be asked.

A handoff passes the context, not just the chat

The worst handoff makes the customer start again. The person taking over should see, in one line, who it is, what they want and what the bot already said. For example: "Mei Ling, existing customer, wants to move Saturday 2pm colour, asked twice, bot couldn't find a later slot." That takes ten seconds to read and saves a frustrated customer typing it all out again.

Tell the customer what happens next

"Someone will get back to you" is not a promise anyone believes. Say who and when: "Our front desk will reply by 6pm today" or "We open at 10am tomorrow, and the team will reply first thing." Then make sure someone does. Set a phone notification for handed-over chats so they don't sink under new messages.

Out of hours, be honest. A tuition centre's bot at 11pm can still book a trial class from free slots, then hand the question about a child's learning needs to the centre manager for the morning. Our guide to after-hours enquiries covers that setup.

Staff need a short script for picking up

The first line from a person matters as much as the handoff itself. Agree a simple opener: their name, that they've read the conversation and what they'll do next. "Hi Mei Ling, it's Jun from the front desk. I can see you'd like a later slot on Saturday, so let me check with the stylist" tells the customer they aren't starting over.

If the answer needs the owner, say so and give a time. A customer told "Our owner will call you before 3pm" waits patiently. One who hears nothing for a day books somewhere else.

Some handoffs should switch to a call

A complaint, a health question or an upset parent is often better handled by phone than by more typing. Offer it: "Would it be easier if I called you now?" Afterwards, write one line in the chat with what you agreed, so both sides have a record.

Don't spread sensitive details to save time. If a customer sends photos of a skin reaction or a child's report card, keep them to the people who need to see them, and don't forward them to staff group chats.

Review the handoffs every week

Once a week, read the handed-over chats. Some will show a question the bot should have answered, which means a gap in your price list or policies. Others will show the bot answering something it shouldn't have, which means a topic to add to the person-only list. Both are ten-minute fixes, and they're how a front desk gets better each month.

Frequently asked questions

Does a WhatsApp chatbot need a way to reach a human?

Yes. WhatsApp's Business Messaging Policy says businesses using automation must offer prompt, clear and direct escalation paths, such as an in-chat transfer to a person, a phone number, email or a support form.

When should a chatbot hand over to staff?

When the topic is on your person-only list, such as complaints, refunds or health questions, when the customer asks for a person, or when the bot fails to answer the same question twice.

How fast should staff reply after a handoff?

As fast as the time you promise in the handoff message. Name a time you can keep, such as by 6pm today or first thing tomorrow, and set a notification so handed-over chats are seen.

How Furoki can help

Furoki Concierge answers from your approved prices, policies and slots in English and 中文, and hands anything on your person-only list, or anything it can't answer, to your team with the conversation attached. It tells the customer what happens next, so nobody is left waiting in a loop. Website chat is live today, and WhatsApp on your own number is rolling out with our first pilot businesses.

Ask the demo salon for a person and see how the handoff works.

Keep reading