When to Automate — and When to Hand Off to a Human
By Masego · 2026-07-15
The best bots know their limits. Handoff is a feature, not a failure — and context quality is the metric that proves it.
01 · The wrong goal
Automation fails when organisations treat 100% bot resolution as the goal. The goal is the right outcome — fast when routine, human when judgment is required.
“Handoff is a feature, not a failure.”
100%
bot resolution is the wrong north star
0
repeats of facts already collected
1
continuous number across bot and agent
02 · Clear handoff triggers
- 01Explicit user request ("speak to someone")
- 02Repeated failed intent matching
- 03High-value sales opportunities
- 04Regulated advice (insurance pricing, legal guidance)
- 05Any message flagged urgent by triage rules
03 · Inbox experience is the product
Agents need conversation context, variables collected by the bot, and media attachments already visible. A handoff that forces the citizen to repeat themselves destroys trust faster than no bot at all.
- Context and variables above the fold
- Media attachments already visible
- Same WhatsApp number across the seam
CerebroNovus models handoff as a first-class flow node — conversation status moves to escalated, bot execution pauses, and agents reply from the same WhatsApp number.
“That continuity is what citizens expect — and what reopen rates will confirm.”
See how organisations deploy these patterns on WhatsApp — people first, systems second.