Customer 3-Way Hangup Logging: detecting when the customer drops off a 3-way

On a 3-way call, the riskiest moment is the one nobody notices: the customer quietly hangs up while the fronter and closer keep talking. Customer 3-Way Hangup Logging is the setting that makes that drop visible, so the system can record it and act on it instead of leaving two agents talking to dead air.

What it logs

When this option is ENABLED, the user_call_log records the moment a customer hangs up if they drop during a Three-way call. That entry gives you a real, queryable record of customer drop-offs rather than a guess. The default is ENABLED.

Just as important, enabling the logging is what allows the optional Customer 3-way hangup action to fire. Without the logging on, that downstream action has nothing to react to, so this setting is the foundation the rest of the behavior sits on.

Why it matters in a fronter-closer flow

In a Fronter and Closer model, the Fronter does a Warm transfer, introduces the customer, and steps back. If the customer hangs up during that handoff, the Closer should know immediately. Logging the hangup means your reports can count these drops and your floor can stop wasting minutes on a Three-way call with only two parties left.

It also gives you a clean signal for coaching. If one Agent sees a spike in mid-transfer customer drops, that is a script or timing problem you can actually see in the data instead of inferring from a vague Hangup cause.

Why leave it on by default

Because the default is ENABLED, most floors get this for free, and there is rarely a good reason to switch it off. The logging is lightweight, it does not change what the agent sees unless you also define an action, and it gives your reports a true count of customer drop-offs during a transfer. The only time you might turn it off is if you have a custom flow that handles the customer leg some other way and you want to avoid duplicate records.

Keep in mind that logging is about the customer leg specifically, not the Closer or the Fronter hanging up. It answers one focused question: did the customer drop while three parties were on the call? That narrow focus is what makes the resulting data trustworthy for measuring handoff quality.

The detection flow

flowchart TD
  A[Customer on 3-way call] --> B[Customer hangs up]
  B --> C{Hangup Logging enabled}
  C -->|ENABLED| D[Write entry to user_call_log]
  C -->|DISABLED| E[Drop goes unrecorded]
  D --> F{Hangup action defined}
  F -->|Yes| G[Run optional hangup action]
  F -->|None| H[Log only agents notified]
  G --> I[Agent moves on]

How it connects to the related settings

Logging is step one. Two companion settings build on it: a delay control that defines how many seconds after the hangup is detected before it is actually logged and any action runs, and the action itself that can, for example, send the agent to the disposition screen. Both depend on this logging being ENABLED first.

If you want the agent screen to react automatically once a drop is detected, read our note on the Customer 3-Way Hangup Action, which is the piece that closes out the dead call cleanly.

For the broader transfer picture and how every closer setting fits, see our transfers and closers guide. If you want a dialer that logs these drops and reacts to them without manual tuning, take a look at our pricing.