Settingsintermediate

Handover Modes Reference

The three handover modes a stack can be configured with — never, by_description, explicit_team — and what each one means for routing handed-off conversations to humans.

4 min read

Handover Modes Reference

Each Agent Stack has one handover mode controlling whether and how the AI hands off conversations to humans. Handover is enabled with the Allow handover to humans switch on the Handover → Triggers sub-tab. While handover is enabled, the Triggers tab also shows the optional Hand over when the question is out of scope switch, which also hands over when the AI cannot verify its answer. The mode is refined on the Delivery sub-tab (which mode and which team).

The three modes

  • never — The AI never hands off — Stays in the stack until resolved or the customer leaves
  • by_description — When trigger conditions match (frustration, legal threat, escalation request, stall, “ask for a human”) — The team whose description best matches the conversation (topic, market, language, pre-chat details)
  • explicit_team — When trigger conditions match — A single team you pick from a dropdown

When to use each

never

Use never only for stacks that handle a single, narrow, closed task where there’s no meaningful human fallback — a sandbox stack, an internal-only stack, a survey collector. For real customer-facing stacks, leave handover on. Customers will eventually need a human, and never means they leave instead.

When the Allow handover to humans switch on the Triggers tab is off, the Delivery tab is greyed out and the Prerequisites tab no longer lets you add requirements — they only apply when handover is enabled. The never mode is unchanged by fallback routing behavior: it does not hand over. The one exception is a capability that needs a teammate’s approval (see below), which can hand the conversation to its existing team.

by_description

The mode the Allow handover to humans switch turns on. The AI decides which team picks up by matching the conversation against each team’s description — what topic the conversation is about, what language it’s in, and any pre-chat survey answers the customer provided, such as installed country, product, or issue type. When the customer provides this information before chat, the AI treats it as stronger evidence than conversation language, embed market, or name/language inference. Pair this with the Handover instructions (optional) text on the Delivery tab to steer the AI’s choice.

In normal handover, by_description still tries to derive a team before committing the handoff. Guardrail forced fallback is not a handover mode: it sends the fallback reply, records the fallback outcome, and keeps the AI on.

This mode is most useful when you have multiple specialist teams (Billing, Tier 2 Support, Returns) and the topic of the handed-off conversation should determine who takes it.

explicit_team

Every handover goes to one specific team. Pick the team in the Which team? field on the Delivery tab. The Save button stays disabled until a team is chosen. Use this when:

  • Your stack only covers one functional area, so one team always picks up.
  • Your team structure is small and routing-by-description would be overkill.
  • You want predictable, auditable routing for compliance reasons.

Triggers (when handover fires)

In by_description and explicit_team mode, handover triggers when any of these are detected:

  • The customer explicitly asks for a human (“can I talk to a person?”).
  • The sentiment-and-risk infrastructure agent flags the conversation as risky (frustration, legal threat, churn risk, escalation request).
  • The orchestrator detects a stall — the conversation has stopped progressing.
  • A prerequisite check completes (for stacks where the AI’s job is to gather and hand off).
  • The customer’s question is out of scope, if Hand over when the question is out of scope is turned on in Handover → Triggers. The same switch also hands over when the AI cannot verify its answer. In that case the answer is not sent, and if the check fails or times out the conversation also goes to a person.

There is one exception to the “cannot verify” case. A reply that openly says it cannot confirm something yet and asks the customer for the detail it needs is sent, and the AI continues on the next turn. This applies only when every open point needs the customer’s account data or an action. The reply is still held, and the conversation handed over, in three cases:

  • The reply skips a request the customer made.
  • The reply involves a product fact the AI does not know.
  • The reply has a confirmation link or code beside an open point.

What the customer sees on the turn the switch hands over: if the question is out of scope, no reply at all. If the AI’s answer was held back, a short fixed line instead: “I’ve passed this to a colleague — they’ll reply here.” on chat, SMS, WhatsApp and Messenger, and a line saying a colleague will get back to them by email on email. This fixed line applies only to held replies; a reply that is sent under the exception above reaches the customer as written. With Hand over without a reply to the customer on, an email customer gets nothing. The switch is not used on voice.

