Skip to main content

Overview

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.

Transfer Destinations

itellicoAI supports three types of transfer destinations. Choose the one that fits your workflow:
Transfer Action configuration showing Name field 'Coding Teacher', Description 'Teacher will teach coding', Transfer Type options with AI Agent selected, Select Agent dropdown showing 'Coding Teacher', Silent Transfer toggle enabled, Play Background Music toggle enabled with Music Duration set to 6 seconds, Ring Before Transfer toggle enabled with Ring Duration set to 4 seconds, and Cancel/Save buttons
Transfer Action configuration showing Name field 'Coding Teacher', Description 'Teacher will teach coding', Transfer Type options with AI Agent selected, Select Agent dropdown showing 'Coding Teacher', Silent Transfer toggle enabled, Play Background Music toggle enabled with Music Duration set to 6 seconds, Ring Before Transfer toggle enabled with Ring Duration set to 4 seconds, and Cancel/Save buttons

Agent Transfer

Transfer calls to other AI agents in your itellicoAI account.

Use Cases

Specialized Agents

Route to agents with specific knowledge (billing, technical, sales)

Language Routing

Transfer to agents configured for different languages

Department Routing

Direct to agents designed for specific departments

Skill-Based Routing

Connect to agents with specialized capabilities

Configuration

1

Select transfer type

Choose AGENT as the transfer type
2

Choose destination agent

Select the target agent from the dropdown menu
3

Optional: Add hold music

Upload audio to play while connecting (optional)
4

Optional: Add ring tone

Add a ring sound during transfer (optional)

Audio Settings

Agent transfers support customizable hold music and ring tones:Hold Music:
  • Play music while the customer waits for the transfer to connect
  • Duration: 1-30 seconds (default: 6 seconds)
  • Use for: Professional experience during connection delays
  • Not recommended for: Instant transfers when immediate connection is preferred
Ring Duration:
  • Play ringing sound while waiting for the destination agent to answer
  • Duration: 1-30 seconds (default: 4 seconds)
  • Enabled by default
  • Simulates normal calling experience
Combined Settings: You can enable both for a complete transfer experience:
  1. Music plays (e.g., 6 seconds) - Professional hold experience
  2. Ringing plays (e.g., 4 seconds) - Connection in progress
  3. Agent answers - Transfer completes
Total delay: Music duration + Ring duration (e.g., 10 seconds)
For instant agent-to-agent transfers, disable both music and ringing for immediate connection.

Benefits

  • Conversation history transfers with the call
  • No additional telephony costs
  • Instant connection (no dialing delay)
  • Full context preservation
  • Customizable hold music and ring tone

Example Instructions

When a customer reports a technical issue that requires troubleshooting:
1. Gather basic information about the problem
2. Explain you're connecting them to a technical specialist
3. Use the 'Transfer to Technical Agent' action
Transfer calls to external phone numbers - mobile phones, landlines, or business numbers.

Use Cases

Human Specialists

Connect to live support agents

On-Call Teams

Route to mobile phones for urgent issues

External Departments

Transfer to teams outside your account

Emergency Contacts

Escalate critical situations

Configuration

1

Select transfer type

Choose PHONE as the transfer type
2

Enter phone number

Enter destination in E.164 format: +1-555-123-4567Format requirements:
  • Must include country code (+1 for US/Canada)
  • No spaces, dashes, or parentheses
  • Examples: +14155551234, +442071234567, +61398765432

Costs & Limitations

Important:
  • Phone transfers incur outbound calling costs (rates vary by destination)
  • Only work during active phone calls (not web calls or widget conversations)
  • Verify phone numbers to avoid charges or failed transfers

Example Instructions

For urgent issues outside business hours:
1. Verify the issue is truly urgent
2. Collect key details (customer name, issue summary)
3. Explain you're connecting to the on-call manager
4. Use the 'Transfer to On-Call Manager' action
Transfer calls to SIP addresses (Session Initiation Protocol URIs) for integration with PBX systems and contact centers.

Use Cases

PBX Integration

Route to internal extensions

Contact Centers

Transfer to ACD queue systems

Enterprise Telephony

Connect to corporate phone systems

VoIP Platforms

Integrate with voice infrastructure

Configuration

1

Prerequisites

Before configuring SIP transfers:
  • SIP trunk configured in itellicoAI
  • Destination SIP endpoint reachable
  • Proper authentication configured
  • Network routing in place
2

Select transfer type

Choose SIP as the transfer type
3

Enter SIP address

Enter destination SIP URI: sip:1001@yourpbx.example.comFormat requirements:
  • Must be valid SIP URI
  • Include username and domain
  • Examples: sip:support@pbx.company.com, sip:1234@10.0.1.50
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.

Example Instructions

For general support requests:
1. Collect caller information
2. Explain estimated wait time
3. Use 'Transfer to Support Queue' action

Transfer Modes

Cold Transfer (Default)

The agent transfers the call immediately and disconnects. The customer connects directly to the destination without the agent introducing them.

How It Works

Example Flow

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..."

Silent Transfer Option

You can enable Silent Transfer mode where the agent transfers without saying anything - the call is immediately routed to the destination.How it works:
  1. Agent logic triggers transfer need
  2. Transfer executes without announcement
  3. 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:
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 Transfer

Coming Soon

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:
  1. Customer placed on hold (hears hold music)
  2. AI initiates new call to destination in background
  3. Destination answers, AI provides briefing
  4. 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.

Multi-Destination Support

Create multiple transfer actions for different destinations to handle various routing scenarios:
Configure multiple transfer destinations for comprehensive routing:
Agent: Customer Service Router

Transfer 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.
Configure multiple transfer options with fallback logic:
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 callback

