What Is a Call Disposition?

A disposition is the smallest piece of data in an outbound operation and one of the most consequential. Everything downstream reads it. The dialer decides whether to retry the record. The suppression logic decides whether the number may be called again at all. The campaign report decides what the day produced. The client report decides what the month was worth. If the code is wrong, every one of those is wrong in the same direction, and nothing in the system will tell you.

Dispositions separate cleanly into two groups. System outcomes describe what the network did, such as busy, no answer, invalid number or machine detected, and these can be recorded without a person involved. Agent outcomes describe what the conversation produced, such as a payment promise, a scheduled callback, a refusal or a request to be removed, and these require the judgment of the person who was on the call.

Designing Codes People Will Use Correctly

• Make them mutually exclusive. If two codes could both describe the same call, agents will split unpredictably between them and the report will be noise.
• Group them into categories. A category on each code gives you a rolled-up view without asking the agent to code twice.
• Put the common ones first. Four or five codes cover most calls on most campaigns. Those should be reachable without searching.
• Give them hotkeys. Wrap-up is where agent time leaks. A keystroke is quicker and more accurate than hunting through a dropdown.
• Watch for the Other pile. A growing catch-all is the clearest sign the taxonomy no longer fits the work.

What Depends on the Code

Retry behaviour is the obvious dependency: no answer earns another attempt, wrong number should not. Suppression is the serious one, because a removal request captured as a disposition has to stop every future attempt against that record, and a miscoded call quietly leaves the number in play. Beyond compliance, dispositions are the denominator for right party contact rate, the input to agent performance comparisons, and the evidence a client is shown when they ask what the campaign actually did.

How DialerBee Handles Dispositions

In DialerBee's lead management, disposition codes are yours to design. Each code carries a category, an icon, a colour, a hotkey and a favourite flag, so agents hit a key and you get a clean taxonomy out the other end. Auto-disposition rules set the code automatically where the outcome is not in doubt, and usage statistics show which codes are actually being used, which is how you find a taxonomy that has drifted away from the work.

On the agent desktop, outcomes appear as disposition cards with keyboard hotkeys, favourites pinned to the front, a search box and a recent list, so wrap-up is a keystroke rather than a hunt through a dropdown. Callbacks are scheduled directly from the disposition, at the time the customer asked for, without leaving the call the agent is finishing, and the disposition popup can add the customer to the CRM at the moment the agent is already deciding what happened. Every contact moves through a defined state machine with outcome columns, so a lead's position is a state you can query rather than a guess from its call history. Supervisors can export the dispositions behind the numbers, so a client or a QA lead can check the outcomes rather than take the dashboard's word for it, and the language mix across all 11 languages is visible alongside the dispositions recorded so far today.

Frequently Asked Questions

What is the difference between a disposition and a call outcome?

They are usually the same thing, but the words are used at different levels. A disposition is the specific code the agent selects, such as promise to pay or wrong number. An outcome is the broader category that code rolls up into, such as contacted or not contacted. Designing codes with a category attached is what lets you report at both levels from one selection.

How many disposition codes should a campaign have?

Few enough that an agent can find the right one without thinking, which in practice means most campaigns settle somewhere under twenty visible codes with the handful used all day pinned to the front. Long lists produce lazy selection, and a taxonomy nobody uses accurately is worse than a short one everybody does.

Can dispositions be set automatically?

For outcomes that are not in doubt, yes. A call that never connected, a number that returned an invalid response, or a machine answer can be coded by rule without an agent deciding anything. Judgement outcomes should stay with the person who had the conversation, because an inferred promise to pay is not evidence of one.

Why do dispositions matter for compliance?

Because they are the record of what the contact produced, and several rules depend on that record. A do-not-call request captured as a disposition has to suppress the number. A wrong-number result should stop further attempts against that record. Without clean coding, the suppression logic is acting on an inaccurate picture of what happened.

What makes a disposition taxonomy go bad?

Codes that overlap, codes that describe the agent's feeling rather than the contact's result, and a catch-all Other that absorbs everything ambiguous. The test is whether two agents handed the same call would pick the same code. If they would not, the code needs splitting or the definitions need writing down.

Related terms: after-call work, callback scheduling, right party contact, consent management and do not call list.