Recipe: Graceful Handover to a Team
A complete configuration that takes a stack from “the AI hands off whenever” to “the AI gathers what’s needed, hands off cleanly, and behaves correctly outside business hours.” Use this when you have one destination team and want a polished customer experience.
What you’ll end up with
- Handover mode:
explicit_team— the Fixed team card on the Delivery tab (single destination team). - Three prerequisites: the built-in contact Email (always required), an order ID (only when the conversation is about an order), and a description of the issue (always required).
- Outside-hours: Offer a follow-up in this conversation on, no close-and-reach-out-later. Confirmation before handover left off — that toggle is not an outside-hours option, it applies to every handover.
- A handoff message tone that matches your personality preset.
Before you start
- The stack and at least one specialist are configured.
- The destination team exists in Settings → Teams with members assigned, and its opening hours are set in Settings → Opening hours → Coverage.
- A conversation custom field for the order ID exists. This one is required, not optional: the only built-in conversation field the picker offers is Subject, and the only built-in contact fields are Email and Phone — everything else has to be a custom field you create first. See Custom Fields.
Build the configuration
1. Turn on handover and pick the team
- Open Settings → Agent Stacks → [stack] → Handover → Triggers.
- Toggle Allow handover to humans on.
- Switch to the Delivery sub-tab.
- Under Choose where conversations get handed off, select the Fixed team card. (The three cards are Never, Fixed team and Agent Stack picks — there is no “Mode” dropdown.)
- Which team? — pick the destination team from the combobox. Save stays disabled until you do.
- Handover instructions (optional): leave blank or add a tone-shaping rule like “Apologize once for any wait if the conversation is more than 5 turns old, then hand off without further apology.”
2. Add prerequisites
Switch to the Prerequisites sub-tab and use Add requirement three times — once per requirement, filling in the panel and clicking Save each time:
- 1 — Email — the built-in Contact (CRM) field — Always required — Ask for the email address on the customer’s account.
- 2 — your order-ID conversation custom field — Only when… “the conversation is about a specific order or transaction” — Ask which order number this is about.
- 3 — your issue-description conversation custom field — Always required — Ask for a one-sentence description of what’s not working.
Use the last column to describe what the AI should collect, not as exact customer-facing copy — that text is never sent to the customer. The live customer question is generated from the field’s name, in the customer’s language, so it won’t match this wording.
Email and Phone prerequisites save to the contact’s addresses and require well-formed values, such as a valid email address or phone number.
Reorder if needed using the up/down arrows. The AI will check each one in order before handing off.
3. Configure outside-hours behavior
Still on the Delivery sub-tab:
- Check opening hours before handing over: on (it ships off)
- Offer a follow-up in this conversation: on (default) — nested under the hours checkbox, so it only appears once that is on
- Offer to close and reach out later: off
- Ask the customer to confirm before handing over: off. This one sits outside the hours block and applies to every handover, in hours or out — it is not an outside-hours option.
This means: during business hours, the AI hands off seamlessly. Outside hours, the AI offers the customer a follow-up in the conversation as a choice. The Prerequisites gate still applies first: the AI asks for each missing applicable requirement before anything else happens. The one exception is the order-ID and issue-description fields: if the customer clearly says they don’t have that value, Atender stops asking and hands over without it. On webchat, the Email requirement has no such exception; the AI keeps asking for it. When the chat widget needs a confirmed email (a required Email requirement or an email follow-up), the code ask goes out 2 times. After that, each reply gets one last line explaining that nothing is passed to a colleague without a confirmed email, and the code entry stays open. A correct code at any later point still hands over, and this attempt is never given up. An optional chat address is asked for at most twice. If the customer clearly refuses it in the reply to the first ask, in any language, the handover goes through on that reply and the internal note says the customer did not want to give the address and quotes the reply. For any other reply the second ask still goes out, and the handover follows the reply after it. A required tenant field is still asked next after a refusal, and the required Email requirement and the confirmed-email code ask are unchanged.
On web chat with the team closed, the customer is told when the team reopens, and the handover commits at once. The team gets the case immediately and replies in the chat. Unless the customer already has a confirmed email address (or a confirmed phone while SMS is on), or your workspace cannot send email, Atender emails the customer a link, but it only confirms the address; an unopened link closes nothing and does not hold up the handover. If the team writes a reply after the visitor has left, it also goes to a confirmed email address, or to a confirmed phone by text message when SMS is on.
4. Save and test
- Click Save on the Delivery sub-tab.
- Test in a real conversation — for example the web chat widget — and send a message that should trigger handover: “I want to talk to a human about my order #12345.”
- The AI should ask for the account email (and accept the order number you already provided), then briefly ask for the issue description.
- Confirm the prerequisites are gathered before the handover commits: the conversation should only be assigned to the team, with the AI switched off, once nothing applicable is missing. If the customer clearly says they don’t have an order number or can’t describe the issue, the handover goes ahead without that field; on webchat, saying they have no email does not release the Email requirement. When the widget needs a confirmed email, the code ask goes out 2 times, then each reply carries one last line saying nothing is passed to a colleague without a confirmed email, and the code entry stays open. A correct code at any later point still hands over.
The Testing tab is not the place for this check. A test run skips the entire handover step — the prerequisite gate, the outside-hours and confirmation deferrals and the commit itself all no-op in test mode — so the stack will never ask for a prerequisite there, and no handover state is written.
Verify it worked
- The Prerequisites tab lists exactly three rows.
- The Delivery tab has the Fixed team card selected and your team in Which team?.
- In a real conversation, the AI asks for missing prerequisites in the order you listed them. It stops asking for the order ID or the issue description once the customer clearly says they don’t have it, but not for the email.
- Outside-hours check (close the team’s hours temporarily, or test against a closed team) offers a follow-up in the conversation rather than handing over immediately. On web chat, the AI should still ask for any missing applicable prerequisites first (except an order ID or issue description the customer said they don’t have). Then the customer is told when the team reopens, the handover commits at once, and the team has the case immediately and replies in the chat. The emailed link only confirms the address; leaving it unopened closes nothing.
Variations
- Two-team setup with topic-based routing: switch to the Agent Stack picks card (
by_description), give each team a description — that is what the model routes on — and use Handover instructions to steer the choice further. - More prerequisites for high-value customers: add a fourth prerequisite on a loyalty-tier custom field, set to Only when… “the customer has not provided one”, to capture context the human will want.
- Strict consent: turn Ask the customer to confirm before handing over on if your team prefers customers to opt in explicitly before being transferred.
Troubleshooting
- Symptom: The AI sometimes hands off without asking for the email. Fix: the gate is not best-effort — on the stack’s own handover path a missing applicable prerequisite blocks the commit and the AI asks for it instead. Handovers that skip the gate come from elsewhere: an automation rule running the Hand over to a human (turn off Agent Stack) action calls the handover directly, and so does a system stand-down when the AI cannot reply at all. Check your automation rules before re-editing the prerequisite.
- Symptom: On an email conversation, the team gets the handover with a prerequisite still empty. Fix: this is expected on email. The AI asks for each missing detail at most twice (the second ask says it is the second request); after that it hands the conversation to the team without it and adds an internal note quoting what the customer wrote after the first question. Other channels never hand over without the detail: after 10 asks in one handover attempt, the attempt is given up. The exception is the code ask for a confirmed email on the chat widget (a required Email requirement or an email follow-up). That ask goes out 2 times, and after that each reply gets one last line explaining that nothing is passed to a colleague without a confirmed email, while the code entry stays open. A correct code at any later point still hands over, and this attempt is never given up. An optional chat address is asked for at most twice. If the customer clearly refuses it in the reply to the first ask, in any language, the handover goes through on that reply and the internal note says the customer did not want to give the address and quotes the reply. For any other reply the second ask still goes out, and the handover follows the reply after it. A required tenant field is still asked next after a refusal, and the required Email requirement and the confirmed-email code ask are unchanged. On email, the built-in Email requirement is normally already met by the sender’s address.
- Symptom: Outside-hours fires during business hours. Fix: double-check the opening-hours rule that resolves for that team and channel, including timezone. Hours are resolved per team and channel; a team with no assignment for the channel falls back to the tenant default, and with no default at all the slot counts as open. See Opening Hours.
- Symptom: Handover triggers but nobody picks the conversation up. Fix: first confirm the destination team has at least one available member. Atender blocks deleting a team while an Agent Stack hands over to it, so if you need to remove that team, first point each affected stack at another team or change its handover mode, then delete the team.