How to Give Sales a Simple Lead-Disposition Process

Start with the outcome: a disposition framework reps will actually use

Give sales a process they can follow in seconds, not minutes. The core is a short list of statuses, a required reason field for every status change, and a time-bound first-touch rule. Everything else — dashboards, automation, scoring — supports those three rules.

Define 4–6 statuses that cover every lead's fate

Keep the list short. Each status must represent a distinct action or outcome, not a feeling.

• New — Lead just entered the system. No activity yet.
• Contacted — Rep has made at least one documented attempt (call, email, LinkedIn).
• Qualified — Lead meets ICP criteria and has expressed buying intent. Moves to opportunity.
• Unqualified — Lead does not fit ICP, has no budget, or explicitly said no. Requires a reason code.
• Nurture — Fit is good but timing isn't right. Goes to marketing drip with a re-engagement date.
• Closed — Won or lost. Final disposition with reason.

Do not add "Working," "Attempting," or "Follow-up" as separate statuses. Those are activities, not dispositions. Track activities in the activity log, not the status field.

Require a reason code on every status change

A status without a reason is a black hole. Build a picklist of 8–12 reason codes that map to your statuses:

• For Unqualified: Wrong industry, No budget, No authority, No need, Duplicate, Spam/Bot, Do not contact.
• For Nurture: Not ready, Budget cycle, Contract renewal, Requested later contact.
• For Closed Lost: Lost to competitor, Price, Product fit, Timeline, Ghosted.

Make the reason field required in your CRM before the status can be saved. This single rule eliminates "zombie" leads that sit in limbo for months.

Enforce a 24–48 hour first-touch SLA

New leads must receive a documented touch within one business day (48 hours max). After that, the lead auto-routes to a queue or a round-robin backup rep. The SLA clock starts at lead creation, not at assignment. Track SLA adherence in a daily dashboard — if it drops below 90%, the process is broken.

Layer in lead-quality signals before reps engage

Not every "lead" deserves a rep's time. The source pack from BotRefund identifies repeatable patterns that separate real prospects from automated and invalid submissions. Use these signals to pre-disposition leads or flag them for review before they hit a rep's queue.

Contactability signals

Disconnected numbers, invalid email domains, repeated addresses, or an unusual concentration of one country code often indicate form spam or bot submissions. Run a phone/email validation step at form submit. Leads that fail go to a "Verify" queue, not directly to sales.

Timing and session behavior

Several leads arriving in short bursts, forms submitted immediately after landing, or conversions at unusual hours suggest automation. Real visitors scroll, hesitate, correct fields, and spend meaningful time on the offer page. Sessions with no scrolling, no field corrections, uniform click paths, and near-zero time on page are strong bot indicators.

Campaign and placement patterns

A sharp lead-quality difference by placement, creative, audience expansion, device, or landing page often reveals where invalid traffic concentrates. If one placement delivers 80% of leads but 0% of qualified opportunities, suppress it before reps see those leads.

CRM outcome feedback loop

A high reported lead count paired with no calls connected, demos booked, qualified opportunities, or repeat engagement is the ultimate signal. Feed disposition outcomes back to marketing weekly. If "Unqualified — Spam/Bot" spikes, the problem is upstream, not in sales.

Step-by-step implementation

1. Audit current states — Export all lead statuses used in the last 90 days. Count how many leads sit in each. Identify statuses that haven't changed in 30+ days.
2. Map to the 6-status model — Collapse redundant states. Delete "Attempting," "Follow-up," "Left voicemail." Keep only disposition outcomes.
3. Build the reason-code picklist — Start with the 8–12 codes above. Add 2–3 business-specific codes only if they drive a different downstream action.
4. Configure CRM validation rules — Require reason on status change. Block "New" → "Closed" without passing through "Contacted" or "Qualified."
5. Set up the SLA automation — Time-based workflow: if status = New AND last activity > 24 hours → reassign + notify manager.
6. Add pre-sales quality gates — Integrate phone/email validation at form submit. Flag sessions with bot behavioral signals (see signals above) for manual review before assignment.
7. Launch a 2-week pilot — Run with one team. Measure: SLA adherence, reason-code completion rate, time-to-first-touch, and % of leads reaching Qualified vs. Unqualified.
8. Iterate and roll out — Adjust reason codes, SLA hours, or quality gates based on pilot data. Then expand to all teams.

One common mistake: treating every bad lead as a sales failure

When a lead goes Unqualified, the default reaction is "rep didn't try hard enough." Often the lead was never real. The source pack emphasizes: "Not every bad lead is a bot, and that matters. Treating every unresponsive contact as fraud can make a team exclude a valuable audience." Use the investigation workflow — preserve attribution, compare ad-platform data, website sessions, and CRM outcomes — before blaming the rep or the channel.

Verification step: the weekly disposition health check

Every Monday, pull a report with four columns: Rep, Leads Assigned (last 7 days), % Contacted within SLA, % With Reason Code. Any rep below 90% on either metric gets a 15-minute coaching conversation, not a lecture. The goal is process adherence, not punishment.