Instructions:
If the primary transfer fails, the agent should try the backup,
and handle complete failure gracefully by collecting callback info.
Use different transfers based on customer data or conversation context:
{% 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 %}

Best Practices

Never transfer calls without context. Explain who you’re connecting them to and why.Good:
"I understand you need help with your bill. Let me connect you
with our billing department who can access your account and
make any necessary adjustments. This should just take a moment."
Poor:
"Hold please." [immediate transfer]
Tell customers what to expect during and after the transfer.Good:
"I'm going to connect you with our technical team. You'll hear
a brief hold message, then they'll pick up within 30 seconds.
They'll have your information ready."
Poor:
"Transferring now." [customer doesn't know what's happening]
Collect basic details before transferring so the recipient has context and the customer doesn’t need to repeat themselves.
Before transferring:
1. Get customer name
2. Understand basic issue
3. Collect account/order number if relevant
4. Ask about urgency
5. Then transfer with context
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”
Always have a plan for when transfers fail (busy, no answer, etc.).
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 time
4. Confirm: "Great, expect a call from us at [number] within the hour"
5. Use 'End Call Politely' action
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)
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)
  • Limit phone transfers to necessary escalations
  • Monitor transfer frequency and costs
  • Set up alerts for unusual transfer volumes

Testing Transfer Actions

Test all transfer destinations before going live to ensure reliable operation: Essential tests:
  • Transfer executes and destination receives call
  • Audio quality is good in both directions
  • Agent explains transfer appropriately in instructions
  • Failure scenarios handled gracefully (no answer, busy signal, invalid destination)
  • Test from different call sources (phone, web)
For phone/SIP transfers, confirm proper E.164 formatting and destination reachability.

Troubleshooting

Symptoms: Transfer appears to connect, but call ends right awayPossible causes:
  • Destination not configured to accept transfers
  • SIP endpoint configuration issue
  • Agent not active (for agent transfers)
  • Network/firewall blocking
Solutions:
  • Verify destination agent is active and published
  • Test destination phone number independently
  • Check SIP trunk configuration and authentication
  • Review firewall rules for SIP traffic
  • Check for “Do Not Disturb” or call blocking on destination
Symptoms: Transfer connects but no audio in one or both directionsPossible causes:
  • RTP (media) ports blocked
  • NAT traversal issues
  • Codec mismatch
  • SIP endpoint audio settings
Solutions:
  • Verify RTP ports are open (typically 10000-20000)
  • Check NAT configuration on SIP endpoints
  • Ensure compatible codecs configured (G.711, Opus)
  • Test audio with simple test call first
  • Review SIP trunk audio settings
Symptoms: Transfer action returns error, call not connectedPossible causes:
  • Invalid phone number format
  • Insufficient account balance
  • Number not reachable
  • Carrier restrictions
Solutions:
  • Verify E.164 format: +14155551234 (not (415) 555-1234)
  • Check account balance and telephony credits
  • Test with different phone number
  • Verify destination country is supported
  • Check for carrier blocking or spam filters
Symptoms: Context/history not available to receiving agentPossible causes:
  • Configuration issue
  • Agents in different accounts
  • Transfer mode setting
Solutions:
  • Verify both agents in same itellicoAI account
  • Check transfer is configured as agent transfer, not phone
  • Review agent transfer settings
  • Test with simple agent-to-agent transfer
  • Contact support if issue persists
Symptoms: Transfer happens but no hold musicPossible causes:
  • Hold music disabled in settings
  • Duration set to 0
  • Agent transfer (music only for phone/SIP)
Solutions:
  • Enable “Play Music” checkbox in transfer settings
  • Set music duration (4-8 seconds recommended)
  • Verify transfer type supports music (not all agent transfers use music)
  • Test with phone transfer to confirm music works
Symptoms: No ringing sound during transferPossible causes:
  • Ring disabled in settings
  • Ring duration set to 0
  • Transfer completes before ring starts
Solutions:
  • Enable “Should Ring” checkbox
  • Set ring duration (4-6 seconds typical)
  • Adjust music duration if ring should play after
  • Verify destination actually supports ringing
Symptoms: SIP transfers return errors or don’t connectPossible causes:
  • Invalid SIP URI format
  • SIP trunk not configured
  • Authentication failure
  • Network routing issue
Solutions:
  • Verify SIP URI format: sip:user@domain.com
  • Check SIP trunk is configured in itellicoAI
  • Verify SIP credentials are correct
  • Test SIP endpoint with SIP client
  • Check DNS resolution for SIP domain
  • Review firewall rules for SIP traffic (port 5060/5061)
Symptoms: Transferred call displays incorrect caller IDPossible causes:
  • SIP trunk caller ID passthrough not configured
  • PBX settings blocking caller ID
  • Carrier blocking or modifying caller ID
Solutions:
  • Verify your SIP trunk is configured to pass caller ID correctly
  • Check your PBX caller ID settings
  • Some carriers block caller ID passthrough - check with your carrier
  • You may need to configure allowed caller IDs on your SIP trunk

Real-World Examples

Route support issues by complexity tier:
Agent: Customer Support Router

Transfer 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 requests

Medium 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
Qualify leads and route to appropriate sales team:
Agent: Sales Qualification Agent

Transfer 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 interest
2. Ask qualifying questions:
   - Company size
   - Budget range
   - Timeline
   - Decision authority

Based on responses:

Small business (<50 employees, <$10k budget):
- Provide self-service resources
- Offer to schedule demo via booking action
- Don't transfer unless they request

Mid-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'
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.
Agent: After-Hours Support

Transfer 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

Advanced Configurations

Use variables to dynamically determine transfer destinations:
{% 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.
Route transfers based on time of day:
{% 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.
Route based on required expertise:
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

Next Steps