The Lead Acceptance Standard: Accept, Reject, or Recycle

A routed lead just landed in your queue. Before you touch it, you owe one decision: accept it, reject it, or recycle it, and log a reason a second rep would log too. This guide is the written definition itself, a pass/fail rubric on data, fit, score, and intent plus a fixed rejection-code taxonomy, for account executives, SDR leads, founders working their own inbound, and partnerships teams. Adopt it as team policy and two people grading the same record will reach the same verdict.

Most published advice on the sales-accepted-lead stage stops at "hold an alignment meeting and write down what qualified means." This is the thing that meeting is supposed to produce. It is gradeable, it is applied to one specific record at the handoff gate, and it is designed so the verdict is reproducible.

What "accepted" means, in one testable sentence

Accepting a lead means acknowledging, before any contact, that the record meets the agreed written SLA criteria for data, fit, score, and intent. That is the whole definition. It is a statement about the handoff, not about whether the lead will ever close.

This matters because the sales-accepted-lead (SAL) stage, the point where inside, field, or channel sales formally accept the leads they receive, was never meant to measure lead quality. SiriusDecisions, now part of Forrester, introduced the Demand Waterfall in 2006 to define these stages and handoff points, and described the SAL stage in a 2012 post. The acceptance rate it produces is a definition-alignment gauge. When reps grade fit from the first sales conversation instead of at handoff, the stage is triggered wrongly and the number stops meaning anything.

So the standard draws a hard line. Rejection happens before contact. Disqualification happens only after a rep has contacted the lead and learned there is no interest, need, or budget. An unqualified lead is a third thing: simply not yet evaluated, or not meeting thresholds. Keep these three separate and the rest of the standard holds together.

What acceptance rate should you be hitting

Strive for 90% or better. That is the SiriusDecisions/Forrester target, and a rate below it signals a breakdown between marketing and sales, not a batch of bad leads. The gap between that target and the widely cited 42% real-world average is a measure of disagreement over the definition.

The number cuts both ways, which is the part most teams miss. A low rate means misaligned definitions. A rate near 100% means the bar is too low and a meaningful share of marketing-qualified leads (MQLs) should be rejected with a coded reason. These are opposite failures that need opposite fixes, so "just raise the rate" is always wrong for one of them.

Benchmark names and values come from the Forrester primary post and two practitioner write-ups.

There is a structural reason to get the gate right at all. A formal SAL stage yields 9.3 closed-won deals per 1,000 inquiries versus 4.6 without one. Formalizing acceptance roughly doubles throughput, which is why the verdict deserves a standard rather than a gut call.

The four criteria, and what each one proves

Grade every routed lead on four pass/fail tests before contact: data validity, ICP and persona fit, score, and intent and timing. Each criterion proves one thing, and each has a tell when it lies to you.

Data validity. Proves the record is actionable. The test: email, phone, and company fields resolve and match an enrichment source. When it lies: enrichment had not returned when the rule ran, so a viable lead is coded "insufficient data" on empty fields. The fix is sequencing, covered below.

ICP and persona fit. Proves the lead belongs to your target market. The test: company passes written headcount, revenue, and industry thresholds, and the contact matches target persona and seniority. When it lies: a rep grades fit on opinion rather than the written threshold, so two reps disagree on the same company. Fit must be graded against the number on the page.

Score. Proves the lead cleared the agreed behavioral or firmographic bar. The test: score meets the threshold both teams signed off on. When it lies: the scoring model drifted and a stale threshold passes leads nobody wants. Re-check the threshold during the monthly review.

Intent and timing. Proves the lead is in or near a buying window. The test: intent signals are present and recorded against the bar. When it lies: a single demo-request form inflates intent for a tire-kicker. Treat intent as a recorded state, not a vibe.

A single authoritative pass/fail rubric with explicit test methods per criterion is not established publicly. This section is that rubric. Where your team's thresholds differ, change the numbers, but keep the rule that every criterion is graded against a written value before contact.

The rejection-code taxonomy that keeps reviewers aligned

Use three families of reject reason and keep the picklist short. SiriusDecisions names them: procedural (the lead was incorrectly routed), clerical (the record is incomplete or inaccurate), and definitional (the lead does not meet target market, activity, or lead-level thresholds). Every reject maps to exactly one family.

The trap is length. A long list produces inconsistent selection, because adjacent codes such as "wrong persona," "low seniority," and "no authority" overlap and reps default to whichever they see first. Collapse overlapping codes. The Oracle CRM On Demand default list ships 11 reject codes, including Duplicate, Insufficient Data, Failed to Reach Contact, and Recently Contacted (under 30 days), which is a useful ceiling: borrow from it, do not exceed it.

Families from the Forrester primary post; example codes drawn from the Oracle default list and a B2B taxonomy.

The data layer is what actually enforces agreement. A restricted, status-dependent picklist is what makes two reviewers pick the same code; a free-text reason looks reasoned on one record but cannot be aggregated across a month. A Salesforce practitioner solved a free-text field that was generating problems by converting it to a restricted picklist with a dependency on the Rejected status. Inter-rater agreement is a field-type decision, not a training decision.

Agreement between two reviewers is enforced by the field type, not by the training deck.

