Why two agents end up in the same session talking to each other

Every so often two of your agents pick up and find themselves talking to each other instead of a customer. It feels like a bug in the dialer, but it almost always traces back to one thing: an earlier agent never closed their session cleanly. The phone stayed connected, the slot stayed alive, and the next agent who logged in landed on top of it.

What a session actually is

When an agent logs in, VICIdial builds an Agent session tied to their phone login and a unique Session ID. That session holds the conference the agent listens on. The phone stays bridged into that conference for the whole shift. As long as the session and the phone bridge are both torn down together at the end, nothing overlaps. The trouble starts when the agent leaves but the bridge does not.

How the overlap happens

If an agent closes their browser tab, kills the phone window, or walks away without clicking LOGOUT, the server can be left holding a half-open session. The phone may still be registered and the conference may still be live. When the next agent reuses that phone login, or the dialer recycles the slot, the new agent's audio gets bridged into a conference that the old call path is still sitting in. Both ends are now live agents, so they hear each other.

The reason a clean LOGOUT matters so much is that it does two things at once. It ends the session record on the server, and it hangs up the phone that was bridged into the conference. Close the tab instead and only the browser side goes away. The server has no reliable way to know whether the agent stepped out for thirty seconds or left for the day, so it keeps the phone slot warm. That warm, unattended slot is exactly what the next person inherits.

The path to the collision

flowchart TD
  A[Agent finishes shift] --> B{Clicked LOGOUT?}
  B -->|Yes| C[Session ends and phone hangs up]
  B -->|No| D[Browser closed but phone stays bridged]
  D --> E[Session left half open]
  E --> F[Next agent reuses the phone login]
  F --> G[Both agents land in the same conference]
  G --> H[They hear each other not a customer]
  C --> I[Clean slot ready for next login]

What to check and fix

• Train agents to use the LOGOUT link, never the browser X. This is the single biggest prevention.
• Confirm two agents are not sharing one phone login. Each Agent should have a distinct phone login so the Status (lead status) of one session can never collide with another.
• When it happens live, have both agents click LOGOUT and log back in. That tears the stale session down.
• Check the real-time agent screen for a phone that shows as logged in with no human behind it. That is your leftover session.

It also helps to understand when the collision is most likely. Shift changes are the classic moment. One team leaves, a new team logs in on the same phones, and any session that was not closed cleanly is now a live trap. Lunch rotations and break swaps are the same risk in miniature. If you see the two-agents problem clustering at predictable times of day, you are almost certainly looking at handoffs where the outgoing agent skipped the LOGOUT link.

If the same slot keeps producing ghosts, the underlying phone may be dropping its registration and reconnecting, which leaves the old bridge behind. That overlaps with the frozen and lagged-out symptoms covered in why agents get logged out as lagged. For the full first-response checklist, start with the VICIdial troubleshooting playbook.

Keep sessions clean

Stale sessions are a habit problem more than a software problem, but a healthy box that holds phone registrations steadily makes them far rarer. VICIfast runs a hardened, managed VICIdial server that is live in under 40 seconds, with monitoring that flags phones logged in with nobody behind them. See our plans and pricing.