Overview
Transfer to Agent allows your AI agent to dynamically transfer the active call to a completely different AI agent during the conversation. This enables specialized handling of different scenarios, departments, or expertise areas.The call transfers to the published version in the current language, or falls back to the default language version of the target agent.
How It Works
When a conversation requires expertise from a different agent, your current agent can:- Detect the transfer need based on your configured conditions
- Say a transition message to inform the customer
- Transfer to the target agent (published version in current language or default)
- Continue the conversation with the new agent using a custom opening message
Transfer vs Switch Language
- Transfer to Agent
- Switch Language
Purpose: Transfer to a different AI agent with different expertiseWhat Changes:
- Different agent personality
- Different system prompt
- Different capabilities
- Different knowledge base
- Customer needs different department
- Specialized expertise required
- Escalation needed
Configuration
1
Click Add Transfer Agent
In your agent configuration, find the Transfer to Agent section and click “Add Transfer Agent”
2
Select Target Agent
Choose which agent to transfer calls to from the dropdownImportant: Only agents you’ve created will appear in the list
3
Define When to Transfer
Write a clear description of when the current agent should transfer to this agentExample:
4
Set Transition Message (Optional)
Message while transferring: What the current agent says before transferringExample: “Let me connect you with our technical support team who can better assist you.”
5
Set Opening Message (Optional)
Start message after transfer: First message from the new agentExample: “Hi! I’m the technical support specialist. I’d be happy to help with your issue. Can you tell me what’s happening?”
6
Save Configuration
Click “Add Agent” to save
Language Handling
The transfer intelligently handles language versions: Scenario 1: Same Language AvailableConfiguration Fields
Agent
Agent
Required: YesPurpose: The target agent to transfer calls toSelection: Choose from your list of created agentsImportant: Target agent must be published for transfers to work
When to Transfer
When to Transfer
Required: YesPurpose: Tells the AI when to trigger the transferBest Practices:Avoid:
- List specific scenarios and keywords
- Include department names
- Mention common customer phrases
- Cover all relevant topics
Message While Transferring
Message While Transferring
Required: No (but recommended)Purpose: What the current agent says before transferringTips:
- Explain what’s happening
- Set customer expectations
- Be professional and reassuring
- Keep it brief
Start Message After Transfer
Start Message After Transfer
Required: No (but recommended)Purpose: First message from the new agent after transferTips:
- Greet the customer warmly
- Introduce the new agent’s role
- Acknowledge the transfer
- Ask how to help
Use Cases
Department Routing
Scenario: Route customers to appropriate department Configuration: Transfer to: Technical Support AgentExpertise Escalation
Scenario: escalate complex issues to specialist agents Configuration:Language + Department Transfer
Scenario: Customer needs different department AND prefers native language Current Agent: General Support (English) Transfer to: Billing Agent (Hindi) Configuration:Best Practices
Publish Target Agents First
Publish Target Agents First
Before configuring transfers:
- Create and configure target agents
- Test each agent independently
- Publish all versions
- Then configure transfers
Be Specific in Trigger Descriptions
Be Specific in Trigger Descriptions
Include:
- Keywords customers use
- Common phrases
- Synonyms and variations
- Department names
- Topic areas
Provide Context in Transfer Messages
Provide Context in Transfer Messages
Help customers understand why they’re being transferred:Good:
- “I’ll connect you with our specialist who handles this.”
- “Let me transfer you to the team that can best help.”
- “Our [department] team is better equipped for this.”
- “Transferring…” (no context)
- “Hold on” (unclear)
Acknowledge the Transfer in Opening
Acknowledge the Transfer in Opening
New agent should:
- Greet warmly
- Acknowledge they understand why customer was transferred
- Reassure customer they’re in the right place
Avoid Transfer Loops
Avoid Transfer Loops
Problem: Customer gets transferred back and forthSolution:
- Make trigger descriptions mutually exclusive
- Don’t configure bidirectional transfers for same topic
- Test transfer paths thoroughly
Test All Transfer Paths
Test All Transfer Paths
Before going live:
- Test each transfer configuration
- Verify smooth handoff
- Check language handling
- Ensure messages are appropriate
- Confirm target agents work correctly
Example Configurations
E-commerce Platform
Product Inquiry Agent → Sales AgentHealthcare Services
Appointment Booking → Specialist ConsultationFinancial Services
General Inquiry → Loan OfficerTroubleshooting
Transfer not triggering
Transfer not triggering
Possible Causes:
- Trigger description too vague
- Target agent not published
- AI doesn’t recognize request
- Make trigger description more specific
- Verify target agent is published
- Add more keyword variations
- Test with explicit trigger phrases
Wrong agent receiving transfer
Wrong agent receiving transfer
Possible Causes:
- Multiple agent triggers overlap
- Similar trigger descriptions
- Make each agent’s triggers unique
- Review all transfer configurations
- Test each transfer individually
- Remove ambiguous descriptions
Transfer fails mid-call
Transfer fails mid-call
Possible Causes:
- Target agent not published
- Network/system issue
- Confirm target agent is published
- Check agent status
- Review error logs
- Contact support if persistent
Language changes unexpectedly
Language changes unexpectedly
Scenario: Customer transferred but language changedReason: Target agent doesn’t have published version in current languageSolution:
Publish target agent in all supported languages:
- Go to target agent
- Create/publish versions for each language
- Test transfers again
Context lost after transfer
Context lost after transfer
Issue: Customer must repeat information to new agentExpected Behavior: This is normal - transfers create fresh conversationsWorkaround: Train new agent’s opening message to ask for key info:
Advanced Scenarios
Multi-Level Transfers
Create transfer chains for complex routing:Conditional Transfers
Use specific conditions for smart routing: Transfer to VIP Agent:Getting Help
Test Your Transfers
Use Test Call to verify all transfer paths work smoothly before going live
Contact Support
Our team can help design optimal transfer flows for your business