When the assistant hands over to a person

Published on October 06, 2026

The assistant hands a conversation to a person when the case goes off script.

It handles what it was written and trained for, and passes on the rest with the history attached, without guessing.

What takes a case off script

Anything that needs a person’s decision, or that the assistant can’t answer with confidence:

Health questions. It doesn’t give clinical advice, and that is a firm rule, not a preference.
Price exceptions, discounts or terms outside what was agreed.
Complaints, and chats where the customer is already unhappy.
Negotiation beyond the price list.
Questions whose answers aren’t in your business content.
An unclear calendar, when there is no way to tell whether a slot exists.

When in doubt between answering and handing over, the rule is to hand over.

A service that makes up answers about health, money or deadlines creates a bigger problem than the original question.

What goes with the handoff

Nobody starts from scratch.

Everything already discussed goes along, so whoever takes over knows where the chat stands.

That includes the customer’s name and contact, when the chat happened and a summary of what was said.

It includes anything agreed, if there was something.

And it includes where the chat stopped and why it went off script.

The record keeps the customer, time, summary and status.

The chat also moves the person to their current stage in the funnel.

What the customer sees

The customer is told.

The assistant says a person will reply, instead of leaving the chat silent.

After hours, the notice says when someone will reply.

Everything is noted for the next day, and whoever takes over has the full context.

While they wait, nothing stalls.

Prices, hours, booking and reminders keep working, and what they already sorted out isn’t lost in the queue.

When handing over is worse than answering

Handing over isn’t always right.

When the assistant already knows the answer, passing the chat to a person just adds waiting time.

Questions about prices, hours, address, lead times and services belong to the assistant.

It is on the number, even in the middle of the night, without needing anyone awake.

Handing over everything costs the same as before you signed up: busy staff answering the same question, customers waiting and empty slots.

A handoff rule that is too loose hands you back the very queue you wanted to get rid of.

What stays automated

A handoff is one moment in the chat, not the end of the service.

Even after a case is passed on:

The calendar keeps working. Booking, rescheduling and cancelling carry on as usual.
The three reminders keep going out: 72 hours, 24 hours and 2 hours before the appointment.
Records keep being saved, with customer, time, summary and status.
Price and hours questions keep getting answered right away, without anyone stepping in.

The 72-hour reminder usually goes out after the WhatsApp 24-hour window has closed.

So it is sent as a utility template, which Meta charges per message and which does not count toward the 1,000 free service messages of the month (Meta’s charging rules).

What you decide first

The handoff is a setting, and what it passes on is your call.

Write this down before going live:

Which topics go to a person, and which the assistant handles.
What hours someone is available to take the chat.
What happens outside those hours: whether the notice says when a reply will come, or someone is on call.
Who receives it, and where: the service WhatsApp, your own or the dashboard.

Without these answers, the handoff is either too loose or happens too soon.

Both are mistakes.

One hands the queue back to your team, and the other leaves the customer without an answer.

Our WhatsApp runs the assistant we set up, already live.