Escalation & handoff
Escalation & human handoff
When and how the AI hands conversations to your team — handoff rules, business hours, off-hours behavior, notifications, and automations.
Escalation is how a conversation moves from the AI to a person. When a trigger fires, the agent tells the customer a human will assist, the conversation lands in your inbox flagged Needs human, and the AI stays quiet until someone takes over or closes the escalation. Configure it at app.asks.app/ai-agent/escalation.
The page runs top to bottom through four sections — Handoff rules, Availability, After handoff, and Automation — and everything saves together with the action bar at the bottom. Only owners and admins can edit; other roles see the page read-only.
Handoff rules
The Automatic handoff card leads with the Enable handoff toggle. It's on by default; with it off, the AI keeps handling every conversation itself.
Handover message. What the customer is told when the AI hands off during business hours — used for keyword and reply-limit handoffs, and whenever the AI doesn't write its own transfer message. Up to 1,000 characters; the default reads "I'm transferring you to a human agent who can better assist you."
Trigger keywords. Keywords are matched as whole words or phrases anywhere in the customer's message (two characters minimum), then handed off immediately. Prefer full phrases over broad single words — a keyword like "refund" would intercept questions your knowledge base can answer. Add your own, or click Add suggested for the defaults: speak to human, talk to agent, human agent, real person, live agent, speak to a manager. With no keywords at all, the AI still hands off based on its own judgment.
Hand off after too many AI replies. A safety net: if a conversation runs this many AI replies without resolution, it's handed off automatically. Choose 3, 5, 7, or 10 — or leave it disabled.
Sentiment. The agent can also monitor customer sentiment and escalate when a customer turns angry. This trigger is off by default and doesn't have a dashboard control — enable it via the API or contact support.

Business hours
The Human Availability (Business Hours) card holds a workspace-scoped, timezone-aware schedule: per-day open hours (overnight ranges close the next day) plus holidays, evaluated in the IANA timezone you pick, with a live line showing whether you're currently open and when you next reopen. These hours are the single source of truth for availability — your SLA policies use them too. With business hours disabled, your workspace is treated as always open.

Off-hours behavior
In the Off-hours handoff card, turn on Use an off-hours message and an escalation outside business hours still hands the conversation off — but instead of promising a live transfer, the agent sends your off-hours message telling the customer when the team will be back.
The message (up to 1,000 characters) supports the {{next_open}} token, replaced with your next opening time — for example "Monday, Jun 22 at 9:00 AM (America/Toronto)". The default reads:
Our team is currently offline. I've passed this to a human agent who
will get back to you when we reopen ({{next_open}}).Optionally, turn on Ask for contact info to have the agent invite the customer to leave an email off-hours when it doesn't already have one.
Off-hours handling only takes effect once business hours are enabled above — otherwise the workspace counts as always open and the off-hours message never sends.
After handoff
The Team notifications card helps your team pick up escalations quickly:
- AI summary on handoff Business and up — posts a concise AI-written summary of the conversation as an internal note the moment it's escalated.
- Notify these emails on handoff — a list of addresses that get an email on every handoff. The card warns you when the list is empty, because then no one is told the AI handed off.

Automation
Two workspace-level automations run when a conversation goes quiet — for AI-handled and human-handled conversations alike. Auto Follow-up sends a check-in when the customer hasn't replied: set the delay (a value in minutes, hours, or days), the maximum number of follow-ups, whether to send only during business hours, and an optional closing message; AI-handled conversations get a dynamic AI-written check-in, human-handled ones your static text. Auto-resolve closes conversations that stay silent for a further timer after the final follow-up. Like everything else on the page, they save with the action bar.
What escalation looks like in the inbox
Escalated conversations carry a Needs human badge in the inbox and its customer panel, and the inbox status filter has a Needs human option so your team can work the queue directly. When a human is done, the conversation can be handed back to the AI, which resumes with the full context. See Human handoff for the agent-side workflow.
Test your rules before going live: open the Playground, type one of your trigger keywords, and confirm the agent hands off the way you expect.