Diagnosing a 3-way transfer that won't connect using the press log

An agent starts a 3-way transfer, the line rings, and then nothing — the outside party never joins the call. Before you blame the carrier or the phone, there is a report that tells you precisely how far the transfer got and where it died. It is the 3-Way Press Log Report, and reading its events turns a vague complaint into a single failing step.

How a press-1 3-way transfer works

In a Three-way call of this type, the agent dials an outside-user — often a Closer or a supervisor — and that person has to press -1- on their phone to accept before they can speak to the agent and customer. The press is the consent step: until the outside party presses, the screen will not bridge the call. This is how a Warm transfer differs from a blind Cold transfer; the outside person actively opts in. If they never press, the transfer never completes, and that is by design.

Reading the press log

The 3-Way Press Log Report lists the outside-user calls launched from the agent screen. You can filter by date range, by agent, and by the outside-user phone number. Color tells you the outcome at a glance: rows shown in black are successful transfers, and rows shown in red are unsuccessful outside-agent calls. The Results column is where the diagnosis lives. The events, in order, are:

• Started — every call gets this; it just means the outside-user call was launched.
• Answered — the outside-user call was answered.
• Accepted — the outside-user pressed -1- to accept the call.
• Reserved — the agent screen approves the call and prepares for the transfer.
• Transfer — the outside-user call is bridged to the agent and customer. This is the success line.
• Declined — the outside-user did not press -1- to accept the call.

Multi-call transfers, where several outside-users are tried at once, add three more: Too Slow means they pressed -1- but someone else pressed first; Defeated means another outside-user pressed first and this call was hung up; and Hungup means the call timed out or was hung up because someone else got there first.

Following the events to the failure point

flowchart TD
  A[Started] --> B{Answered}
  B -->|No| C[Phone or carrier never rang]
  B -->|Yes| D{Accepted}
  D -->|No declined| E[Outside party never pressed 1]
  D -->|Yes| F{Reserved}
  F -->|No| G[Screen did not approve recheck agent]
  F -->|Yes| H{Transfer}
  H -->|Yes| I[Success black row]
  H -->|No| J[Bridge failed check channels]

Read the last event a red row reached and the cause is usually obvious:

• Stuck at Started or no Answered — the outside number never picked up. Check the number, the carrier route, and whether the destination phone is even ringing.
• Answered but Declined — they picked up and never pressed -1-. Either they did not know to, or the DTMF digit is not reaching the dialer. Confirm the person knows to press 1, then check DTMF handling on that leg.
• Accepted but no Reserved or Transfer — the press landed but the screen never bridged. Look at the agent session and the Channel the call rode on.

When the press is real but never registers, the most common culprits are DTMF being swallowed by the carrier or a softphone, the same class of problem you chase when transfers and IVR menus misbehave.

Where to go next

For a column-by-column tour of the report, read how to read the 3-Way Press Log Report. For the broader checklist when calls and transfers misbehave, start at the VICIdial troubleshooting playbook.

If you would rather your transfers just worked, VICIfast runs a managed, hardened VICIdial box that is live in under 40 seconds. See our plans and pricing.