How to read the 3-Way Press Log Report and what each result means
Decode every row of the 3-Way Press Log Report, from Started to Transfer, and tell a clean handoff from a failed one at a glance.
When an agent dials an outside party into a live call, the system logs every step of that handoff. The 3-Way Press Log Report is where you go to see whether the transfer actually completed or quietly fell apart. It tracks the press-1 calls placed from the agent screen, where the outside party has to press 1 on their phone before they can speak.
Each line is one leg of a Three-way call. The fastest read is the color: rows in black are successful handoffs, rows in red are calls that never made it to the agent and customer. Once you know that, the Results column tells you exactly where each red row gave up.
What each Results event means
A call walks through a fixed sequence of events. A clean transfer hits every stage in order; a failed one stops partway and gets marked accordingly.
stateDiagram-v2
[*] --> Started
Started --> Answered
Answered --> Accepted
Accepted --> Reserved
Reserved --> Transfer
Answered --> Declined
Accepted --> TooSlow
Accepted --> Defeated
Started --> Hungup
Transfer --> [*]- Started — every leg gets this. It just means the outside call was launched.
- Answered — the outside party picked up the phone.
- Accepted — they pressed 1 to accept the call. This is the Press 1 gate that separates a real human from a voicemail or a hangup.
- Reserved — the agent screen approves the leg and gets ready to bridge it in.
- Transfer — the leg is bridged to the agent and customer. This is the only event that means the handoff succeeded.
- Declined — answered but never pressed 1. They heard the prompt and ignored it, or it went to a machine.
- Too Slow — multi-call only. They did press 1, but a different outside party pressed it first.
- Defeated — multi-call only. Someone else won the race, so this leg was hung up before they could accept.
- Hungup — the leg timed out, or another party beat it, so it was dropped.
Single 3-way vs multi-call
A single 3-way dials one outside number. You expect one row, walking Started to Answered to Accepted to Reserved to Transfer. If it stops at Declined, the person on the other end never pressed 1.
A multi-3-way dials several numbers at once and gives the call to whoever presses 1 first. Here you'll see one Transfer row in black and one or more Too Slow, Defeated, or Hungup rows in red for the legs that lost the race. Those red rows are expected, not errors — the same way a Closer picking up a Warm transfer leaves the other ringing closers as dropped legs.
How to investigate a row
- Filter by date and the agent user or outside number you're chasing.
- Find the last event for that leg. If it never reached Accepted, the outside party never pressed 1.
- If it reached Accepted but stalled before Transfer, the bridge failed — look at audio and the Cold transfer path next.
- If lots of Declined rows pile up on one route, suspect a DTMF or audio issue on that carrier, not the agents.
This report tells you where the handoff stopped, but not always why. Pair it with the full picture in the troubleshooting playbook, and if you're tracing dropped audio on the bridged leg, walk it with the Hangup Cause Report. VICIfast runs the box for you, so you spend your time reading the report instead of patching the dialer that wrote it — see plans and pricing.
About VICIfast LLC
VICIfast LLC operates a managed VICIdial hosting + BYOI service for outbound and inbound call centers. We run the dialers, the carriers, the recordings pipeline, and the compliance plumbing so operators don’t have to.
Citing this article
VICIfast Engineering. “How to read the 3-Way Press Log Report and what each result means”. VICIfast LLC, June 25, 2026. Retrieved from https://vicifast.com/blog/how-to-read-the-3way-press-log-report
Have questions?
Related posts
Operations
Diagnosing high agent latency: the reports that point to the cause
Operations
Why agents get logged out with a LAGGED message and how to fix it
Operations
How to read the Webserver-URL Report on a multi-server setup
Operations
How to read the User Group Login Report to confirm where an agent logged in
You might be interested in
VICIfast newsletter
Liked this? Get the next one in your inbox.
We ship the kind of stuff you just read — concrete, numbers-first, no drip. One email when a new post goes live. Unsubscribe in one click.
Comments
No comments yet — be the first.