Multi-dial 3-way press-1: ringing several outside numbers and connecting the first to answer

Sometimes you do not care which specialist takes the call, you just want the fastest one. Multi-dial 3-way Press 1 rings a list of outside numbers at the same time and connects your agent and customer to whoever presses 1 first. Everybody else gets dropped. It is the press-1 idea scaled out to a pool of outside parties.

The multi_dial_phones field

This runs through the transfer_conference function on the agent API and is meant only for Agent 3-way Press-1 Calls. You pass multi_dial_phones with up to 10 phone numbers separated by commas, like 2125551212,4075551212,3125551212. Duplicates in that list are removed automatically, so you do not waste a slot ringing the same desk twice.

Each number gets its own outside-user leg, and each leg waits for a press 1. The first acceptance wins the bridge into the Three-way call with the agent and customer. A three-way call here is the shared conversation between your agent, the customer, and the one outside party who accepted.

The ten-number ceiling is a real limit, not a suggestion, so order the list with your strongest desks first if you want them to have the best shot. Because duplicates are stripped before dialing, padding the list with the same number twice does not improve its odds. Keep the list to numbers you genuinely want ringing at once, since every leg you launch is a phone you have to answer or hang up.

Multi-dial runs on the same press-1 plumbing as the single-number flow, including the dial override that dials each number exactly as given without a campaign-defined phone code or prefix in the way. That is why your list should be full, dialable numbers rather than short internal extensions.

Guarding against overlap with md_check

Multi-dial has a matching safety option: md_check. Set it to YES and the API checks for still-active previous 3-way press-1 calls and shows an error if any are found. That stops an agent from kicking off a second wave of calls while the first batch is still ringing, which would otherwise leave orphaned legs and confused outside parties.

There is a sibling option, tw_check, for the regular dialing 3-way options. It checks for still-active previous 3-way calls and errors if found. Use md_check for the multi-dial flow and tw_check for the single-dial flows so a stuck call never collides with a fresh one.

How the race resolves

flowchart TD
  A[Agent submits multi_dial_phones] --> B[md_check for active 3-way press-1]
  B -->|Active found| C[Error and stop]
  B -->|Clear| D[Ring all outside numbers]
  D --> E[Number one]
  D --> F[Number two]
  D --> G[Number three]
  E --> H{First to press 1}
  F --> H
  G --> H
  H --> I[Bridge winner to agent and customer]
  H --> J[Hang up the rest]

When multi-dial earns its keep

Reach for this when a Lead needs any qualified closer fast and you have a bench of outside specialists. Instead of a fronter trying one number, hearing it ring out, and dialing the next, every number rings together and the customer waits less. It pairs well with a Warm transfer mindset because the customer only ever meets the person who actively accepted.

The single-number version and the AGI plumbing behind both are in 3-way press-1 calls explained. For how this fits the wider handoff toolkit, see the transfers and closers guide.

If wiring the API and special extensions yourself sounds like a weekend gone, our pricing covers a managed VICIdial with multi-dial press-1 ready out of the box.