Lead Routing SOP: Rules, SLAs, and Recycle Codes for Demand Handoffs

Why this document exists

An HBR audit of 2,241 US companies found that 23% never responded to a web-generated lead at all, and among responders the average response took 42 hours — while companies that followed up within an hour were roughly 7x more likely to qualify the lead, and more than 60x more likely than those that waited 24 hours or longer. InsideSales’ later analysis of 5.7 million marketing leads found about 8x higher conversion when the first contact attempt happened within 5 minutes rather than 6 minutes or more — yet 77% of those leads never received a single rep attempt. In 2026 the gap hasn’t closed: buyers complete more of their evaluation before they talk to anyone (96% of prospects research before engaging, per HubSpot), which means routing speed and handoff hygiene are now the only things you control between intent and conversation. This SOP turns those findings into operating rules.

1. Purpose and scope

This SOP defines how every inbound and gated-content lead is qualified, routed, worked, and recycled across marketing and sales. It covers:

• Stage definitions and ownership
• Routing rules (territory, segment, product, round-robin, weighted)
• First-attempt SLA timers and escalation paths
• Accept, reject, and recycle reason codes
• Recycle and nurture triggers and cadence
• Exceptions (VIPs, duplicates, out-of-territory, compliance flags)
• Weekly audit checklist and change log

Out of scope: outbound prospecting sequences (owned by SDR leadership), account assignment inside named-account programs, and compensation design. This document does not override existing sales contracts or channel agreements; where they conflict, the signed agreement wins.

2. Stage definitions and ownership

One definition per stage, one owner per stage. If a stage has no named owner, it will be optimized by no one.

Rules that apply to every stage transition:

• Every transition records: timestamp, reason code, owner (from, to), and source campaign.
• No stage can be skipped silently. If a lead goes Lead → SQL, it still gets the codes for both jumps (e.g., MQL accept + SAL convert on the same day).
• “Qualified” is defined as a meaningful conversation with a decision maker — a booking, not a touch. Count touches separately from qualifies; they are different metrics.

3. Routing rules

Order of evaluation matters. Evaluate rules top to bottom and stop at the first match.

1. Compliance blocklist — suppression list, do-not-contact flag, GDPR/CCPA opt-out, pending erasure request. End state: archived, never routed. (See section 7.)
2. Territory — geo or industry territory from account data (industry + country + state). Leads with no territory match go to the unassigned queue, not to a random rep.
3. Product-line fit — product or solution line from the form, firmographics, or intent keywords. Leads with no product fit are routed to the closest line or recycled with code REC-03.
4. Segment — enterprise / mid-market / SMB based on employee count or revenue band. Named-account lists take priority over segment routing.
5. Pool assignment — within the eligible pool (territory × product × segment), assign by:
   • Round-robin: equal rotation across reps in the pool. Simple, perceived as fair, but it ignores capacity and performance.
   • Weighted: capacity-based weights (e.g., 3:2:1 by open pipeline or active meetings), or skill-based weights for product line or segment complexity. Recommended once you have 30+ days of per-rep conversion data.
   • Explicit owner: only for named accounts, channel partners, and VIP referrals. Never for anonymous inbound.
6. Worked-lead guard: a lead previously worked and recycled in the last 60 days routes to a different rep than the last owner.

Worked example — rule table (SAMPLE — hypothetical “Meridian Cloud”, not real data)

Copy this structure; replace values with your real ICP, thresholds, and owners.

Design notes:

• Put the highest-value, lowest-volume conditions first; anonymous general traffic should hit the nurture branch quickly.
• Every condition needs an action that is an end state (assigned, merged, archived, recycled) — never “hold.”
• The sample above is illustrative. Your rule table must be built from your ICP, not copied from this file.

4. SLA timers and escalations

Why minutes matter: InsideSales measured about 8x higher conversion when the first attempt happened within 5 minutes vs 6 minutes or more, on 5.7M leads across 400+ companies — and still found fewer than 15% of worked leads were attempted within the first day, with 57.1% of first attempts happening after more than a week. HBR’s earlier study showed a 7x qualification gap between an hour and “later.” SLAs below are starting defaults, not gospel: set them from your own connect-rate data, but treat “within the hour for hot” as a floor, not a stretch goal.

