Lead Disposition

5 min read

Also known as: Call disposition, Lead outcome code, Disposition code

Lead disposition is the standardized outcome code a rep or AI agent assigns to a lead after each touch to track status and next action.

Definition

Lead disposition is the structured tag your sales team applies to a lead after every interaction — a call, email, or meeting — to record what happened and what comes next. Common dispositions include 'connected,' 'voicemail,' 'not interested,' 'callback scheduled,' 'qualified,' and 'disqualified.' Without consistent disposition codes, your pipeline becomes a black box where leads sit indefinitely with no clear status.

In practice, dispositions live as a required dropdown field in your CRM that fires the moment an SDR ends a call or closes an outreach task. Each code typically triggers downstream automation — a 'callback' disposition books a follow-up task, a 'disqualified' code removes the lead from active sequences, and a 'qualified' code routes the record to an AE. Reporting then rolls dispositions up into funnel metrics: connect rates, conversion by source, and rep activity quality.

Disposition is distinct from lead status (which describes where the lead sits in the overall lifecycle: new, working, MQL, SQL) and from outcome (the eventual deal result). Disposition is touch-level; status is record-level; outcome is deal-level.

Why It Matters

Clean disposition data is what separates a forecast you trust from one you guess at. When every touch is coded consistently, you can see which sources actually convert, which scripts get connects, and which reps are working leads versus burning them. It also feeds AI agents the labeled data they need to score leads, prioritize callbacks, and route records intelligently.

When disposition discipline breaks down, leads get worked twice or not at all, follow-ups slip, and managers can't tell the difference between a lazy week and a tough market. Dirty disposition data also poisons any AI scoring layer you build on top — the model learns the wrong patterns because the inputs lie about what actually happened on the call.

Examples in Practice

A 30-person SaaS SDR team uses eight disposition codes tied to dialer outcomes. After each call, the rep picks one — 'connected-qualified,' 'connected-not-fit,' 'voicemail-1,' 'voicemail-2,' 'gatekeeper,' 'bad-number,' 'callback-set,' or 'do-not-call.' The CRM then auto-cadences the next touch based on the code, eliminating manual task creation.

A mid-market services agency notices its connect rate looks healthy at 22%, but close rates are flat. Auditing disposition data reveals reps mark voicemails as 'connected' to inflate activity numbers. Tightening the disposition definitions and adding call-recording spot-checks drops reported connects to 11% but doubles the meeting-set rate within a quarter.

A B2B insurance brokerage routes inbound leads to an AI SDR agent that handles first-touch qualification. The agent applies dispositions automatically based on conversation content — 'qualified-hot,' 'needs-nurture,' 'wrong-vertical,' 'no-response-after-5' — and only hot leads land on a human AE's calendar, cutting AE time-per-lead by roughly 60%.

Frequently Asked Questions

What is lead disposition and why does it matter?

Lead disposition is the outcome tag applied to a lead after each touch — call, email, or meeting — that records what happened and drives the next action. It matters because it's the raw input for every meaningful sales metric: connect rate, conversion rate, source quality, and rep productivity. Without it, you're flying blind on pipeline health.

How is lead disposition different from lead status?

Lead status describes where a record sits in the overall lifecycle — new, contacted, qualified, customer. Lead disposition describes what happened on a specific touch — voicemail, callback set, not interested. A single lead can have one status but dozens of dispositions over its lifetime, one for each interaction logged.

When should I use lead disposition codes?

Use them every time a rep or AI agent completes an outreach action — a dial, an email send, a meeting, a chat session. They should be a required field that blocks the rep from moving on until coded. Skipping dispositions on 'unimportant' touches is how data quality erodes.

What metrics measure lead disposition effectiveness?

Track disposition distribution per rep (are codes consistent across the team?), connect rate (connected dispositions divided by attempts), conversion rate by disposition (which codes lead to closed deals?), and time-in-disposition (how long leads sit before recoding). Compare these across sources to find your best lead channels.

What's the typical cost of implementing lead disposition tracking?

It's usually a configuration cost inside your existing CRM rather than a separate line item. The real cost is process design — defining a tight code list (typically 6 to 12 codes), training reps, and enforcing the field. Expect a few days of admin setup and a couple of weeks of coaching to lock in adoption.

What tools handle lead disposition?

Any modern CRM with sales engagement features supports disposition tracking, usually tied to a dialer or sequencing tool. AI-native CRMs go further by letting an AI SDR agent apply dispositions automatically from call transcripts or email replies, removing the manual-entry burden and standardizing how outcomes are coded.

How do I implement lead disposition for a small team?

Start with 6 to 8 codes max — too many options kill consistency. Define each one in plain language with a clear example, make the field required in your CRM, and tie each code to a default next action. Review disposition reports weekly for the first month to catch reps using codes inconsistently.

What's the biggest mistake teams make with lead disposition?

Too many overlapping codes. When reps face 25 options with fuzzy boundaries, they default to whichever button is fastest, and your data becomes meaningless. The second biggest mistake is not auditing — managers assume the data is clean because the field is required, but reps will gravitate to whichever code avoids follow-up work.

Can AI agents handle lead disposition automatically?

Yes. An AI SDR agent that runs calls or email conversations can apply dispositions in real time based on conversation content — flagging objections, intent signals, or no-fit conditions without rep involvement. This is more consistent than human coding and produces cleaner training data for downstream lead-scoring models.

How many disposition codes should I have?

Most high-performing teams operate with 8 to 12 codes total, split between connected outcomes (qualified, not fit, callback) and non-connected outcomes (voicemail, gatekeeper, bad number, no answer). Going above 15 codes creates decision fatigue and inconsistency; going below 6 means you're not capturing enough signal to act on.

The AMW Suite