How call escalation works
When a Voice AI agent detects that a call should be transferred, it follows a defined escalation path:- The agent recognizes an escalation trigger (keyword, sentiment, explicit request, or rule)
- The agent acknowledges the caller’s need and explains the transfer
- HoopAI routes the call to the designated team member or group
- If the transfer succeeds, the human takes over; if not, the failover logic activates
Call escalation is available for both inbound and outbound Voice AI agents. The configuration steps are the same regardless of call direction.
Transfer trigger types
HoopAI supports several types of escalation triggers. You can combine multiple triggers to create a robust escalation strategy.Keyword triggers
Define specific words or phrases that immediately trigger a transfer when the caller says them.| Keyword category | Example phrases |
|---|---|
| Direct requests | ”Talk to a person,” “speak to a human,” “transfer me,” “get me a manager” |
| Frustration signals | ”This isn’t working,” “I’m done with this,” “this is ridiculous” |
| Complex topics | ”Cancel my account,” “billing dispute,” “legal question” |
| VIP identifiers | ”I’m a premium member,” “enterprise account,” custom VIP phrases |
Sentiment-based triggers
HoopAI can analyze the caller’s tone and emotional state in real time. When the sentiment score drops below a configurable threshold, the agent automatically initiates a transfer. Sentiment analysis considers:- Tone of voice — Rising volume, rapid speech, or sharp tonal shifts
- Word choice — Negative language patterns and repeated complaints
- Conversation flow — Repeated questions, circular conversations, or increasing impatience
Explicit caller request
Any direct request to speak with a human should be honored immediately. HoopAI’s Voice AI agents are pre-trained to recognize common transfer requests, but you can expand recognition by adding custom phrases in your agent’s escalation settings.Rule-based triggers
Set up conditional rules that trigger escalation based on contact data or conversation context:- Contact tags — Automatically escalate calls from contacts tagged as “VIP” or “high-value”
- Call duration — Transfer if the call exceeds a set time limit (e.g., 5 minutes)
- Loop detection — Escalate when the AI repeats the same response more than a configurable number of times
- Topic detection — Route calls about specific topics (billing, cancellations, legal) directly to qualified team members
Warm vs cold transfers
HoopAI supports two transfer styles, each suited to different situations.Warm transfer
In a warm transfer, the Voice AI agent briefs the human team member before connecting the caller. The agent provides context such as the caller’s name, the reason for the call, and a summary of the conversation so far. When to use warm transfers:- High-value or VIP callers who expect personalized service
- Complex issues where context prevents the caller from repeating themselves
- Situations where the caller is already frustrated
During a warm transfer, the caller hears hold music or a “please hold” message while the AI briefs the team member. This typically takes 5 to 15 seconds.
Cold transfer
In a cold transfer, the call is routed directly to the human team member without any briefing. The caller is connected immediately, and the team member sees basic caller information on their screen but does not receive a conversation summary. When to use cold transfers:- Simple routing scenarios (e.g., transferring to a specific department)
- When speed matters more than context
- Low-complexity calls where the caller can quickly explain their need
Configuring call escalation
Open your Voice AI agent
Navigate to AI Agents > Voice AI in your HoopAI account. Select the agent you want to configure, or create a new one. If you need help creating an agent, see Creating Voice AI agents.
Navigate to escalation settings
In the agent editor, scroll to the Call Escalation section or click the Escalation tab in the sidebar. This is where all transfer rules are managed.
Add keyword triggers
Under Keyword Triggers, click Add Keyword and enter the words or phrases that should trigger a transfer. You can add multiple keywords, and each one is matched independently.
Configure sentiment threshold
Enable Sentiment-Based Escalation and set the sensitivity level:
For most businesses, Medium provides the best balance between automation and human intervention.
| Level | Behavior |
|---|---|
| Low | Only escalates when strong negative sentiment is detected over multiple exchanges |
| Medium | Escalates when moderate frustration is detected consistently |
| High | Escalates at the first sign of caller dissatisfaction |
Set up transfer destinations
Define where escalated calls should be routed:
- Specific user — Route to a named team member (e.g., your office manager)
- User group — Route to a team (e.g., “Sales Team” or “Support Team”) and ring all members or use round-robin
- External number — Forward to a phone number outside HoopAI (e.g., a personal mobile for after-hours)
- Queue — Place the caller in a hold queue if all team members are busy
Choose transfer style
Select either Warm Transfer or Cold Transfer as the default style. You can override this per trigger if needed — for example, use warm transfers for VIP escalations and cold transfers for simple department routing.
Configure the transfer message
“I understand you would like to speak with a team member. Let me connect you now — one moment please.”You can also customize the hold message or music the caller hears during the transfer.
Escalation to specific team members
For businesses with specialized teams, you can route different types of escalations to different people:Route by topic
Route by topic
Use topic-detection rules to send billing questions to your finance team, technical issues to support, and sales inquiries to your closers. Each topic can have its own transfer destination and style.
Route by schedule
Route by schedule
Configure time-based routing so that calls during business hours go to your in-office team, while after-hours calls route to an on-call team member or voicemail.
Route by contact data
Route by contact data
Use contact tags, custom fields, or pipeline stage to determine who handles the escalation. A contact in the “Enterprise” pipeline stage might always go to a senior account manager.
Failover when no human is available
Not every transfer will reach a human on the first attempt. Configure failover behavior so callers are never left hanging:- Retry with timeout — Ring the destination for a set number of seconds (e.g., 30 seconds) before moving to the next step
- Secondary destination — If the primary team member does not answer, route to a backup person or group
- Voicemail — If no one is available, offer to take a voicemail and create a task for follow-up
- AI continuation — Return the caller to the Voice AI agent with instructions to collect contact information and schedule a callback
- Callback scheduling — Let the AI offer to book a callback at a convenient time using your calendar integration
Best practices for call escalation
- Test every trigger — Make test calls using each keyword and scenario to verify routing works as expected
- Monitor escalation rates — If more than 30% of calls are escalating, your AI agent may need better training or prompt adjustments
- Keep transfer messages short — Callers want to reach a human quickly. A brief acknowledgment followed by the transfer is ideal
- Brief your team — Make sure human team members know they are receiving AI-transferred calls and understand how to access conversation summaries
- Review transcripts regularly — Check escalated call transcripts to identify patterns and improve your AI agent’s handling of common issues
- Set realistic expectations — If your team is small, use queue or callback options rather than promising immediate human availability
Next steps
Creating Voice AI agents
Build your first Voice AI agent from scratch with step-by-step guidance.
Testing and debugging
Test your escalation configuration and troubleshoot transfer issues.
Inbound vs outbound calls
Understand the differences between inbound and outbound Voice AI setups.
Voice AI troubleshooting
Solve common Voice AI issues including failed transfers and routing problems.