Call disposition
Definition
Call disposition: codes, wrap-up, and list logic
Call disposition is the code an agent selects at the end of a call to record what happened. That single tag, whether sale, callback, wrong number, or do not call, tells your dialer and CRM what to do with that contact next.
Every outbound and inbound campaign runs on these codes. The dialer reads the disposition, then decides whether to retry the number tonight, park it in a nurture sequence, or suppress it for good.
Get the code set wrong and everything downstream breaks. Retry logic misfires, weekly reporting lies to you, and compliance loses the audit trail it needs for do-not-call requests.
Key takeaways
- A call disposition is the outcome code an agent applies in the final seconds of a call.
- Codes drive automation: retry timing, nurture routing, suppression, and do-not-call flags.
- Keep the set short. Twelve to twenty clear codes beat sixty that agents guess at.
- Wrap-up time sits inside handle time, so code selection speed moves your cost per contact.
- Weekly quality sampling catches miscoded calls before they poison your reporting.
How it works
A call disposition works as a three-step handoff. The agent ends the conversation, picks one code from a fixed list, and the platform writes that outcome to the contact record, where list logic acts on it automatically.
Design the code set first. Every code needs one unambiguous meaning, one owner, and one automation attached to it. If two codes could describe the same call, agents pick whichever is faster and your data drifts.
Wrap-up time — the seconds after hangup when the agent codes the call — sits inside handle time on most platforms. Trim the list and you trim the clock.
Ownership matters as much as design. Someone in operations should hold the code set, approve every addition, and push changes into your customer relationship management (CRM) platform so both systems stay in step.
Here is the pattern most dialer configurations follow.
| Disposition code | What it means | What the dialer does next |
|---|---|---|
| Sale booked | Contact agreed and the order is confirmed | Drops the record from the dial list, starts fulfilment |
| Callback scheduled | Contact named a specific time to talk | Reserves the slot, routes it back to the same agent |
| No answer | Line rang out with no contact made | Retries later the same day under attempt-cap rules |
| Busy | Line engaged | Retries after a short cooldown |
| Not interested | Contact declined the offer | Moves the record to a long-cycle nurture list |
| Wrong number | Number does not belong to the contact | Flags the record for data cleansing |
| Do not call | Contact asked to be removed | Writes to the suppression list permanently |
Codes marked as final outcomes close the record. Codes marked as retryable push back into the queue with an attempt cap, a cooldown window, and a time-of-day rule.
Then comes quality assurance. Supervisors pull a weekly sample of recorded calls and compare what actually happened against the code the agent chose.
Miscoding is rarely deliberate. It is usually a code list that grew too long, stayed too vague, or got trained once and never revisited.
Automation is where the payoff lands. A single code can suppress a record, fire a follow-up email, and move a pipeline stage at once — so one careless click carries real weight.
Examples
Disposition sets look different in every vertical, but the pattern holds: the code names the outcome, and the platform reacts. Here are four setups you would recognise on any floor, in-house or run by a call center partner.
Outbound software sales. A Manila team dialling mid-market prospects runs eight codes. Sales representatives tag demo-booked, callback, gatekeeper, or not-interested, and each one triggers a different follow-up sequence.
Accounts receivable collections. Codes split by promise: paid in full, payment plan agreed, refused, disputed, or third-party contact. Regulators expect the refused and disputed records to stop receiving calls immediately.
Inbound customer support. A contact center resolving billing queries codes for first-contact resolution, escalation, or transfer. Those tags feed straight into average handle time (AHT) dashboards.
Appointment reminders. Clinics and dental groups code confirmed, rescheduled, cancelled, or voicemail-left. Voicemail records requeue once; confirmed records leave the list until the next cycle.
Across all four, the same discipline applies. The United States Do Not Call Registry, run by the Federal Trade Commission since 2003, only works if your do-not-call code writes to suppression the moment the agent clicks it.
Voice is not the only channel using them either. Chat and email queues in the same platform carry their own disposition lists, and blended teams keep the wording aligned so one report covers every channel.
Clean coding also pays back internally.
One vendor guide notes that disposition data provides valuable information and detailed insights.
Supervisors use it for coaching, forecasting, and list health.
Related terms
Call disposition sits inside a small family of contact-centre terms. Knowing the neighbours makes code-set design easier, because each one either feeds the disposition or consumes the data it produces once the call ends.
- Agents: the frontline staff who select the disposition code and own its accuracy.
- Call Center: a voice-only operation where dispositions mainly govern dial-list behaviour.
- Contact Center: a multichannel operation where dispositions cover chat and email outcomes too.
- Average Handle Time (AHT): the per-contact clock that includes the wrap-up seconds spent coding.
- Customer Relationship Management (CRM): the system of record that stores each disposition against the contact.
FAQ
What is a call disposition in a call center?
It is the outcome code an agent applies once a call ends. The code tells the dialer and CRM what happened, and it determines whether the number gets dialled again.
How many disposition codes should a campaign have?
Most campaigns work well with twelve to twenty codes. Fewer than eight hides useful detail, while long lists slow agents down and invite guessing. Review the set quarterly and retire codes nobody uses.
Who picks the disposition, the agent or the system?
Agents pick it in almost every setup, because only they know how the conversation actually ended. Dialers auto-dispose the mechanical outcomes such as busy, ring-no-answer, and answering machine detection.
Does call disposition affect average handle time?
Yes. Coding happens during wrap-up, which counts inside handle time on most platforms, so a bloated code list quietly raises your cost per contact.
How do you audit disposition accuracy?
Sample recorded calls weekly, compare each recording against the code chosen, and coach the outliers.
If you are building an outbound floor and want partners who already run disciplined disposition sets, browse the Outsource Accelerator BPO hubs.







Independent