Key facts from the source pack

Signal category	What to watch for	Why it matters for disposition
Contactability	Disconnected numbers, invalid email domains, repeated addresses, unusual country-code concentration	Flags likely spam/bot leads before rep contact
Timing	Burst arrivals, instant form submits, unusual-hour conversions	Indicates automation; route to verification queue
Session behavior	No scrolling, no field corrections, uniform click paths, near-zero time on page	Strong bot indicator; suppress or flag for review
Campaign patterns	Sharp quality differences by placement, creative, audience, device, landing page	Identifies waste sources; suppress bad placements upstream
CRM outcome	High lead count, zero calls connected, demos booked, or qualified opportunities	Feedback loop to marketing; proves disposition process is working

Limitations and when this advice does not apply

• High-velocity inbound (100+ leads/rep/day) — You need automated scoring and routing, not manual disposition. This process assumes reps can personally touch each lead.
• Channel partners or resellers — Their disposition process belongs in their CRM. Push reason codes via API or require them in your PRM.
• Product-led growth with self-serve activation — Disposition happens in-product (activated, stalled, churned). Sales only engages PQLs.
• No CRM or a CRM that cannot enforce required fields — Fix the tool first. A process that relies on discipline alone will fail.

Terminology

• Disposition — The final classification of a lead's outcome (Qualified, Unqualified, Nurture, Closed). Not the same as activity.
• Reason code — A standardized picklist value explaining why a lead received its disposition.
• SLA (Service Level Agreement) — The maximum allowed time between lead creation and first documented rep touch.
• ICP (Ideal Customer Profile) — The firmographic and technographic criteria that define a qualified account.
• Bot traffic / invalid traffic — Automated, non-human form submissions or clicks that inflate lead counts but never convert.

FAQ

How many statuses is too many?

More than six. If you have "Contacted — Left Voicemail," "Contacted — Sent Email," "Contacted — Connected," you are tracking activities, not dispositions. Collapse them into "Contacted" and log the activity type separately.

Should marketing see sales disposition data?

Yes. Marketing needs the "Unqualified — Spam/Bot" and "Unqualified — Wrong Industry" counts to suppress bad channels and refine targeting. Share a weekly summary, not raw lead records.

What if a lead re-engages after being marked Nurture or Unqualified?

Reopen as New with a new created date. Do not resurrect the old record — it breaks SLA and attribution tracking. The new entry gets a fresh 24-hour clock.

How do I handle leads that are real people but clearly not buyers (students, researchers, competitors)?

Use "Unqualified — No Need" or "Unqualified — Competitor" reason codes. These are valid dispositions. They tell marketing the targeting worked (real human) but the fit didn't.

Can I automate disposition for obvious bot leads?

Yes. If your bot detection (like the signals in the source pack) reaches high confidence — e.g., 99% across 100+ behavioral, browser, and network signals — auto-disposition as "Unqualified — Spam/Bot" and exclude from rep queues. Keep a human-review override for edge cases.

What is the minimum viable version of this process for a team of 3 reps?

Three statuses (New, Contacted, Qualified/Unqualified), two reason codes (Qualified, Not a Fit), and a 48-hour SLA tracked in a shared spreadsheet. Add CRM enforcement and reason-code granularity when you hit 5+ reps.

How does this connect to ad-platform refunds?

When disposition data shows a consistent pattern of "Unqualified — Spam/Bot" from a specific campaign or placement, you have the CRM evidence needed to file an invalid-traffic refund claim with Google or Meta. The source pack notes that refund-ready reports require click IDs, campaign details, timestamps, and session recordings — all preserved when you don't pause the campaign before investigating.

Further reading and comparison sources

These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.

• How to set up a lead disposition process | Insightly
• How to set up a lead disposition process? | Medium
• Lead Distribution Methods and Best Practices

How BotRefund can help

BotRefund detects the automated and invalid traffic that pollutes lead-disposition data. Its 110+ behavioral, browser, hardware, network, and attribution signals identify bot visits with 99% confidence, and each finding includes a session-by-session explanation — not a generic estimate.

For sales teams, this means:

• Leads flagged as high-confidence bot traffic can be auto-dispositioned as "Unqualified — Spam/Bot" before a rep wastes a call.
• Refund-ready reports (click IDs, timestamps, session recordings, signal-by-signal reasoning) give marketing the evidence to claim invalid-traffic credits from Google and Meta, recovering budget that can be reinvested in clean lead sources.
• Conversion-signal protection suppresses bot conversion events so ad-platform algorithms train on real outcomes, improving lead quality upstream.

Limitation: BotRefund does not replace your CRM disposition workflow. It feeds it. You still need the status framework, reason codes, and SLA enforcement described in this article. The integration point is a pre-sales quality gate: leads that pass bot detection go to sales; leads that fail go to a verification queue or auto-disposition.