SLA tiers

Timers run on business hours and are per-territory: a lead submitted at 23:00 Monday in your prospect’s timezone is “cold” for the overnight window only if the rule table says so — timezone-aware routing is a routing rule, not a nicety.

Escalation matrix

For the fuller marketing–sales agreement (accept criteria, handoff SLAs, meeting definitions), pair this section with the Sales–Marketing SLA Setup playbook.

5. Accept / reject / recycle codes

Codes are the audit trail. Every decision on every lead must carry exactly one code from the active list, plus owner and timestamp. Retire codes by renaming, never by reuse; change log it.

Accept codes

Reject codes

Recycle codes

6. Recycle and nurture rules

Recycle is a stage, not a failure. The InsideSales data shows why: 77% of marketing leads never received a single rep attempt, and 80% of inbound follow-up sequences stopped below five attempts (most sat at 2–3), while connection rates rose roughly 15% for sequences of 7+ attempts. Separate the “never worked” bucket from the “worked and genuinely cold” bucket — they need different treatments.

Re-route triggers (any one reactivates a recycled lead and assigns a new owner):

• New intent signal: pricing/demo/contact-page visit, high-intent content download, third-party intent spike
• Form re-submission or reply to a nurture email
• New buyer at the same account (contact change)
• Account joins a named-account or ABM list

Cadence defaults:

• REC-01: 90-day nurture cycle, re-scored monthly; re-route on score re-crossing the MQL threshold
• REC-02: 60-day nurture cycle; re-route on any new intent signal, with a different rep than the last owner (worked-lead guard)
• Nurture content: 4–6 touches per cycle, value-first; no sales asks until a re-route trigger fires

Measurement: track recycle-to-recovery rate (recycled leads that later re-route and convert) per source. If a source’s recycle rate is high but recovery is near zero, that source is producing timing noise, not demand — take it to the 90-Day Demand Generation Audit playbook and action it there.

7. Exception handling

• VIP / executive referral: named owner, no round-robin; route on account name or referrer flag before any other rule except compliance. Sales leadership designates VIPs; SDRs cannot self-designate.
• Duplicates: merge by email first, then domain+company. Keep the newest engagement and the oldest source attribution. Log with REJ-03.
• Out-of-territory: never assign to the wrong territory as a workaround. Route to the correct pool or the unassigned queue; SLA starts on assignment, not on submission.
• Compliance flags: suppression, do-not-contact, and opt-out leads are archived, never routed. GDPR erasure requests and CCPA/CPRA “do not sell/share” requests take priority over every other rule; log the action. For lawful-basis and PECR questions on email and SMS outreach, use the ICO’s direct marketing guidance as the operating reference (see Sources).
• Anonymous traffic: forms without identifiable firmographics go to nurture, not to a rep; the rule table’s final branch must absorb this.

8. Weekly audit checklist

Run every Friday, same time, same owner (RevOps or the person accountable for this SOP).

1. Unassigned queue = 0 (or a documented reason per lead).
2. SLA attainment: first-attempt timers met ≥ 90% of volume, hot tier ≥ 95%.
3. Leads sitting in “assigned” with no attempt logged in 24 h — list, notify managers.
4. Reason-code hygiene: no blank or free-text codes; reject/recycle codes match the definitions.
5. Duplicate rate this week; REJ-03 merges completed, not pending.
6. Recycle triggers fired on time; recovered leads re-routed with a different rep.
7. Compliance queue: suppression/opt-out handled same day; no flagged lead in any working queue.
8. Rule table drift: leads routed in ways the table doesn’t explain (triage as table bug or data bug).
9. Update the change log if anything changed this week.

9. Change log

Every change to this SOP gets a row: version, date, change, owner, reason. A rule table without a change log is an opinion, not a standard.

Next review date: 2026-09-04 (or on any pipeline-attribution change).