Human Handoff
Human handoff is the point in a WhatsApp conversation where an automated bot steps aside and a live agent takes over. It happens when the customer's intent is complex, sensitive, high-value, or simply beyond what the flow was designed to answer. Done well, the transition is invisible to the customer — they never repeat themselves, and the agent lands mid-conversation with full context. On the WhatsApp Business API, human handoff is the bridge between automation that saves cost and human judgement that saves the sale, and getting the trigger and routing logic right is what separates a helpful bot from a frustrating one.
In one line
Human handoff is the escalation of a WhatsApp chat from a bot to a human agent for complex or sensitive queries. It relies on clear triggers, context transfer, and smart routing so customers never repeat themselves — and it works inside the 24-hour service window at no extra WhatsApp cost.What human handoff actually means
Human handoff (also called agent escalation or bot-to-human transfer) is the controlled transfer of an active conversation from automated handling to a real person. The bot handles the predictable, high-volume work — order status, opening hours, FAQ answers, appointment slots — and recognises when a query needs empathy, negotiation, or a decision it cannot make. At that moment it routes the conversation, along with everything already said, to a live agent in a shared team inbox. The defining feature of a good handoff is continuity: the customer keeps chatting in the same WhatsApp thread, and the agent inherits the full transcript rather than starting from a blank slate. Handoff is not the same as 'giving up on automation' — the strongest deployments blend both, letting the bot resolve the easy 60–80% and reserving human time for the conversations that genuinely need it.
- Bot resolves routine, repetitive, low-risk queries at scale
- Live agent takes over for nuance, negotiation, or sensitive topics
- The customer stays in one continuous WhatsApp thread throughout
- Full conversation context transfers so nothing is repeated
Why it matters for WhatsApp businesses
On WhatsApp, customers expect a fast, human-feeling reply — a rigid bot that traps them in a loop is worse than no bot at all. Human handoff protects the customer experience by ensuring that automation has an escape hatch. It also protects revenue: an abandoned cart, a pricing objection, or a complaint about a delayed order are exactly the moments where a real agent can recover the situation and a bot usually cannot. Crucially, handoff carries no extra WhatsApp messaging cost of its own. WhatsApp bills per delivered message by category (marketing, utility, authentication) since Meta moved off per-conversation billing on 1 July 2025, and replies an agent sends inside the 24-hour customer service window are free-form service messages that fall outside those paid categories. So the handoff itself does not create a new charge — it simply changes who is typing. That makes human handoff one of the highest-leverage things you can configure: better outcomes, no billing penalty.
How human handoff works in practice
A handoff has three moving parts: the trigger, the context transfer, and the routing. The trigger is the condition that fires the escalation — it can be intent-based (the customer types 'talk to a person' or 'refund'), rule-based (the bot fails to understand twice, or a chosen menu option always goes to a human), sentiment-based (frustration or anger is detected), or value-based (an enterprise lead or a high-cart-value customer). Once triggered, the platform packages the conversation history, customer profile, and any variables collected in the flow, then hands them to an agent. Routing decides which agent: it might use auto-assignment to balance load, skill-based routing to reach the right team (billing vs. sales vs. support), or language routing for regional queues. A good system also manages the reverse path — once the human resolves the issue, the conversation can be handed back to the bot for follow-ups, or closed with the 24-hour window in mind.
Common mistakes to avoid
The most frequent handoff failures are about timing and context, not technology. Escalating too late leaves customers stuck repeating themselves to a bot that clearly cannot help, and escalating too early wastes agent capacity on questions the bot should have answered. Losing context is the cardinal sin — if the agent opens the chat and asks 'How can I help you?' after the customer already explained everything, the handoff has failed. Teams also forget the 24-hour service window: if a customer message arrives and no agent replies within 24 hours, free-form service replies are no longer allowed and you must re-open the conversation with an approved template, which is a billable utility or marketing message. Finally, many businesses set up the trigger but never staff the queue — a handoff that lands in an inbox nobody watches is worse than telling the customer to email. Plan agent availability, set an SLA, and give customers a clear expectation of when a human will respond.
- Escalating too late — customers loop with an unhelpful bot
- Escalating too early — agents drown in questions the bot could answer
- Dropping context so the agent starts from zero
- Ignoring the 24-hour window and needing a paid template to re-engage
- Building the trigger but leaving the agent queue unstaffed
Frequently asked questions
What is human handoff in WhatsApp?+
Does human handoff cost extra on WhatsApp?+
When should a bot hand off to a human agent?+
What happens to the conversation history during a handoff?+
How is human handoff different from a shared team inbox?+
What is the 24-hour window and how does it affect handoff?+
Can the conversation go back to the bot after a human handles it?+
How do I route handoffs to the right agent?+
Design a handoff your customers will love
Talk to an InfiQ onboarding specialist and set up bot-to-agent escalation, smart routing, and a shared inbox that keeps every WhatsApp conversation seamless.