Lead Routing & Assignment Rules: How to Build a System That Actually Works

A lead comes in at 2:14 PM. It sits in a queue. Nobody picks it up. At 4:47 PM, an SDR finally claims it. They call the next morning. The prospect already booked a demo with a competitor who responded in 90 seconds.

This happens hundreds of times a day across B2B organizations. And the root cause is almost always the same: broken lead routing.

Why Lead Routing Matters More Than You Think

The data on speed-to-lead is unambiguous:

InsideSales.com (now XANT) research: Leads contacted within 5 minutes are 100x more likely to be qualified than those contacted after 30 minutes.
Harvard Business Review study: The average B2B company takes 42 hours to respond to a lead. 42 hours.
Drift's analysis: Only 7% of companies respond within 5 minutes.

Every minute between form submission and first contact costs you pipeline. A well-designed routing system doesn't just improve rep efficiency — it directly increases conversion rates by 30-50%.

The Three Core Routing Models

1. Round-Robin

The simplest model. Leads are distributed sequentially across a pool of reps.

When to use it:

Small teams (< 8 reps) with homogeneous territories
Inbound leads with no geographic or segment differentiation
Early-stage companies where every rep sells the same way

The math: If you have 5 SDRs and 100 leads/day, each rep gets 20 leads. Clean. Fair.

The problem: Round-robin treats all reps and all leads as equal. They aren't. Your best closer shouldn't get the same volume as a week-two hire, and a $500K enterprise lead shouldn't be routed the same as a $5K SMB trial.

2. Weighted Assignment

Leads are distributed based on rep capacity, performance, or other factors.

Common weighting factors:

Factor	Weight Logic	Example
Quota attainment	Higher performers get more leads	Rep at 120% → 1.5x weight
Current pipeline value	Reps with thin pipeline get priority	< $100K pipeline → 2x weight
Ramp status	New reps get fewer, easier leads	Month 1-2 → 0.5x weight
Specialization	Certain reps handle certain segments	Enterprise certified → enterprise leads
Availability	On PTO or at capacity → skip	OOO flag → 0x weight

Implementation in Salesforce: Use a custom object (Lead_Assignment_Config__c) that stores rep weights. A Flow checks the config, calculates weighted probability, and assigns via a custom Apex round-robin with weights.

Implementation in HubSpot: Use rotation rules with conditional logic. HubSpot's native rotation supports basic weighting through "proportional distribution" settings.

3. Territory-Based Routing

Leads are assigned based on geographic, industry, or account-size territories.

Territory dimensions:

Geographic: Region, state, country, zip code
Firmographic: Company size, industry vertical, tech stack
Named accounts: Specific companies pre-assigned to reps
Hybrid: Geography + company size (e.g., "Enterprise West" vs "SMB East")

The territory matrix:

Segment	West	Central	East	International
Enterprise (>1000 emp)	Rep A	Rep B	Rep C	Rep D
Mid-Market (100-999)	Rep E	Rep F	Rep G	Rep H
SMB (<100)	Pool 1	Pool 1	Pool 2	Pool 2

Territory-based routing requires clean data. If your lead's company size field is blank 40% of the time, your routing breaks 40% of the time.

Handling Edge Cases (Where Most Systems Break)

The happy path is easy. It's the edge cases that expose bad routing:

Existing Accounts

A lead comes in from a company that already has an open opportunity. If you route this to a random SDR instead of the owning AE, you've just created a terrible customer experience and a potential commission dispute.

Solution: Before any routing logic fires, check:

Does this lead's email domain match an existing account?
Does that account have an assigned owner?
Is there an open opportunity?

If yes to all three, route directly to the account owner. If the account exists but has no open opps, route to the account owner with an alert. If no account match, proceed to standard routing.

Partner/Channel Leads

Leads sourced by partners need different treatment:

Route to the partner manager or a dedicated channel sales team
Tag with partner source for attribution
Ensure the partner gets visibility (portal access or automated updates)
Never route a partner-sourced lead to a direct rep who'll ignore the partner relationship

Named Accounts

Strategic accounts that are pre-assigned regardless of inbound activity. Build a lookup table:

