Call disposition codes to log and how to use them in outreach

A rep wraps up a dialing session and every single note reads the same: “called, no luck.” Forty calls, one phrase, zero signal. The manager scrolls through the list and can’t tell who hung up, who said no, who asked for a callback next week, and who just never picked up. Nobody follows up on anything, because nobody knows what actually happened.

That’s the real cost of skipping call dispositions. A short, strict list of outcomes turns a vague note into a trigger for the next step in your sequence, whether that’s a retry, a follow-up email, or a calendar link.

In this piece, I’ll walk through the call dispositions worth logging, how they differ from a plain call status, and how to wire each one to a specific next action instead of a shrug. I’ll also show how lemlist uses disposition data internally to separate a bad list from bad timing from a bad pitch, so you can fix the right problem instead of guessing.

What a call disposition is

A call disposition is the label a rep or dialer assigns to a call when it ends, describing the outcome. It answers one question: what happened? Common synonyms include call outcome, call result, and call status, though “call status” can mean something different depending on the tool (more on that below).

If you are building a cold calling motion for the first time, dispositions are the foundation. Without them, every call looks the same in your data, and no automation can fire.

Call disposition versus call status

Many dialers and CRMs separate two fields, and the distinction matters.

A call status is what the phone line did. It is a system-level event: the call rang and was not answered, the line was busy, or the connection failed. The rep does not choose it. The dialer logs it automatically.

A call disposition is what happened in the conversation. The rep reached a gatekeeper, spoke to the prospect who said “not now,” or booked a meeting. This requires a human judgment call.

Keep both fields. The status tells you whether the call connected at a technical level. The disposition tells you what to do next. And never let reps type free text in either field. The moment you allow open notes instead of a fixed pick list, your reporting breaks and no automation can read the outcome.

The call dispositions every outbound team needs

The table below covers the dispositions that map to real next steps in an outbound sequence. Every row answers: what happened, and what fires next?

How to design your disposition list

A disposition list only works if reps actually use it. Here are the rules that keep it functional.

• •

  Every code must be mutually exclusive. If a rep hesitates between two options, the definitions overlap and the data is already dirty.

• •

  One code per call. No multi-select. The rep picks the single label that best describes the outcome.

• •

  Keep the list short enough that a rep can scan it in seconds. If they have to scroll, they will default to whatever is at the top.

• •

  Each code maps to exactly one next action. If a disposition does not trigger a step, it does not belong on the list.

• •

  Write a clear definition for every code, especially edge cases. “Connected, not interested” and “connected, call back later” can blur without a written rule.

• •

  Audit usage quarterly. If a code is never selected, remove it. If reps keep asking “which one do I pick?”, the definitions need work.

Turn each disposition into a next step

Dispositions are only useful if they move the lead forward. Here is how each one should connect to the rest of your multichannel sequence.

No answer triggers a retry call on a different day, plus an email if the prospect has not received one yet. The goal is to vary the channel and the timing. If you are wondering how many times to call a prospect before moving on, the answer depends on your connect rate data, but the disposition is what counts each attempt.

Voicemail left should trigger a follow-up email after a cold call that references the voicemail. Something like “I just left you a quick voicemail about [reason]” gives the prospect context and a second channel to respond on.

Call back later creates a scheduled task at the exact time the prospect requested. This is a warm callback, so treat it differently from a cold retry.

Connected, interested means you send a meeting link immediately or confirm the slot before hanging up. Do not wait. The interest decays fast.

Connected, not interested stops the calling sequence. You can move the lead to a nurture track or mark them closed-lost, but do not keep dialing someone who said no.

Each of these transitions works best when the call step sits inside a multichannel sequence where email and LinkedIn steps are already built. The disposition becomes the branching logic.

Use dispositions to diagnose list and timing problems

When you aggregate dispositions across a campaign, patterns emerge that tell you where the real problem is.

