Guides · Working the calls after you make them
Call disposition codes for cold calling
Last updated November 14, 2026
Most pages treat a call disposition as a label you drop in a box for the record. That framing is why so many picklists grow to twenty-five codes nobody trusts. A disposition isn’t a label — it’s a trigger. The one question worth asking of any code is “what should happen the instant a rep taps it?” If the answer is “nothing, it just gets recorded,” the code is dead weight. Everything below is built around that test.
For cold calling, use a short set of roughly eight mutually-exclusive disposition codes, where every code fires a specific next action. Five keep the lead in rotation with a different next step — Interested/meeting, Callback, Gatekeeper, Left voicemail, No answer. Three end the cold sequence — Not interested, Wrong number, Do not call. The rule that actually matters is not the list but what happens on the next dial: the strongest judgment wins, so an interested lead that later rings out stays interested.
The eight codes, and what each one should fire
Copy this set straight into your dialer or CRM picklist. The columns that matter are the last two: every code names an action, and the three with a red stop are the only ones that end the cold sequence. If a code of your own doesn’t fit one of these rows, it’s probably two codes pretending to be one.
| Disposition | When to use it | What it should fire | Cold seq. |
|---|---|---|---|
| Interested / meeting booked | Prospect agreed to a next step or booked time. | Create the follow-up task or calendar hold; move to the active pipeline. | keeps |
| Callback requested | They asked you to call back at a specific time. | Schedule a callback task at the stated time. Never guess the time. | keeps |
| Gatekeeper | You only reached a receptionist/assistant, not the prospect. | Retry at a different hour; log who screens the line. | keeps |
| Left voicemail | Call reached an answering machine and you left (or dropped) a message. | Queue a retry in ~2 days and an optional follow-up email. No "sent" claims. | keeps |
| No answer | Rang out, busy, or hung up before a word — nobody was spoken to. | Return to the dial queue; count the attempt. | keeps |
| Not interested | A real conversation ended in a clear no. | End the cold sequence. Eligible for nurture later — not a do-not-call. | ends |
| Wrong number | The person reached is not the prospect and not at the company. | Flag the data as bad and drop the number from this list. | ends |
| Do not call | They asked not to be contacted, or you must suppress the number. | Add to the suppression/DNC list and remove from every campaign. | ends |
Compliance note: the do-not-call code is an instruction, not a mood. In the US the TCPA requires honoring internal do-not-call requests; the add-to-suppression step is what makes the code do its job. This is general information, not legal advice — confirm your obligations for the places you call.
Why eight, not twenty-five
The temptation is to add a code for every shade of outcome: “interested but no budget,” “interested but timing,” “spoke but distracted.” Resist it. Two things break when the list gets long:
- Reps stop agreeing. Faced with a dozen near-synonyms under time pressure, two reps tag the same call differently, and the report built on those tags quietly becomes fiction. Mutually exclusive beats exhaustive.
- Nuance belongs in the note, not the code.“Interested but no budget until Q2” is one disposition (Callback or Interested) plus a sentence of context. The code routes the lead; the note carries the detail.
A useful stress test: if your Wrong number rate climbs past ~15%, that isn’t a disposition problem, it’s a list-quality problem the dispositions just made visible. A short, honest set earns that kind of signal; a bloated one buries it.
The rule nobody writes down: which disposition wins on the next dial
Here is the part every “what is a call disposition” glossary skips, and it’s the part that decides whether your pipeline is real. A disposition tags one call. But the lead gets dialed again — so what is the lead’s status after a second, third, fourth attempt that each ended differently? Get this wrong and a hot lead silently rots back into the cold queue.
The principle is simple to state and easy to get backwards: the strongest judgment wins, not the most recent dial. Walk one lead through a week:
Notice what did not happen. Friday’s no-answer and Monday’s canceled parallel leg did not overwrite Callback. They were unanswered attempts on a lead a human had already judged, so they counted as attempts and nothing more. A system that let the most recent dial win would have shown this lead as “no answer” by Friday — and your rep would never have seen the callback they promised. That single bug, multiplied across a list, is how teams end a day with “13 dials, one conversation, seven leads marked contacted” and no idea which number to trust.
The ordering you want, top to bottom:
- A rep’s own logged disposition — a human judged the lead; it stands until a human changes it.
- A confident conversation outcome — Interested, Callback, Not interested, Wrong number, Do not call. These set the lead’s status and then protect it.
- A plain contacted signal — someone answered but the outcome was neutral. Better than silence, worse than a judgment.
- An unanswered attempt — voicemail, no answer, busy. These may only overwrite another unanswered state, never a judgment above them.
Letting the dialer keep the codes honest
You can run this set by hand in any CRM picklist, and it works. The friction is that reps forget to tag, and the precedence rule above is tedious to enforce manually. DialSheet is a free power dialer with a built-in CRM that bakes the whole thing in:
- Machine outcomes tag themselves. Voicemail, no answer, busy and — on parallel legs — answering-machine detection are set from the call itself, so reps only ever disposition real conversations.
- The AI proposes the conversation outcome.Every connected call is transcribed and summarized, and the model suggests a disposition (Interested, Callback, Gatekeeper, Wrong number, or a conservative “neutral”) plus the concrete next step — but only when the rep hasn’t already logged one. The rep’s own call always wins.
- Precedence is enforced, not hoped for. A disposition a rep set is never replaced by a later ring, and opt-outs, rejections and wrong numbers suppress the auto-drafted follow-up so nothing chases a lead that said no.
- Your own outcomes, and your CRM’s. Pro accounts name custom outcomes (“Send pricing”) under Settings → Call outcomes, and the HubSpot integration maps each DialSheet outcome to your HubSpot call dispositions so a sequence moves itself.
Stop re-typing what already happened on the call
DialSheet dispositions the calls for you, keeps the strongest judgment on each lead, and drafts the follow-up from the transcript — free for one caller, $19 a month for a 3-seat pack, dialing on your own Twilio. Import a list and watch a day’s outcomes land clean.
Start free — no cardQuestions reps and managers actually ask
What is a call disposition in cold calling?
A call disposition is the one-word outcome a rep tags a call with the moment it ends — Interested, Left voicemail, Callback, Not interested, and so on. In cold calling its job is not record-keeping; it is to fire the next action automatically. A good disposition set makes "what happens next" a consequence of the tag, not a second decision the rep has to remember to make: a callback books a task, a voicemail queues a retry, a do-not-call drops the number from every campaign.
What are the most common cold-calling call disposition codes?
The set almost every outbound team converges on is about eight codes: Interested / meeting booked, Callback requested, Gatekeeper, Left voicemail, No answer, Not interested, Wrong number, and Do not call. Three of those (Not interested, Wrong number, Do not call) are judgments that should end the sequence; the rest keep the lead in rotation with a different next step. Vendors differ on labels but not on the shape of the list.
How many call dispositions should I use?
Keep it to roughly six to ten, and make them mutually exclusive. The failure mode is a 25-code picklist where two reps tag the same call differently, so the data is noise and nobody trusts the report. If you cannot say in one sentence what next action a code fires, it is not earning its place. Add a code only when a real outcome has nowhere to go — not to describe a feeling about the call.
What is the difference between a call disposition and a lead status?
A disposition describes one call; a lead status describes the person across all of their calls. "Left voicemail" is a disposition on Tuesday's call. "Callback" is the lead's status until someone changes it. The link between them is the rule that trips most teams up: a judgment disposition should set the lead's status and then protect it, so a later unanswered dial does not quietly downgrade an interested lead back to "no answer."
Which disposition wins when the same lead is dialed more than once?
The strongest judgment should win, not the most recent dial. If a rep marked a lead Interested on Monday and the number simply rings out on Friday, the lead is still Interested — the Friday ring is a no-answer attempt on an interested lead, not a reason to relabel the person. The ordering most teams want is: a rep's own judgment beats everything, a confident outcome (Interested, Callback, Not interested, Wrong number, Do not call) beats a plain ring, and an unanswered dial only ever overwrites another unanswered state. DialSheet enforces exactly that: a disposition a rep logged is never replaced by a later ring.
Should "not interested" and "do not call" be separate codes?
Yes. "Not interested" means this contact passed today — it can re-enter a nurture track in a quarter. "Do not call" is a compliance instruction: the number comes off every list and stays off. Collapsing them loses the distinction between a soft no you can re-approach and a hard stop you legally must honor. Keep them separate, and have the do-not-call code add the number to your suppression list, not just change a label.
Can a dialer set call dispositions automatically?
Partly, and the split matters. Machine-detectable outcomes — voicemail, no answer, busy, wrong number — a dialer can tag on its own reliably. Conversation outcomes (Interested vs. a polite brush-off) are a judgment, and the honest tools let the AI propose one from the transcript only when the rep did not log their own, with the rep always overriding. DialSheet transcribes the call, writes a summary and a suggested disposition, and auto-sets the lead status for confident outcomes — but a rep's logged outcome always wins outright.
Related, if you’re cleaning up how calls get logged: