Lead scoring hub → BDR queue routing

BDR Queue Routing from Lead Scores: Tiered Assignment + Escalation

Lead scoring is half the story. The half that gets skipped is what happens between "lead crosses threshold" and "BDR makes first contact." Without a routing layer that handles tier branching, weighted round-robin, and automatic escalation, the score itself is decoration.

The three routing layers

Layer 1: Tier assignment from score

The tier-assignment workflow from the HubSpot or Salesforce templates handles this. The output is a Lead Tier value (Hot / Warm / Cold / Disqualified). Routing reads the tier, not the raw score.

Why tier and not score: scores fluctuate by 1-2 points all day from minor behavior events. Routing on raw score causes the same lead to bounce between BDRs every few hours. Routing on tier (which only changes when score crosses a threshold) is stable.

Layer 2: Weighted round-robin within tier

Plain round-robin assumes BDRs are interchangeable. They're not. Some close 2x faster on certain industries; some are at capacity; some are on PTO. The right algorithm weights each BDR's slot by:

• • Recent close rate (trailing 30 days) — better closers get more leads
• • Deal-size fit — BDRs who close enterprise deals get enterprise-sized leads
• • Current capacity — open opps, scheduled meetings, OOO status
• • Industry specialization — if defined

Salesforce Round Robin Distributor and LeanData both implement weighted round-robin natively. HubSpot's built-in rotator is plain round-robin and breaks at >5 BDRs.

Layer 3: Escalation when SLA breaches

Without escalation, a missed alert sits in a BDR's queue forever. The lead loses 50%+ of conversion potential within the first hour. The escalation rules need to be aggressive:

When to skip the BDR layer entirely

Below $25K ACV, the BDR qualification step usually destroys more value than it creates. The math: a 5-minute response from an AE converts at ~21x the rate of a 30-minute response. If the BDR adds 15 minutes to the cycle (queue wait + qualification call + handoff), you've lost most of the speed lift. For SMB and self-serve motions, route Hot leads directly to the next available AE.

For deals over $50K ACV, BDR qualification pays for itself. The AE meeting becomes higher-quality (MEDDIC pre-filled, decision process mapped, technical fit confirmed) and the close rate lift is bigger than the speed loss. The 15-minute BDR call is worth the delay.

Between $25K-$50K, the answer depends on BDR quality. If your BDRs are genuinely good at qualification, keep them in the loop. If they're new or under-trained, skip them.

Sequencing the routed lead

Gaming controls (because they will try)

BDRs respond to incentives. If you tie comp to lead-to-meeting conversion without controls, the queue degrades fast. Three controls keep it honest:

• No silent rejections. A BDR can't decline a Hot lead without a manager-approved disqualification reason. Otherwise BDRs cherry-pick easy wins and the hard ones rot in the queue.
• Logged SLA tied to comp. Time-to-first-touch is logged on every lead. Median TTFT per BDR is reviewed weekly. Outliers either retrain or rotate off Hot queue duty.
• Lead-to-opp conversion review. A BDR who books lots of meetings on bad-fit leads ("padding the meeting count") shows up here as having low downstream opp creation. Pull the report monthly.

The handoff that breaks most teams

BDR-to-AE handoff is where 15-25% of conversion gets lost (HBR, 2014). The handoff has to carry forward:

• • The triggering action (which behavior crossed threshold)
• • The full score breakdown (Fit / Intent / which signals contributed)
• • The qualification call notes (BDR's MEDDIC pre-fill)
• • Any BANT or pain qualifiers the BDR captured
• • Confirmed next-step (meeting time, expected attendees)

Build this as a structured handoff template in the CRM, not a free-form note. AEs ignore the free-form notes; they read the structured template.

Common mistakes

• Plain round-robin at scale. Works for <5 BDRs. Breaks fast above that — different speeds, different specialties, different capacities.
• Routing on raw score instead of tier. The lead bounces between BDRs every few hours from normal score fluctuation.
• No escalation path. Missed alerts sit in queues forever. The lead converts on a competitor while you're waiting for a BDR who's at lunch.
• BDR layer for SMB deals. Below $25K ACV, the BDR qualification step destroys more value than it creates. Route Hot leads straight to AE.
• Free-form handoff notes. AEs ignore them. Use a structured handoff template tied to fields the AE can sort and filter on.

Frequently asked