A high wrong number rate points to bad data. Your list source is the issue. According to lemlist internal data, verified phone numbers connect at around 20%, while scraped lists connect at around 10%. If your wrong number rate is climbing, the fix is better enrichment.

A high no answer rate points to timing or channel. You are calling at the wrong hour, or the prospect simply does not pick up unknown numbers. Test different call windows and layer in email or LinkedIn touches.

A high “connected, not interested” rate points to the pitch. The data got you through. The timing was right. But the message did not land. That is a coaching opportunity.

These patterns only surface when dispositions are logged consistently. Across lemlist campaigns, the average call connect rate is 13.8%, the median campaign sits at 9.1%, and the top 10% of campaigns reach 34.1% or higher, based on lemlist internal data. If your numbers fall well below the median, dispositions will tell you whether to fix the list, the schedule, or the script.

Dispositions as call metrics

Every meaningful call metric is built from disposition data. Here are the ones that matter and how to calculate them.

• •

  Connect rate = (calls where the prospect answered / total calls dialed) x 100. This includes all “connected” dispositions: not interested, call back later, interested, and meeting booked.

• •

  Conversation rate = (calls where a real conversation happened / total calls dialed) x 100. Exclude pickups that lasted under a few seconds or reached a gatekeeper only.

• •

  Meetings per connected call = (meeting booked dispositions / total connected dispositions) x 100. This measures pitch effectiveness once you get through.

• •

  Wrong number rate = (wrong number dispositions / total calls dialed) x 100. This is your data quality thermometer.

Channel sequencing changes these numbers dramatically. lemlist internal data shows a warm call placed after a LinkedIn connection accept connects at 21.4%, compared to 9.6% for a cold first-touch call. That gap shows why dispositions need to live inside a multichannel sequence, not in a standalone dialer.

For a deeper look at what to track, see the guides on cold calling metrics and call tracking and analytics.

Common disposition mistakes

Five patterns break disposition data faster than anything else.

• •

  Free text notes instead of codes. If reps type “spoke to someone, they seemed busy,” no system can parse that into a next step or a report. Force a pick list.

• •

  Codes that overlap. “Not interested” and “rejected” sound different but mean the same thing. Reps split between them, and your data splits with them.

• •

  “Other” as the most used code. If more than a small fraction of calls land on “other,” your list is missing a real outcome. Find out what reps are lumping in there and add a proper code.

• •

  Dispositions that never trigger an action. A code like “spoke to prospect” tells you nothing about what happens next. Every disposition must map to one next step, or it is dead weight.

• •

  Outcomes that stay in the dialer. If dispositions live only in the dialer, the AE who picks up the lead has no context. Push every outcome to the CRM so the full history travels with the contact.

How to log call dispositions in lemlist

lemlist keeps calling inside the same workflow as email and LinkedIn, so dispositions feed directly into the sequence logic.

You can call prospects from lemlist using in-app calling, then set a call status after each call ends. The status is your disposition. It logs to the lead record and determines what fires next.

For higher volume, the parallel dialer lets you work through a list faster and log outcomes as you go. You are not switching between a dialer and a CRM. Everything stays in one place.

Because calls sit inside multichannel sequences alongside email and LinkedIn steps, a call disposition can trigger a follow-up email or a LinkedIn message automatically. The call is not isolated. It is one step in a chain with conditions built around the outcome.

You can mark leads as Interested or Not interested, and the campaign stops on reply. That means a “connected, not interested” disposition removes the lead from further touches without manual cleanup.

All call activity pushes to HubSpot, Salesforce, or Pipedrive natively, or you can send events through webhooks to any system in your stack. The disposition travels with the lead.

Final takeaway

A call disposition is a one-second decision that determines whether a lead moves forward or disappears into a spreadsheet. Keep your list short, map every code to one next action, and use the aggregate data to fix your lists, your timing, and your pitch. The reps who log clean dispositions are the ones whose managers can actually help them improve.

Build your first signal-based sequence in lemlist.