The Transfer action is one of the most powerful call control tools, enabling your AI agents to seamlessly route conversations to the right destination when specialized help is needed. Whether transferring to human specialists, other AI agents, or external phone systems, proper transfer configuration ensures smooth handoffs that maintain customer satisfaction.This comprehensive guide covers everything you need to know about transfer destinations, transfer modes, advanced settings, and best practices for reliable call routing.
Transfers happen in real-time during active calls. The customer stays on the line while being connected to the new destination - they don’t get hung up on or need to call back.
When a customer reports a technical issue that requires troubleshooting:1. Gather basic information about the problem2. Explain you're connecting them to a technical specialist3. Use the 'Transfer to Technical Agent' action
Phone Number Transfer
Transfer calls to external phone numbers - mobile phones, landlines, or business numbers.
For urgent issues outside business hours:1. Verify the issue is truly urgent2. Collect key details (customer name, issue summary)3. Explain you're connecting to the on-call manager4. Use the 'Transfer to On-Call Manager' action
SIP Address Transfer
Transfer calls to SIP addresses (Session Initiation Protocol URIs) for integration with PBX systems and contact centers.
SIP transfers are ideal for enterprises with existing phone systems. They provide seamless integration between AI agents and traditional telephony infrastructure.
SIP transfers only work during active phone calls. They cannot be used during web calls or widget conversations.
Customer: "I have a billing question"Agent: "I'd be happy to help. Let me connect you with our billing department who can access your account details."[Cold transfer to billing → Agent disconnects]Billing Agent: "Hello, how can I help you?"Customer: "I have a question about my bill..."
You can enable Silent Transfer mode where the agent transfers without saying anything - the call is immediately routed to the destination.How it works:
Agent logic triggers transfer need
Transfer executes without announcement
Customer routed to destination silently
When to use:
Pure routing, no conversation yet (IVR replacement)
Menu-based routing
Language detection and auto-routing
Configuration:
Check the Silent Transfer checkbox
Any transfer message is ignored when silent mode is enabled
Example:
Copy
Agent: Language Router (silent routing agent)Instructions:Based on the language the customer speaks:- If Spanish detected, use 'Transfer to Spanish Agent' (silent)- If French detected, use 'Transfer to French Agent' (silent)- If English, continue conversation
Silent transfers can feel abrupt to customers. Use sparingly and only when appropriate for the use case.
Warm transfers use a three-way call approach: the customer hears hold music while the AI initiates a new call to the destination in the background. Once the destination answers, the AI provides context (via whisper message, summary, or three-way introduction) before connecting the customer. This ensures the receiving agent is briefed and prepared before speaking with the customer.How it works:
Customer placed on hold (hears hold music)
AI initiates new call to destination in background
Destination answers, AI provides briefing
Customer connected to briefed destination agent
Key difference from cold transfer: AI maintains both call legs and briefs the destination before connecting the customer, rather than disconnecting immediately.This feature is currently in development and will be available in a future release.
Create multiple transfer actions for different destinations to handle various routing scenarios:
Complete Routing Configuration
Configure multiple transfer destinations for comprehensive routing:
Copy
Agent: Customer Service RouterTransfer Actions Configured:1. Transfer to Billing Department (+1-555-100-0001)2. Transfer to Technical Support (+1-555-100-0002)3. Transfer to Sales Team (+1-555-100-0003)4. Transfer to Returns Department (+1-555-100-0004)5. Transfer to Manager (sip:manager@pbx.company.com)6. Transfer to Spanish Agent (Agent ID: ag_spanish_01)Instructions:Route customers to appropriate department:Billing questions → 'Transfer to Billing Department'Technical issues → 'Transfer to Technical Support'Sales inquiries → 'Transfer to Sales Team'Return requests → 'Transfer to Returns Department'Escalations → 'Transfer to Manager'Spanish speakers → 'Transfer to Spanish Agent'Always explain who you're connecting them to before transferring.
Fallback Chains
Configure multiple transfer options with fallback logic:
Copy
Primary escalation path:1. Attempt 'Transfer to Technical Support'2. If fails, attempt 'Transfer to General Support'3. If that fails, attempt 'Transfer to Manager'4. If all fail, apologize and schedule callbackInstructions:If the primary transfer fails, the agent should try the backup,and handle complete failure gracefully by collecting callback info.
Conditional Routing
Use different transfers based on customer data or conversation context:
Copy
{% if contact_account_type == "enterprise" %}Route enterprise customers to 'Transfer to Enterprise Support'{% elif contact_account_type == "premium" %}Route premium customers to 'Transfer to Premium Support'{% else %}Route standard customers to 'Transfer to General Support'{% endif %}
Never transfer calls without context. Explain who you’re connecting them to and why.Good:
Copy
"I understand you need help with your bill. Let me connect youwith our billing department who can access your account andmake any necessary adjustments. This should just take a moment."
Poor:
Copy
"Hold please." [immediate transfer]
Set Customer Expectations
Tell customers what to expect during and after the transfer.Good:
Copy
"I'm going to connect you with our technical team. You'll heara brief hold message, then they'll pick up within 30 seconds.They'll have your information ready."
Collect basic details before transferring so the recipient has context and the customer doesn’t need to repeat themselves.
Copy
Before transferring:1. Get customer name2. Understand basic issue3. Collect account/order number if relevant4. Ask about urgency5. Then transfer with context
Use Descriptive Names
Name each transfer action clearly based on destination.Good:
“Transfer to Billing Department”
“Escalate to Technical Support”
“Route to Spanish-Speaking Agent”
“Connect to On-Call Manager”
Poor:
“Transfer 1”
“Phone Transfer”
“Escalate”
Handle Transfer Failures
Always have a plan for when transfers fail (busy, no answer, etc.).
Copy
If 'Transfer to Support' action fails:1. Apologize: "I apologize, I'm having trouble connecting right now"2. Offer callback: "I can have our support team call you back within the next hour"3. Collect callback number and best time4. Confirm: "Great, expect a call from us at [number] within the hour"5. Use 'End Call Politely' action
Use E.164 Format for Phone Numbers
Always format phone numbers correctly to avoid transfer failures.Correct E.164 format:
Include country code: +1 for US/Canada
No spaces, dashes, or punctheses
Examples: +14155551234, +442071234567
Incorrect formats:
❌ (415) 555-1234
❌ 415-555-1234
❌ 14155551234 (missing +)
❌ +1 415 555 1234 (spaces)
Consider Costs for Phone Transfers
Be mindful of telephony costs, especially for international transfers.Cost optimization:
Use agent transfers when possible (free)
Use SIP transfers for internal routing (typically free or low-cost)
Agent: Customer Support RouterTransfer Actions:- Transfer to L1 Support (sip:support-l1@queue.company.com)- Transfer to L2 Support (sip:support-l2@queue.company.com)- Transfer to Engineering (+1-555-100-9999)Instructions:Route support issues by complexity:Simple questions (password reset, account questions):- Answer directly using knowledge base- Don't transfer unless customer requestsMedium complexity (feature questions, minor bugs):- Attempt to help using knowledge base- If unable to resolve, use 'Transfer to L1 Support'High complexity (system outages, critical bugs):- Gather detailed information- Use 'Transfer to L2 Support'Critical emergencies (data loss, security incidents):- Collect all details immediately- Use 'Transfer to Engineering' without delay
Sales Qualification with Transfer
Qualify leads and route to appropriate sales team:
Copy
Agent: Sales Qualification AgentTransfer Actions:- Transfer to Inside Sales (+1-555-200-1000)- Transfer to Enterprise Sales (+1-555-200-2000)- Transfer to Customer Success (sip:cs-team@company.com)Instructions:For inbound sales inquiries:1. Greet and understand their interest2. Ask qualifying questions: - Company size - Budget range - Timeline - Decision authorityBased on responses:Small business (<50 employees, <$10k budget):- Provide self-service resources- Offer to schedule demo via booking action- Don't transfer unless they requestMid-market (50-500 employees, $10k-$100k budget):- Use 'Transfer to Inside Sales'- Explain: "I'm connecting you with an account executive who can discuss our mid-market packages"Enterprise (500+ employees, $100k+ budget):- Use 'Transfer to Enterprise Sales'- Explain: "I'm connecting you with our enterprise team who specializes in large deployments"Existing customer wanting expansion:- Use 'Transfer to Customer Success'
After-Hours Routing
Handle calls outside business hours:
Best practice: If you have a PBX system, handle after-hours routing at the PBX level for superior reliability and control.
Copy
Agent: After-Hours SupportTransfer Actions:- Transfer to On-Call Engineer (+1-555-emergency)- Transfer to Voicemail (sip:vm@pbx.company.com)Instructions:Outside normal business hours (Mon-Fri 9am-5pm):1. Greet: "Thank you for calling. Our offices are currently closed."2. Ask about urgency: "Is this an urgent issue affecting your business operations?"If urgent/emergency:- Gather details: name, company, issue description, impact- Explain: "I'm connecting you to our on-call engineer who can help immediately"- Use 'Transfer to On-Call Engineer'If not urgent:- Explain business hours- Offer options: a) Leave voicemail (Use 'Transfer to Voicemail') b) Schedule callback for next business day (Use booking action) c) Visit self-service knowledge base
Use variables to dynamically determine transfer destinations:
Copy
{% if contact_region == "west" %}Transfer destination: +1-555-WEST-001{% elif contact_region == "east" %}Transfer destination: +1-555-EAST-001{% else %}Transfer destination: +1-555-MAIN-001{% endif %}When transferring, use the appropriate regional number.
Time-Based Routing
Route transfers based on time of day:
Copy
{% set current_hour = current_datetime | date('H') | int %}{% if current_hour >= 9 and current_hour < 17 %}Business hours: Use 'Transfer to Support Team'{% else %}After hours: Use 'Transfer to On-Call Support'{% endif %}
The current_datetime variable must be passed to your agent via Dynamic Context. Configure a context endpoint that returns this data in your agent’s operational settings.
Skill-Based Routing
Route based on required expertise:
Copy
Determine required skill:- Billing question → 'Transfer to Billing Specialist'- Technical issue → 'Transfer to Technical Support'- Product question → 'Transfer to Product Expert'- Account management → 'Transfer to Account Manager'Use customer's account type to influence routing:- VIP accounts always get priority queue transfers- Enterprise accounts route to dedicated support- Standard accounts route to general support queue