Skip to main content

Warm Transfers

A warm transfer connects a caller to a human agent while providing context about the conversation. Unlike cold transfers, the receiving agent knows who’s calling and why before the connection is made.

How Warm Transfers Work

Configuring Warm Transfers

Basic Configuration

Brief Templates

Customize what the AI tells the receiving agent:

Available Variables

Hold Experience

Configure what callers hear while waiting:

Hold Options

Transfer Flow Options

Accept/Decline

The receiving agent can accept or decline:

Auto-Connect

Connect immediately without confirmation:

Voicemail Fallback

If the transfer is declined or times out:

Multi-Destination Transfers

Sequential Dialing

Try destinations in order:

Simultaneous Ring

Ring multiple destinations at once:

Skill-Based Routing

Route based on agent skills:

Skill Groups

Define skill groups for routing:

Screen Pop Integration

Send caller information to the receiving agent’s screen:

Transfer Events

Monitor transfer status via webhooks:

Event Payload

Best Practices

Receiving agents are busy. Aim for 10-15 seconds of context, not a full recap.
30 seconds is typical. Too short and agents can’t answer; too long and callers abandon.
If no one answers, route to voicemail or offer a callback.
If auto-connecting, a whisper gives agents heads-up without delay.
High decline rates indicate staffing or routing issues.

Troubleshooting

Transfers failing

  1. Verify destination number is correct
  2. Check if receiving agents are available
  3. Ensure timeout isn’t too short
  4. Verify telephony connection is working

Callers abandoning during hold

  1. Reduce timeout duration
  2. Improve hold music/messaging
  3. Add position-in-queue announcements
  4. Consider callback option

Context not appearing

  1. Verify brief template syntax
  2. Check if variables are being collected
  3. Test screen pop URL separately
  4. Review webhook deliverability

Next Steps