How Call Transfers Work in VICIdial

Understanding Call Transfers in VICIdial

Call transfers are a daily operation in any contact center. Whether an agent needs to escalate a billing question to a supervisor, connect a warm lead to a closer, or route a support call to a specialist, VICIdial provides multiple transfer methods to handle these workflows. Understanding how each transfer type works—and when to use it—keeps customer experiences smooth and prevents the dropped-call chaos that frustrates both agents and callers.

VICIdial supports blind transfers, warm transfers (also called attended transfers), and conference-style transfers that keep all parties on the line. Each method has distinct behavior, configuration requirements, and appropriate use cases. This guide covers all three, along with the campaign and system settings that control transfer availability.

Transfer Types Explained

Blind Transfer

A blind transfer immediately redirects the caller to a new destination without the transferring agent staying on the line. The agent initiates the transfer, selects or dials the target, and VICIdial connects the caller directly. The original agent is released and returns to available status. Blind transfers are fast and work well when the agent knows exactly where the call needs to go—such as transferring to a specific extension or an inbound queue.

The risk with blind transfers is that if the destination does not answer or is unavailable, the caller may hear ringing indefinitely or get dumped to voicemail without context. Use blind transfers only when you are confident the target will answer.

Warm Transfer (Attended Transfer)

A warm transfer lets the agent speak with the transfer target before connecting the caller. The agent places the caller on hold, dials the target (another agent, supervisor, or external number), briefs them on the situation, and then bridges all parties together or drops off once the handoff is complete. Warm transfers are the standard for sales escalations, complex support issues, and any situation where context must pass between agents.

In VICIdial, warm transfers typically use the three-way calling feature. The agent conferences the caller and the transfer target, introduces the parties, and then hangs up to leave the caller with the new agent. The vicidial dialer handles the SIP bridging automatically once the agent initiates the conference.

Conference Transfer

Conference transfers keep all parties—caller, original agent, and transfer target—on the same call simultaneously. This is useful for joint sales calls, compliance-monitored transfers, or situations where the original agent needs to remain briefly during the handoff. The agent controls when to drop off the conference, leaving the caller and target connected.

Enabling Transfers in Campaign Settings

Transfer capabilities are controlled at the campaign level. Not every campaign needs transfers enabled—inbound survey campaigns, for example, may disable them to keep agents on script. For sales and support campaigns, transfers are essential.

1. Navigate to Admin → Campaigns → Campaign Detail for your target campaign
2. Set Allow Closers to Y if agents should transfer to closer groups
3. Configure Transfer Groups — define which inbound groups or extensions agents can transfer to
4. Set Agent Transfer Options — enable blind, warm, and external transfer permissions
5. Configure the Transfer-Conf DTMF settings for three-way calling activation
6. Set External Transfer Protocol if agents need to transfer to outside phone numbers
7. Save campaign settings and have agents log out and back in to pick up changes

If you are setting up a new campaign, complete your outbound campaign configuration and SIP carrier setup before enabling transfers. Transfers to external numbers route through your SIP carrier, so carrier capacity and number formatting rules apply.

Agent Transfer Workflows

Transferring to Another Agent

During a live call, the agent clicks the Transfer button in the agent interface (or dials the transfer DTMF code). VICIdial presents a list of available transfer destinations based on the campaign's transfer group configuration. The agent selects the target agent or group, chooses blind or warm transfer, and VICIdial handles the SIP routing.

For warm transfers to another agent, the transferring agent should use the park-and-dial method: park the caller, dial the target agent's extension, brief them on the call, then conference the caller back in. Supervisors monitoring the floor can assist with transfers using monitor, whisper, and barge features to observe the handoff.

Transferring to an External Number

External transfers route calls to phone numbers outside the VICIdial system—partner companies, cell phones, or specialized support lines. The agent dials the external number after parking the caller, confirms the destination answers, and bridges the call. External transfers consume an additional SIP channel on your carrier, so verify your channel limits can accommodate transfer volume.

Format external numbers correctly for your SIP carrier—typically 10 or 11 digits for US numbers. Misformatted external transfer numbers fail silently or produce fast busy tones. Test external transfers to common destinations during your initial vicidial setup phase.

Transferring to Inbound Groups

