Every value of the transfer_conference API: BLIND_TRANSFER, LOCAL_CLOSER, and more

The transfer_conference function does one thing per call, and the value field decides which thing. Get the value right and the matching fields fall into place. Get it wrong and you get a validation error instead of a moved call. Here is each value, what it expects, and the situation it fits.

The hangup values

Two values clean up a 3-way instead of moving it. HANGUP_XFER drops only the third party, which is what you want when a closer call fell through and you need the customer back with the agent alone. HANGUP_BOTH ends the customer and the third party together, ending the whole conference. Neither needs a phone_number, since you are removing parties rather than dialing. Treat HANGUP_XFER as the gentle recovery and HANGUP_BOTH as the hard reset: one keeps the customer with you, the other ends everything. On a floor where agents stack calls, having both available from the same request means your toolbar can offer a tidy-up button for either situation without a second integration.

The dial-and-leave values

BLIND_TRANSFER sends the customer straight to a defined phone number and removes the agent, the textbook Cold transfer. It needs a phone_number. LEAVE_VM is a special case of the same idea: it blind-transfers the customer to the campaign-defined voicemail message, so it behaves like a Voicemail drop with no live party at the other end and no number to supply.

LOCAL_CLOSER hands the call to another VICIdial agent. It needs an Ingroup named in ingroup_choices, and you can use the reserved DEFAULTINGROUP to route back to the originating in-group or campaign. To target one specific agent instead of a queue, set ingroup_choices to AGENTDIRECT and put that agent in phone_number. This is the value most floors use to feed a qualified lead from a fronter to a Closer.

The 3-way values

flowchart TD
  A[transfer_conference value] --> B{Stay on the line}
  B -->|Yes| C[DIAL_WITH_CUSTOMER]
  B -->|Yes private brief| D[PARK_CUSTOMER_DIAL]
  B -->|No drop now| E[BLIND_TRANSFER or LOCAL_CLOSER]
  C --> F[Three way call]
  D --> F
  F --> G[LEAVE_3WAY_CALL]
  G --> H[Agent on disposition screen]

DIAL_WITH_CUSTOMER opens a Three-way call with the customer on the line, either by dialing a phone_number or by sending the call to a closer in-group. PARK_CUSTOMER_DIAL does the same but sends the customer to park first, so the agent can brief the third party privately before bringing the customer back. Both accept a consultative flag for agent-to-agent consultative transfers. When the agent is done with the introduction, LEAVE_3WAY_CALL drops the agent and leaves the customer and third party in conference, sending the agent to the disposition screen.

For a deeper look at the blind path specifically, including transferring to an AGI script, see how to blind-transfer a VICIdial call. The rest of the handoff chain sits in our transfers and closers guide.

One habit saves a lot of confusion: match the value to the fields it expects before you send the request. BLIND_TRANSFER and DIAL_WITH_CUSTOMER want a phone_number when they dial a number. LOCAL_CLOSER and the consultative variants want an ingroup_choices. HANGUP_XFER, HANGUP_BOTH, LEAVE_VM, and LEAVE_3WAY_CALL want neither. Sending the wrong combination returns a validation error rather than a moved call, so a quick check on your side keeps the agent from staring at a frozen transfer frame while you debug.

Knowing every value means you can build a CRM button for any handoff your floor needs without guessing. If you want a platform where the transfer API (application programming interface) is ready to use, check our pricing and skip the setup grind.