force_fronter_leave_3way: making the fronter drop off a 3-way automatically

In a fronter-closer setup, the fronter brings the customer onto a 3-way call, introduces the closer, and is supposed to drop off. Sometimes they forget, or they freeze, or their connection drops the click. The force_fronter_leave_3way function exists for exactly that: it tells the fronter's session to leave the conference for them, so the closer and customer keep talking cleanly.

What the function actually does

This is an Agent API call. You hit it with the named agent_user being the closer who wants the fronter gone. The function deliberately will not run the leave command for that named agent. Instead it looks for the oldest other user who is currently on a call with the same Lead id that the named agent is talking to, and sends the leave command to them. That other user is the Fronter. The result is the same as if the fronter had clicked LEAVE 3-WAY CALL themselves: they exit, the customer stays, and the closer owns the conversation.

The value choices and where to look

The value parameter controls where the system searches for the fronter. LOCAL_ONLY looks for the fronter only on the local cluster. LOCAL_AND_CCC checks the local cluster first and then a remote CCC, which matters when your floors are split across servers. CCC_REMOTE is for when the closer is not on this cluster at all; with that value you can also pass an optional lead_id to point the search at the right call. If everyone sits on one server, LOCAL_ONLY is all you need.

flowchart TD
  A[Closer calls force_fronter_leave_3way] --> B{Which value}
  B -->|LOCAL_ONLY| C[Search local cluster]
  B -->|LOCAL_AND_CCC| D[Search local then remote CCC]
  B -->|CCC_REMOTE| E[Search remote cluster]
  C --> F[Find oldest other user on same lead]
  D --> F
  E --> F
  F --> G[Send leave command to fronter]
  G --> H[Fronter drops customer stays]

When this is worth wiring up

On a busy floor, a fronter who lingers on the 3-way ties up a seat and can hear the rest of the sale. Forcing the drop keeps Wrap-up time honest and stops a stuck conference from holding a fronter hostage. Pair it with a clean handoff routine and the fronter is free for the next call within a second of the closer taking over. If you want the broader picture of how fronters and closers pass calls back and forth, the transfers and closers guide lays out the full chain.

There is a companion function, force_fronter_audio_stop, that silences any audio still playing in the fronter's session after they leave. The two are often used together. For the button click that this function automates, read up on the leave 3-way call button so you know exactly what state the fronter session lands in.

A quick reality check before you build it in: the named agent must be logged in and actually on a phone call, and there must be a second user on the same lead, or the search comes back empty. If you get a no fronter found response, that is the system telling you it could not match a second session to the call. Plan for that case in your script so a failed force does not leave the closer wondering what happened.

Most teams reach for this once they outgrow trusting fronters to self-clean. If you are building a fronter-closer floor and want the dialer side handled for you, look at our pricing to see what a managed VICIdial setup runs.