Why transferring to another agent with Transfer No Dispo causes data problems

Transfer No Dispo is a campaign option that lets an agent transfer a call without the disposition screen popping up afterward. Normally, when an agent hands a customer off, the agent screen jumps to the dispo screen so they can record the outcome of the call. Transfer No Dispo suppresses that jump and leaves the agent in the talk screen instead. It sounds convenient, and for some transfers it is. For one specific transfer type it quietly breaks your numbers.

What the option actually covers

When enabled, Transfer No Dispo applies to a handoff to an external number, to a Local Closer, or to Leave 3-Way. The default is disabled. For an external number or a Leave 3-Way, skipping the dispo screen is usually harmless, because the agent is leaving the call entirely and the lead record can be closed cleanly. The trouble starts when the transfer target is another Agent on your own system.

Where the inconsistency comes from

When you transfer to another agent, two agent sessions touch the same Lead in a short window. The sending agent is supposed to record a Disposition for their half of the call, and the receiving agent records the final outcome for theirs. The dispo screen is what forces the sending agent's half to be written cleanly before the lead moves on. Skip it, and the sending agent can be left without a recorded status while the receiving agent is already working and dispositioning the same lead. The two halves of the call can disagree about what happened, which is exactly the kind of mismatch that makes your Fronter and closer reports stop adding up.

flowchart TD
  A[Agent transfers live call] --> B{Transfer target}
  B -->|External number| C[Skip dispo is safe]
  B -->|Leave 3 way| C
  B -->|Another agent| D[Sending agent leaves no status]
  D --> E[Receiving agent dispositions lead]
  E --> F[Two halves disagree]
  F --> G[Report totals do not match]

How to keep your data clean

The simple rule: do not enable Transfer No Dispo on a campaign whose agents transfer to other agents. If your flow is fronter to closer through a Local Closer handoff, leave the dispo screen on so each fronter records their half. If you genuinely only ever transfer to external numbers or a VM message, then Transfer No Dispo can save a couple of clicks per call with no downside. The safe move is to scope it to the campaigns where it truly applies rather than turning it on globally, because one shared setting flipped on the wrong campaign is enough to make a whole day of reports untrustworthy.

If you are not sure which transfer style your campaign uses, the difference matters here. Sending a customer to a coworker through an Ingroup is an agent-to-agent transfer for the purposes of this warning, even if it feels like just another button. The how-to for that path is covered in transferring a call to another agent, and the wider handoff model is in the transfers and closers guide.

Clean reporting is mostly a matter of letting each agent record their own outcome, and Transfer No Dispo only earns its keep where there is exactly one agent on the lead. If you have already seen mismatched totals after turning it on, the fix is usually as simple as switching it back to disabled on the agent-to-agent campaigns and letting the dispo screen do its job again. If you would rather start from a configuration where these traps are already set sensibly, take a look at our pricing.