A capability with Needs a teammate’s approval turned on hands over outside these triggers. After the customer confirms the action, the action waits for a teammate to approve it and the conversation goes to a team: the team it already has; if it has none, a by_description stack picks one from what the customer wrote (or leaves it with no team), and an explicit_team stack uses its selected team. On a never stack, this works only when the conversation already has a team. A teammate then approves or declines the action, and either takes the conversation over or returns it to the Agent Stack.

Required information

Before handing off, the AI tries to collect everything in the Prerequisites sub-tab. Each prerequisite has an always or when condition, and the AI asks the customer for each missing detail before triggering the handoff. How many times it asks depends on the channel:

  • Email: the AI asks at most twice per detail. The second email says it is the second request and that the case moves on without the detail. After that, the conversation is handed over automatically, with an internal note that quotes what the customer wrote.
  • Other channels: the AI asks up to 10 times per handover attempt, counted across all details. When that limit is reached, the attempt is given up without a handover. Two cases work differently:
  • The chat widget’s own email address: this is optional unless an email follow-up needs it, and asked at most twice. After the second ask, the next reply hands over without the address once nothing else is missing.
  • A required code (for an email follow-up, an always-closed chat, or a workspace field that needs a confirmed email): the code is asked twice. After that, each reply gets a fixed line saying the customer cannot be passed to a colleague without a confirmed address. The code entry stays open, so a later correct code hands over as normal. This attempt is never given up, and nobody is handed over without the confirmed address.

On email, the question follows the AI’s own answer when one is kept; otherwise it is a short email of its own (greeting, reason and question, closing). Superadmins see a Handover gate section in the debug panel of an AI message when the gate ran on that turn.

Delivery options

All four options live on the Delivery tab, below the mode picker, and appear once the mode is anything other than Never.

  • Check opening hours before handing over — off — If the destination team is closed, keep the conversation with the stack and offer the customer options instead of handing off
  • Offer a follow-up in this conversation — on — Tells the customer when the team opens again, and the team replies in the same conversation
  • Offer to close and reach out later — off — Lets the customer close the conversation and try again during opening hours
  • Ask the customer to confirm before handing over — off — The stack explains the transfer and waits for confirmation, in the customer’s language (except on email when Hand over without a reply to the customer is on, see below)

Only the two middle options are outside-hours options. Offer a follow-up in this conversation and Offer to close and reach out later are nested under Check opening hours before handing over and are shown only while it is on. Ask the customer to confirm before handing over is an independent toggle that applies to every handover, in hours or out (except on email when Hand over without a reply to the customer is on) — do not read it as an outside-hours choice.

Both outside-hours options can be on at once; the AI presents them as choices to the customer.

Hand over without a reply on email

This switch is not on the Delivery tab. It is Hand over without a reply to the customer (default: off), on the stack’s Personality tab under Channel preferences → Email, in the Behaviour box, and it is saved with that tab’s Save button. While the handover mode is never, the switch can’t be turned on.

On email, a committed handover sends the customer no message and skips the confirmation question; the team still sees the conversation and the reason. Chat, voice, SMS, WhatsApp and Messenger are unchanged.

It is independent of the opening-hours block: it does not depend on Check opening hours before handing over, and turning it on does not change that block. It only silences the message sent at the moment of a committed handover. Questions for missing prerequisites, outside-hours offers, and failed-handover messages are still sent. When no team can be reached, the “can’t reach a teammate” reply is never sent on email, with or without this switch: the AI stands down and the conversation is handed over to a person instead.

Handover instructions

The free-form Handover instructions (optional) text on the Delivery tab (up to 15,000 characters) is appended to the AI’s prompt when it’s deciding how to hand off. Use it for:

  • Tone for the handoff message (“apologize for the wait if the conversation lasted more than 5 turns”).
  • Information to always include in the handoff pack (“mention loyalty status if it’s Gold or Platinum”).
  • Things to never reveal in the handoff message (“don’t tell the customer which team is picking up”).

See also

Tags

Ai FeaturesReference