When the chatbot should stop and hand off to a person
Operational escalation signals: frustration, high stakes, sensitive data and after-hours — without leaving the customer in an empty loop.
What you’ll take away
- Hand-off is conversation design, not proof the bot failed.
- Write rules for frustration, risk and intent — not only “I don’t know.”
- The human must get context, not a blank chat.
A chatbot that tries to solve everything frustrates people. One that escalates too early saves no time. The middle ground is written rules, not model vibes.
Signals that need a human now
- Repeated frustration — the user rephrases the same complaint three times or uses angry language.
- High stakes — cancellations, claims, large quotes.
- Sensitive data — health, minors, bank details outside the allowed flow.
- Explicit ask — “I want to talk to someone” is not a debate.
- Out of coverage — the bot lacks the policy or stock; hand off rather than invent.
What the hand-off must carry
Whoever picks up needs: a summary, data already captured (name, order, channel) and the reason for escalation. If the human starts from zero, the customer feels the bot only wasted time.
Watch out: “someone will be with you shortly” with no real queue or SLA is worse than an honest response window.
After hours
Honest options: a structured message, a callback slot, or escalation to a channel that is actually watched (email, ticket). Faking “an agent is typing…” destroys trust.
How we design it at Bitora
On a business chatbot escalation is in scope from day one. Starting prices and timelines (under two weeks with a closed scope) live on pricing and chatbots for business.
Does this fit your company?
AI agents and automation →You may also like
September 9, 20261 min read
Signs you need a diagnostic (not another spreadsheet)
When Excel and the inbox are no longer enough: when to ask for an opportunity map and what a free diagnostic should deliver.
August 31, 20262 min read
Customer support automation: where to start without breaking what already works
The first automations that pay off in support are rarely the flashiest. A practical order for SMEs that want fewer repetitive tickets, not a robot that annoys everyone.
August 29, 20263 min read
WhatsApp chatbot for an SME: the steps in order (without skipping the basics)
From choosing the right API to defining escalation rules: a practical sequence for launching an AI assistant on WhatsApp without blocking your number or frustrating customers.
Ready to digitize your business?
Request a free diagnostic and we will return a prioritized opportunity map, not a pitch.Free · Reply in 24h · No commitment
Request a free diagnosticNo commitment · Reply in 24h · support@bitora.es