IF lead.company IN named_account_list
  THEN assign to named_account_owner
  SKIP all other routing logic

This check should fire before round-robin, territory, or weighted logic.

After-Hours Leads

A lead submits a form at 11 PM. Your reps are asleep. Options:

Queue and assign at 8 AM: Simple but adds hours of delay
Assign immediately + auto-email: Rep gets it in morning, but an automated acknowledgment goes out immediately
Follow-the-sun routing: If you have global teams, route to the team that's currently in business hours
AI SDR / chatbot: Immediate engagement for qualification, books meeting for a human

The best approach for most teams: assign immediately so the rep sees it first thing, but send an automated response within 60 seconds acknowledging the inquiry and setting expectations.

Building the Routing Flow

Here's the decision tree that handles 95% of scenarios:

Lead arrives → enrich (Clearbit, ZoomInfo, or similar)
Spam/junk check → filter competitors, personal emails (if B2B only), known bad domains
Named account check → if match, route to named account owner → DONE
Existing account check → if match, route to account owner → DONE
Partner source check → if partner-sourced, route to channel team → DONE
Segment assignment → based on employee count, revenue, or other firmographic data
Territory assignment → based on geo + segment
Rep assignment → round-robin or weighted within the assigned territory pool
SLA clock starts → rep has X minutes to make first contact

Salesforce Implementation

Use a combination of:

Lead Assignment Rules for basic routing
Flow Builder for complex conditional logic
Apex triggers for real-time matching against account data
Queue-based routing for team-level assignment before individual assignment

HubSpot Implementation

Use:

Workflows with branching logic for segmentation
Lead rotation for distribution within segments
Contact owner assignment actions
Delay + if/then branches for SLA escalation

SLA Enforcement: The Part Everyone Skips

Routing without SLAs is just organized chaos. Define and enforce:

Lead Source	First Touch SLA	Follow-up SLA
Demo request	5 minutes	2 attempts within 1 hour
Content download	4 hours	3 attempts within 24 hours
Pricing page + chat	2 minutes	Immediate callback
Event/webinar	24 hours	3 attempts within 48 hours
Partner referral	1 hour	Same-day callback

Enforcement mechanisms:

Escalation workflow: If SLA is missed, re-route to a backup rep or manager
Manager alerts: Slack/email notification when SLA is about to breach
Reporting: Weekly SLA compliance dashboard showing response times by rep
Consequences: SLA compliance as a metric in rep performance reviews

Measuring Your Routing System

Track these metrics weekly:

Average speed-to-lead: Time from submission to first meaningful contact (not auto-emails)
SLA compliance rate: % of leads contacted within SLA (target: >90%)
Routing accuracy: % of leads that needed manual re-assignment (target: <5%)
Conversion by route: Compare conversion rates across routing paths to find broken segments
Lead aging: Number of leads sitting unworked beyond SLA

Build a Salesforce report or HubSpot dashboard that shows these in real time. Review weekly in your sales ops standup. If routing accuracy drops below 95%, your rules need updating — usually because territories shifted, reps changed, or a new lead source wasn't accounted for.

Common Mistakes to Avoid

1. Over-engineering on day one. Start with simple round-robin. Add complexity only when you have data showing it's needed.

2. Not accounting for rep capacity. A rep running 80 open opportunities shouldn't receive the same lead volume as one with 30.

3. Ignoring data quality. Routing depends on clean data. If company size is blank, your segment-based routing falls back to... nothing. Always build a default/fallback path.

4. No feedback loop. Reps should have a simple way to flag mis-routed leads. Track those flags. If the same error pattern recurs, fix the rule.

5. Treating routing as a one-time project. Your business changes. New segments, new territories, new reps, new products. Audit your routing rules quarterly.

The Bottom Line

Lead routing isn't glamorous. Nobody's writing LinkedIn posts about their assignment rules. But the difference between a 2-minute response and a 2-hour response is real pipeline — sometimes 3-5x more of it.

Build the system. Enforce the SLAs. Measure the results. Iterate quarterly. Your conversion rates will thank you.