Academy › Build › WhatsApp and customers

When the bot hands off to you

By the end, you'll have written the first message you send when you pick up a conversation handed off by the bot, including what you understood and when you'll reply, and you'll have checked how the handoff alert reaches you.

By Yodai · Published on September 6, 2026 · Updated on October 12, 2026

4 min read

Not every question that comes in on WhatsApp ends with a booking link or a payment link. The bot handles the usual questions just fine: hours, the price of a haircut, whether there's an opening Saturday. But then comes the odd message, "Can you do highlights and a straightening treatment the same day? I have a wedding," and that's where the bot can't decide for you. What does the customer see in that moment? And how do you find out it's your turn to answer?

If you haven't decided those two things ahead of time, here's the worst thing that can happen to a conversation: the customer is left with an "I'll get back to you" that goes nowhere, or you find out two hours late because the alert got buried in your phone's notifications.

When the handoff kicks in

There are moments in a conversation where the decision isn't the bot's to make. Here you need to decide exactly what happens in that instant, not just notice that it came in.

These are two different situations: the customer asks to talk to a person ("I want to talk to someone," "this won't work for me, call me"), or asks something the bot can't answer. In the first case, the customer already knows what they want, and that's when the bot hands you the conversation. In the second, check what your bot does: if it doesn't hand off on its own, it'll answer with what it knows, and the customer doesn't always notice they've hit a limit. That's why it helps for the customer to know they can ask for a person, and for you to read those conversations so you can step in on time.

Handoff by request or handoff by uncertainty

The customer asks for a person

They already know they want to talk to you, not the bot
Your first message can be short: confirm that you've seen it
There's no need to explain why you're handing it off

The bot doesn't know how to answer

The customer doesn't always notice they've hit a limit
Your message needs to say what's happening, not just "hold on"
It helps to repeat in one line what they asked, so they know they've been understood

Which one I pick: When the customer asks for a person, you confirm and that's it. When it's the bot that's stuck without an answer, spend one more sentence saying what you understood, because otherwise the customer doesn't know if you read their message or the bot just froze.

The sentence the customer sees

The handoff message has one job: making sure the customer doesn't feel like they've been talking to a wall. That means two things always get written, even if the rest of the message changes: what you understood they're asking for, and when they can expect a reply. If your bot doesn't let you write that message, because it hands off with a short, always-the-same notice like "a team member will get back to you here as soon as they can", those two things go in the first message you send when you pick up the conversation, and the sooner it gets there, the better.

"By when" isn't "shortly." It's a window you can actually keep: "before 2 pm," "this afternoon," "as soon as we open tomorrow." If you promise a window and miss it three times in a row, the customer stops believing the phrase altogether and messages you twice just to make sure.

Any message where you send a link follows the same principle: it's about giving something concrete instead of an empty promise.

Your first message when you pick up the conversation

Highlights and a blowout the same day is something I need to check to see if we can fit you in. I'll get back to you before 2:00 PM. If you're in a rush for the wedding, tell me the date and I'll confirm with that.

The alert that reaches you

What the customer reads is half the job. The other half is what reaches you, because a handoff with no alert is a customer waiting with nobody aware of it.

You need to know three things without reading the whole conversation: who's writing, what they asked for, and how long they've been waiting. Before you turn the bot on, trigger a handoff yourself from another number and see what notice you get and where. If it doesn't tell you those three things, you'll end up opening conversations one by one to figure out which one's urgent, and it's better to know that before you have a customer waiting.

Sort by wait time, not by order of arrival: the one who's been waiting fifteen minutes goes before the one who just wrote in, even if the second one looks easier to answer.

The sentence that repeats itself without saying anything

The costly mistake is when the only thing the customer reads is a generic line, something like "a team member will be with you shortly." It works the first time; by the third time, the customer notices it's a template and that nobody read what they wrote. If your bot hands off with a fixed message, your first message is what fixes it: it only takes one more line to say what you understood from their message, and that line is what makes them notice there's a person on the other end, not an answering machine.

What you'll walk away with

Your first message when you pick up the conversation is built for both situations: when the customer asks for a person and when the bot doesn't know how to answer
That message says what you understood and by when you'll answer, with a time window you can actually keep
You know how and where the heads-up reaches you when it's your turn to answer, because you've tested it, and you handle things by wait time, not by order of arrival
Still to do: test the bot with the real questions your own customers ask

In Yodai the WhatsApp bot answers with your prices and your hours, and hands the chat over when someone asks for a person. See how the WhatsApp bot for your business works.

NextTest it with the questions people actually ask you, not the easy ones