The accept, reject, or recycle procedure

Run these eight steps in order on every routed lead. The whole pre-contact grade should take under three minutes; the value is that it is reproducible, not slow.

Enrichment order is load-bearing and sits upstream of step one. Route first and enrich later and the rules ran on empty fields; enrichment feeds routing, never the reverse. Enrichment latency is a top cause of mistaken disqualification, so confirm enrichment completed before you grade.

Applying this standard is only as good as the people holding the queue, and in Refolk's index the supply is heavily concentrated by geography. If you need the reps or the RevOps owners who build these handoff workflows, Refolk returns them by description rather than by filter.

How the SLA clock and recycling fit together

Set a 24-hour accept-or-reject SLA and give every recycled lead a dated re-evaluation. The gate and the clock are in tension, and resolving that tension is what makes the standard pay off.

The clock is not administrative. Forrester's primary text ties the 24-hour best practice and 72-business-hour maximum to follow-up after acceptance; practitioner sources extend the 24-48 hour window to the accept-or-reject decision itself. The reason to keep it tight is response-time math: an MIT study found qualifying odds drop roughly 21x between a 5-minute and a 30-minute contact, and an HBR audit of 2,241 firms and over 100,000 leads found a median response of 42 hours. A gate that takes longer than a day quietly destroys the leads it is supposed to protect.

Windows from the Forrester post, Nutshell, and the MIT/HBR response-time literature.

Recycling is where the reject-versus-disqualify line earns its keep. Rejected leads reroute automatically back to marketing or teleprospecting for resubmission. Recycled leads enter a reason-specific track: no-budget leads get a quarterly value email and a check-in near their budget cycle; no-authority leads get forwardable content plus enrichment to find the real decision-maker; bad-timing leads get a dated reminder that re-surfaces on the date the prospect named. This works because 80% of B2B leads are not immediately sales-ready, and organizations with formal recycling programs achieve 20-30% higher lead-to-opportunity conversion.

How this goes wrong

Most failures here are false positives: a grade that looks correct but was produced by a broken mechanism. These are the eight to audit for, and each has a check you can run.

1. Grading fit after a call, not at handoff. The symptom is a low acceptance rate blamed on "bad leads" when reps are conflating rejection with post-contact disqualification. Check: audit whether any rejection code was logged after a logged call activity. If so, the SAL stage is being triggered by lead quality assessed from the first conversation, which it was never meant to measure.

2. Taxonomy too long. Two reps pick different-but-adjacent codes for the same lead, so reporting looks noisy while reps believe they agree. Check: count how many codes map to the same family and whether "wrong persona," "low seniority," and "no authority" all exist. Collapse overlapping codes.

3. Free-text reason fields. A record looks reasoned but cannot be aggregated, so no spike is ever visible. Check: verify the reason field is a restricted picklist with a dependency on the Rejected status, not an open text box.

4. Enrichment latency causing false rejects. Viable leads get coded "insufficient data" or "out of ICP" only because enrichment had not returned. One team reported enrichment too slow to clear a 50-employee threshold, so most viable leads were disqualified. Check: confirm enrichment completed before the grade timestamp.

5. Rejecting for process failures. A lead routed to the wrong rep, contacted too late, or in an inactive territory gets a definitional reject, blaming the lead for your error. Check: route these to a procedural code and fix the mechanism, not the lead.

6. Recycle equals delete. "Recycled" leads vanish instead of entering a track. Disqualified does not mean deleted. Check: confirm a re-evaluation date and a sequence enrollment exist on every recycled record.

7. Near-100% acceptance read as health. A 98% rate looks like alignment but means no gating. Check: if acceptance sits close to 100%, the bar is too low, and a meaningful share of MQLs should be rejected with a coded reason.

8. No reason-spike monitoring. A single broken form floods "clerical" rejects unnoticed. Check: review the rejection-code distribution monthly; the rates of acceptance and rejection reveal lead-management problems that can be fixed quickly once seen.

Who applies this, and keeping it current

The people who run this standard daily are concentrated, which shapes who you hire and how you staff review. In Refolk's index, there are roughly 48,200 SDR and BDR-titled professionals in the United States against 6,042 in the United Kingdom, an 8x ratio, and roughly 1,623 Revenue Operations and Sales Operations professionals in the US against 177 in the UK, a 9.2x ratio.

Counts from Refolk's index across two country-paired queries; the ratio column is derived.

The practical read: the reps applying the gate are abundant in the US, where the single most common exact title is "Sales Development Representative" and named employers surface like ServiceNow and Placer.ai. The RevOps owners who build the picklist and the routing rules are far scarcer everywhere, and in the UK pool they cluster in London at fintech such as Capital on Tap and The Access Group. Scarcity of the owner, not the applier, is usually what blocks adoption.

Before you call the standard live, verify it against this checklist.

Keep it current by treating the acceptance rate as a living instrument, not a report. Re-run the monthly review on real volume, and when a code spikes or the rate drifts outside the 70-90% band, re-open the definition rather than retraining reps. The thresholds will age as your ICP moves; the mechanism, grade against written criteria before contact and log a coded reason, is what stays. Revisit the picklist whenever a new code starts collecting more than its share of volume, because that is almost always two older codes that should have been one.