Feature 03 · Escalates to humans
When the bot can't help, a human picks up — with full context.
The moment a conversation needs a person, the whole thread lands in your team inbox — so no customer is left talking to a wall.
A bot that can't escalate just traps customers in a loop with no way out.
AI support is only as good as its exit hatch. Clanker Support is built around the hand-off: the moment a conversation needs a person, it routes the whole thread — every message, not a summary — into a shared inbox.
You set how eager it is to escalate with a per-project threshold, so the bot handles the routine questions and your team gets the ones that matter.
What you get
Full context, every time
The complete conversation moves to your inbox — your team picks up mid-thread without asking the customer to repeat themselves.
A threshold you control
Dial how readily the bot hands off, per project, so escalations match your team's capacity and risk tolerance.
No lost threads
Every hand-off is captured and tracked — nothing falls into a black hole between bot and human.
What it means in practice
- ✓Escalated conversations land in a single team inbox, not scattered across tools.
- ✓Reply from the inbox and the customer gets it by email (see Email threading).
- ✓Adjust the escalation threshold any time as you learn what the bot should handle.
Explore the rest
Drop-in widget
One script tag. Loads in a shadow DOM so your styles never leak — and theirs never leak into you.
02Answers from your docs
Paste your knowledge base or system prompt. The bot stays on-topic and admits when it doesn't know.
04Email threading
Replies go out as email and customer responses thread back into the same conversation automatically.
05Any model, any time
Built on LLM Gateway. Swap GPT, Claude, or a custom model per project — a config change, not a rewrite.
06Self-hostable
Open architecture on serverless edge infra. Run the whole stack on your own account. No surprise vendors.
Ship support today