Inbound group transfers route callers to a queue of available agents in a different campaign—common in closers workflows where a front-line agent qualifies a lead and transfers to a senior closer group. Configure inbound groups in Admin → Inbound and add them to the campaign's transfer group list.

When transferring to an inbound group, the caller enters the group's queue and hears hold music until an agent in that group answers. Set realistic queue timeout values to prevent callers from waiting indefinitely. Monitor queue depth in the real-time reports during high transfer volume periods.

Closer Campaigns and Transfer Groups

Closer campaigns are a specialized VICIdial workflow where front-line agents transfer qualified leads to a dedicated closing team. The closer campaign operates as a separate campaign with its own agents, scripts, and dispositions, but receives calls via transfers from one or more feeder campaigns.

• Enable Allow Closers on the feeder campaign
• Create a closer campaign with its own agent group and script
• Configure the Transfer-Conf Group to point to the closer campaign's inbound group
• Set closer agents to the closer campaign and feeder agents to the feeder campaign
• Train feeder agents on qualification criteria before enabling transfers
• Monitor transfer rates and closer connect rates in real-time reports

Closer workflows are common in vicidial outbound calling operations for insurance, solar, and financial services. The key metric is transfer-to-close rate—if closers are not converting transferred calls, revisit qualification criteria with the feeder team.

Transfer Recording and Compliance

Call recording behavior during transfers depends on your recording configuration. In most setups, recording continues through the transfer as long as the call remains within the VICIdial system. External transfers may stop recording when the call leaves your vicidial server, depending on carrier and recording settings.

For compliance-sensitive industries, verify recording continuity through each transfer type during testing. If your operation requires all-party consent, ensure your script includes disclosure before any transfer occurs. Teams integrating with CRMs should confirm transfer events and disposition changes sync correctly—see our Salesforce integration guide for webhook and API options.

Troubleshooting Transfer Issues

Transfer Button Not Visible to Agents

Check that transfer options are enabled in the campaign settings. Agents must log out and back in after campaign changes. Verify the agent's user level has transfer permissions—some user levels restrict transfer capabilities. Confirm the campaign is not set to a dial method that disables transfers during auto-dialed calls.

Blind Transfer Goes to Dead Air

The transfer target is likely unavailable or the extension is misconfigured. Verify the target agent is logged in and in READY status. For inbound group transfers, confirm agents are available in the target group. Check Asterisk logs for SIP errors during the transfer attempt.

Caller Disconnected During Warm Transfer

The caller may have hung up during hold, or the hold timeout expired. Increase the park/hold timeout in campaign settings. Train agents to complete warm transfers quickly—extended hold times cause caller abandonment. If disconnects happen at the moment of conference, check for RTP issues covered in our one-way audio guide.

External Transfer Fails

Verify the external number format matches your carrier requirements. Confirm your SIP carrier allows outbound calls to the destination number type (some carriers block international or premium numbers). Check that you have available SIP channels—an external transfer uses two channels simultaneously (caller + outbound leg to the external number).

Best Practices for Call Transfers

Transfers should feel seamless to the caller. Train agents to explain the transfer before initiating it—"I'm going to connect you with our specialist who can help with that"—rather than silently transferring. For warm transfers, agents should provide the receiving agent with key context: caller name, reason for the call, and any relevant account details.

Track transfer metrics in your real-time reports: transfer rate, transfer hold time, and post-transfer disposition. High transfer rates may indicate a script or training gap on the feeder team. Long transfer hold times suggest closer groups are understaffed.

Review transfer workflows monthly. As your team grows and campaigns evolve, transfer group configurations need updating. New inbound groups, agent promotions to closer roles, and carrier changes all affect transfer routing.

Conclusion

Call transfers in VICIdial are powerful but depend on correct campaign configuration, proper SIP carrier capacity, and well-trained agents. Start by enabling the transfer types your workflow actually needs, test each method with internal calls, and build agent training around warm transfer etiquette. Blind transfers for known destinations, warm transfers for escalations, and conference transfers for joint conversations cover the vast majority of contact center scenarios.

If transfers fail consistently despite correct configuration, the issue often traces back to SIP trunk problems or server resource limits. Engage your vicidial support provider with specific examples—campaign ID, transfer type, source and destination, and timestamps—for the fastest resolution.