Most teams log calls with a list inherited from whichever tool they bought first: answered, no answer, voicemail, not interested, callback. Then they wonder why call data never explains anything about pipeline.
The reason is that those labels describe the telephony, not the sales process. “Answered” tells you the network worked. It does not tell you whether the person was the right person, whether the problem exists, or what should happen next.
Design backwards from your stages
Start with the stages you actually manage, then ask what a call can do to a deal at each one. Every outcome should map to exactly one destination.
| Outcome | What it means | Where the record goes |
|---|---|---|
| Meeting booked | Time in the calendar | Pipeline: meeting scheduled |
| Connected, interested, no time | Right person, real problem, wrong moment | Nurture with a dated task |
| Connected, wrong person | Company fits, contact does not | Back to prospecting, account stays |
| Connected, no need | Problem does not exist here | Closed, reason: no need |
| Connected, competitor in place | Real problem, someone else solved it | Nurture, dated to contract cycle |
| Do not contact | Explicit request | Suppressed across all channels |
| Gatekeeper, name captured | Progress, not a failure | New contact on the account |
| Voicemail left | Touch delivered | Sequence continues, email queued |
| No answer | Nothing happened | Sequence continues, attempt counted |
| Bad number | Data problem | Data flagged, re-enrichment queued |
Ten outcomes, each with a destination. The test for any disposition you are considering adding: if two outcomes send the record to the same place and imply the same next action, they are one outcome.
The four that most teams are missing
Disqualification reasons, split out. “Not interested” is the most expensive label in outbound because it merges wrong person, no need, bad timing and competitor-in-place. Those imply four different actions and three of them are worth revisiting.
Gatekeeper with a name captured. Filing this under “no answer” throws away the most useful thing a blocked call produces.
Bad number. Without it, dead data looks like poor rep performance. With it, you get a re-enrichment queue and a coverage metric for your data vendor.
Do not contact, as a cross-channel action. A request on the phone has to stop the emails, the LinkedIn touches and the WhatsApp thread. If your channels sit in separate tools, this is where compliance quietly breaks.
The metrics this unlocks
With outcomes designed this way, four numbers become available that most teams cannot produce:
- Connect rate against dials, per number and per rep. Around 31% is a healthy benchmark on verified mobiles; a number sitting well below it is usually a data or caller-ID problem rather than a rep problem.
- Conversation-to-meeting rate. The only true measure of the script.
- Disqualification mix. If “no need” dominates, targeting is wrong. If “wrong person” dominates, your contact-level filters are wrong. Two different fixes.
- Data quality, as bad-number rate per source.
Each points at a different owner: the first two belong to sales, the third to targeting, the fourth to your data vendor. That is the actual point of dispositions.
Getting reps to log honestly
Accuracy is a design problem, not a discipline problem. Three things fix most of it: keep the list under twelve, make sure every option changes what happens next, and make logging the outcome replace work rather than add to it. If choosing “meeting booked” schedules the invite and moves the stage, reps choose it accurately. If it just files a label, they choose whatever is nearest.
Next: scripts and objection paths by persona, or what the calls cost per meeting.
Frequently asked questions
What is a call disposition?
The outcome a rep records at the end of a call. Good dispositions describe what happened and what should happen next; bad ones describe only whether the phone was answered.
How many dispositions should we have?
Eight to twelve. Fewer and the data cannot explain anything; more and reps pick whichever is nearest the mouse, which is worse than having none.
What is the most commonly missing disposition?
A specific reason for disqualification. “Not interested” hides four different facts: wrong role, no need, bad timing and a competitor already in place, and each one implies a different next action.
Should dispositions change pipeline stages automatically?
Yes, where the outcome unambiguously implies a stage. A booked meeting should move the deal without a second action, and a disqualification should close it with the reason attached.
How do we stop reps mis-logging?
Make the list short, make every option mean something a rep cares about, and make the outcome do the work of scheduling the next step. Dispositions get logged accurately when logging them saves the rep time.