What is a call disposition?
The outcome code logged at the end of a call that decides what happens to the contact next.
Call disposition — A call disposition is the outcome code logged at the end of a call — reached, voicemail, wrong number, booked, not interested — that drives what happens next. It is what turns a call log into a pipeline signal.
Why it matters
A call log by itself is just a record that a call happened. A disposition turns it into a signal a pipeline can act on: reached and interested might trigger a follow-up task, voicemail might trigger a retry in a few days, not interested might remove the contact from the cadence entirely. Without a disposition, every call sits in the log with no way to tell, at a glance, which ones need something done next.
The design problem is that dispositions are only useful if they get logged accurately, which means they have to be fast to choose. A rep or an agent finishing a call is not going to work through a long list of fine-grained outcomes; they will reach for whatever option is fastest, and if the right one isn't obvious in a couple of seconds, they will default to something generic that loses the actual signal.
How a disposition drives what happens next
- 1
The call ends
Whether reached, voicemail or no answer, the call itself is over.
- 2
An outcome is chosen
The rep, or the voice agent, selects a disposition from a short fixed list.
- 3
It's logged against the contact
The disposition attaches to the contact's record, alongside the call itself.
- 4
Downstream logic reacts
A cadence advances, a task is created, or the contact drops out, depending on the code chosen.
The mistake to watch for
Questions
- What is the difference between a call disposition and call notes?
- A disposition is a short, fixed code, like reached or voicemail, chosen from a limited list so it can drive automated logic. Call notes are free text describing what actually happened. A disposition is what a system can act on; notes are what a person reads later for context.
- How many dispositions should a list have?
- As few as the pipeline actually needs to act differently. A short list, often five to eight options covering the outcomes that matter, gets used correctly far more often than a long, granular one that takes too long to read through mid-call.
- Can an AI voice agent set its own call disposition?
- Yes, when it's built to. The agent can select the appropriate outcome code based on how the call went and log it against the contact automatically, the same way a human rep would after a manual call.