Transfer No Dispo: skipping the disposition screen after a transfer (and why it's risky)

By default, when a VICIdial agent transfers a call, the disposition screen pops up so they can mark how the call went before moving on. Transfer No Dispo turns that prompt off for certain handoffs. It is a small convenience with a sharp edge, so it is worth knowing exactly when it helps and when it bites.

What it skips

A Disposition is the outcome code an agent picks at the end of a call, the SALE, NI, or callback tag that drives your reports. With Transfer No Dispo enabled, an agent can transfer a call to an external number, a Local Closer, or use Leave 3-Way without the disposition screen appearing. The default is DISABLED, meaning the prompt shows up like normal.

The appeal is obvious. On a high-volume floor, every click counts, and a Fronter who hands off thirty calls an hour does not always need to stop and tag each one. Skipping the screen keeps them moving to the next Lead.

Why it is risky

Here is the warning that matters: do not enable this if calls are transferred to other agents. Doing so can cause data inconsistencies. When two agents are both attached to a Lead and neither one closes out the record cleanly, your reporting and your lead state can drift out of sync.

So the safe use is narrow. It is fine for transfers to an external number or to a Local Closer where the Agent who started the call is genuinely done. It is dangerous when the handoff is agent-to-agent, because both sessions can fight over the same record.

What a data inconsistency looks like

When the screen is skipped, the originating call record never gets its closing outcome written. If that same lead lands in front of a second agent moments later, you can end up with two open sessions, a missing Disposition on one leg, and call time logged against the wrong person. None of that throws an error in the moment, which is exactly why it is dangerous: the damage shows up later in your reports, not on the agent's screen.

On a clean external transfer the risk is gone, because the originating agent's session ends normally and the call simply leaves the dialer. The trouble only appears when another VICIdial agent inherits a record that was never closed out.

Decision flow

flowchart TD
  A[Agent clicks transfer] --> B{Transfer No Dispo enabled}
  B -->|No| C[Dispo screen pops up]
  B -->|Yes| D{Transfer target}
  D -->|External or Local Closer| E[No dispo screen agent moves on]
  D -->|Another agent| F[Risk of data inconsistency]
  C --> G[Agent tags outcome]
  E --> H[Next call]

A safer setup

If you run a Fronter and Closer model where the fronter does a Warm transfer to a closer pool, weigh the click you save against the cleanup you might create. In most shops it is better to leave the disposition prompt on and train agents to tag fast. Reports built on missing dispositions are hard to trust later.

If you do enable it, restrict it to campaigns that only transfer outward to numbers or a Local Closer, never to other agents in the same dialer. Pair that with a clear understanding of how a 3-way call with the customer behaves so you know which path each transfer button takes.

Our transfers and closers guide walks through every related setting so you can choose the combination that keeps your data clean. Want a dialer where these guardrails come pre-tuned for your campaigns? See our pricing.