AI Agent Escalation: Triage, FAQ, and Transfer to a human
Set up the AI agent to answer FAQs on its own and escalate to a human when needed — using tag and custom field triggers or instructions.
The AI agent can act as a front-line triage agent: it answers the routine, repeatable questions on its own (an FAQ agent), and escalates the conversation to a teammate the moment a human is needed. This keeps your team focused on the conversations that actually require a person, while contacts still get an instant first response.
New to the AI agent? Set it up and activate it first using How to setup AvoAI. This article assumes you already have an agent configured.
How the AI agent hands a conversation back
When the agent decides (or is triggered) to escalate, what happens next depends on whether you use auto-assignment.
Your setup | What happens on handoff |
Auto-assignment is on | Use this if you want the conversation assigned to a real, live rep on your team. The AI agent reassigns it based on your reps marked as Available on the roster and office hours. If no rep is available, see the note below. |
Auto-assignment is off | The AI agent stops replying and adds the ai_escalated tag. The conversation assignment is governed by the setting in the note below. |
When no human agent is marked as Available on the roster to take the conversation — (whether your auto-assignment is on or off) — your inbox gets an in-app notification, and the conversation assignment depends on your Convo Management setting → Reassign to Available Agent When Owner is Offline :
On — the conversation is set to Unassigned so any available teammate can pick it up. Off — the conversation stays assigned to the AI agent (it has already stopped replying).
To route handoffs to the right people automatically, add your teammates (and the AI agent) to the auto-assignment roster and set up skill routing via tags.
Before you start
- Your AI agent is configured and activated.
- Under Automation > AvoAI Agent > Configure Agent, Escalate to a Teammate is set to Yes. This turns on the agent's ability to hand off, and it's required for the handoff settings below.
- Test your setup in the Test Agent Sandbox before going live.
Two ways to configure handoff
There are two ways to tell the agent when to escalate. You can use either one or both together.
- Handoff on a tag or custom field — a deterministic trigger that always escalates, with no AI judgment involved.
- Handoff based on instructions — the agent decides when to escalate based on the conversation, using the instructions or recipes you give it.
Method 1: Hand off when a contact has a tag or custom field
This is the most reliable way to guarantee an escalation. If a contact has a matching tag or custom field value, the agent escalates immediately — it does not run the conversation through the AI first.
Go to Automation > AvoAI Agent > Configure Agent and open the Escalate to a Teammate section.
Escalate with no response when contact has any of these tags
- Select one or more existing tags from the dropdown.
- The agent escalates as soon as a contact carries any of those tags.
- Don't see the tag you need? Use Add new tags to create it.
Escalate with no response when contact custom fields match these values
- Pick a custom field and enter the value that should trigger escalation.
- Matches are case-insensitive (for example,
VIP,vip, andVIPall match).
- Use Manage custom fields to add or edit fields.
IMPT: Click Add after each tag or field
AND click Update at the bottom to save.
Tag and custom field triggers always escalate with no response — the agent hands off silently and does not send a reply, regardless of how the When Escalating, Skip Responding setting (option #9) is configured. That setting only applies to instruction-based escalations.
Pair it with auto-tagging for topic-based handoff
Tag triggers get even more powerful when combined with auto-tagging. You can have the AI agent scan incoming messages, apply a tag when it detects a topic (for example, billing or cancellation), and then use that same tag as an escalation trigger — so certain topics route straight to a human.
To set this up, follow the Auto-apply Tags to Conversations Using AvoAI guide, then add the tag you chose to the escalation trigger above.
Method 2: Configure escalation logic with instructions
For escalation that depends on what's said in the conversation (rather than a tag or field that already exists), use the agent's instructions. This is where you turn the AI agent into an FAQ agent that answers what it can and escalates the rest.
Go to Automation > AvoAI Agent > Instruct Agent.
Use recipes to get started
Click Recipes to open pre-written instruction templates you can customize:
- FAQ — give the agent the answers to your common questions so it can handle them on its own.
- Escalation Policy — tell the agent when to escalate to a human.
- Add Tags to Conversation — tell the agent when to tag a conversation (useful for Method 1).
Click a recipe to open an instruction window with editable starter content, adjust it for your business, and save.
Write clear escalation instructions
Escalation instructions work best as simple "if this, then that" statements.
Example escalation instructions:
If you cannot answer a question, respond with $escalation_message and escalate to an agent.
If they ask about billing or refunds, escalate to an agent.
If they ask to speak to a person, escalate to an agent.
Keep your FAQ instructions and your escalation instructions organized as separate entries so you can edit or disable one without affecting the other.
For instruction-based escalations, the When Escalating, Skip Responding setting (option #9 on the Configure Agent page) controls whether the agent sends a reply before handing off. Set it to Yes if you never want a reply sent on escalation.
For more guidance, see Best Practices for Instructions and AI Agent Use Cases & Best Practices.
Which method should I use?
- Use tags or custom fields (Method 1) when you already know a contact should always go to a human — known VIP accounts, flagged contacts, or topics you've auto-tagged. It's guaranteed and never sends a reply.
- Use instructions (Method 2) when the decision depends on what the contact says in the moment, like a question the agent can't answer.
- Many teams use both: instructions handle the day-to-day FAQ and judgment calls, and tag/field triggers act as a hard guarantee for specific contacts or topics.
Always test your escalation flow in the Test Agent Sandbox before turning it on in a live inbox.