Inbound Lead Routing Rules

Lead routing determines which rep gets which lead. Bad routing means slow response (lead goes to a rep who's in a meeting), wrong context (enterprise lead goes to an SMB rep), or conflict (two reps claim the same account). Good routing is invisible. The right rep gets the right lead instantly and nobody thinks about it.

The principle: route on the fewest rules possible that produce correct assignments. Every rule adds complexity, edge cases, and maintenance. Start simple. Add rules only when misrouting creates measurable problems.

The Routing Decision Tree

Every inbound lead runs through this logic in order. First match wins.

New inbound lead arrives
  ↓
1. EXISTING ACCOUNT CHECK
   Does this lead's company match an existing Account in CRM?
   → YES: Route to the Account Owner. Stop.
   → NO: Continue.
  ↓
2. EXISTING DEAL CHECK
   Is there an open Opportunity at this company?
   → YES: Route to the Opportunity Owner. Alert them. Stop.
   → NO: Continue.
  ↓
3. NAMED ACCOUNT CHECK
   Is this company on an ABM target list or named account list?
   → YES: Route to the ABM owner for that account. Stop.
   → NO: Continue.
  ↓
4. SEGMENT ROUTING
   Based on enriched data (company size, industry, geography):
   → Enterprise (1000+ employees): Route to Enterprise SDR/AE pool
   → Mid-market (200-999): Route to Mid-market SDR pool
   → SMB (< 200): Route to SMB SDR pool or self-serve flow
  ↓
5. WITHIN-SEGMENT ASSIGNMENT
   Within the correct pool:
   → Round-robin among available reps in that segment
   → OR territory match (geography, vertical) if territories exist
  ↓
6. FALLBACK
   If no segment match or all reps unavailable:
   → Route to SDR manager or a catch-all queue
   → Alert: "Unrouted lead needs manual assignment"

Decision tree rules

• Account match is always Step 1. If someone at Acme Corp requests a demo and Acme Corp already has an account owner, that owner gets the lead. Always. No exceptions. Routing to a different rep creates internal conflict and confuses the prospect
• First match wins. Don't run all rules. Stop at the first match. A lead that matches an existing account shouldn't also go through segment routing
• Fallback is mandatory. Every routing system has edge cases it can't handle. A lead with no company name, from an unrecognized country, with a personal email. The fallback catches these and routes to a human for manual assignment. Without a fallback, leads get lost

Routing Methods

Method 1: Round-Robin

Distribute leads equally among reps in a pool, rotating through the list.

How it works: Rep A gets lead 1, Rep B gets lead 2, Rep C gets lead 3, Rep A gets lead 4, etc.

Round-robin rules:

• Remove reps from the rotation when they're on PTO, in training, or at capacity. If a rep is out, their leads go to the next person. Don't let leads queue
• Weight the rotation if reps have different capacities. A senior AE handling 5 accounts might get 1 lead for every 3 the junior SDR gets. Weighted round-robin handles this
• Reset the rotation weekly or monthly. Over time, small imbalances accumulate. A weekly reset keeps distribution fair

Method 2: Territory-Based

Assign leads based on geography, industry, or company size to reps who own those segments.

Territory rules:

• Every territory must have a primary owner AND a backup. When the primary is unavailable, the backup gets the lead. No orphan territories
• Territories must be mutually exclusive. A lead should match exactly one territory. Overlapping territories (a fintech company in the US matches both "US territory" and "fintech vertical") cause conflicts. Define the priority: vertical first, then geography, or vice versa
• Review territory balance quarterly. If one territory produces 3x the leads of another, the rep in the hot territory is overwhelmed and the rep in the cold territory is idle. Rebalance

Method 3: Skill-Based

Route leads to reps with specific expertise based on the lead's characteristics.

Skill-based rules:

• Requires form data or enrichment to classify the lead's needs. Without data, skill-based routing can't work. Fall back to round-robin
• Don't over-segment. If you have 3 SDRs, you don't need 5 skill categories. Keep the number of skill segments ≤ number of reps / 2

Method 4: Hybrid (Recommended)

Combine methods in priority order. Most B2B SaaS teams should use this.

1. Account match → Account owner (always first)
2. Named account match → ABM owner
3. Territory match → Territory owner
4. Round-robin within matched segment → Next available rep
5. Fallback → Manager / catch-all queue

Routing by Lead Source

Different lead sources may need different routing paths.

Source-based routing rules

• High-intent sources (demo, pricing, chat) get real-time routing with < 30 second assignment
• Medium-intent sources (content MQL) get near-real-time routing with < 5 minute assignment
• Low-intent sources (webinar, newsletter) get batch routing (daily or post-event)
• Never mix high-intent and low-intent in the same routing queue. A demo request sitting behind 50 content download MQLs is a disaster

Routing Data Requirements

Routing is only as good as the data powering it. Missing data = misrouted leads.

Data needed per routing method

Enrichment timing

Enrichment rules:

• For demo requests: route first on email domain, enrich async. Speed > precision. A misrouted lead that gets a call in 2 minutes is better than a perfectly routed lead that gets a call in 10 minutes
• For content MQLs: enrich before routing. These leads have lower urgency. The extra 10 seconds for enrichment produces better routing
• Always have a fallback for leads that can't be enriched. Personal emails (gmail, yahoo), new companies not in enrichment databases, and international leads often fail enrichment. Route to round-robin, not to /dev/null

Routing SLAs

Define how fast the assigned rep must act after receiving the routed lead.

SLA enforcement

• Track assignment-to-first-touch time per rep. Publish weekly. Reps who consistently miss SLA need coaching, not more leads
• Automatic escalation is non-negotiable for demo requests. If the assigned rep doesn't acknowledge within 3 minutes, the lead auto-routes to a backup
• Don't set SLAs you can't measure. If your CRM doesn't timestamp assignment and first activity separately, fix the tracking before setting SLAs

CRM Implementation

HubSpot routing

Salesforce routing

Routing implementation rules

• Test routing with 10 test leads before going live. Create leads that match each branch and verify they land with the right rep
• Log every routing decision. Which rule matched, which rep was assigned, at what timestamp. This is the debug log for when routing goes wrong
• Build a routing audit report. Weekly: leads routed per rep, leads per routing rule, unrouted leads (fallback), and average routing time

Common Routing Scenarios

Scenario: Lead from existing customer's company

A new contact at a company that's already a customer submits a demo request.

Correct routing: Route to the Account Owner (AE or CSM). They know the relationship. A new contact may be a champion for expansion, a replacement for a departed contact, or a different department exploring the product.

Wrong routing: Round-robin to an SDR who has no context on the account.

Scenario: Lead from a competitor's employee

Someone at a direct competitor submits a demo request.

Correct routing: Flag for review. Don't auto-route. This could be competitive intelligence, a genuine buyer who's leaving the competitor, or a mistake. Route to marketing or sales leadership for manual handling.

Scenario: Lead with a personal email (gmail, yahoo)

A demo request comes from a @gmail.com address.

Correct routing: Attempt enrichment on the personal email. If enrichment identifies a company, route normally. If not, route to round-robin with a flag: "Personal email. May need company verification on first call."

Wrong routing: Auto-disqualify personal emails. Some legitimate buyers use personal email, especially founders and consultants.

Scenario: Lead from a company with multiple reps assigned

Two reps own different deals at the same company (one in Sales, one in Expansion pipeline).

Correct routing: Route to the rep who owns the most relevant deal. If the new contact's department aligns with one deal, route there. If unclear, route to the Account Owner (company level) and let them triage internally.

Measuring Routing Effectiveness

Anti-Pattern Check

• No account match step. A lead from a company where you have an active deal gets round-robined to a random SDR. The existing AE doesn't know. The prospect gets a generic pitch. Always check account match first
• No fallback route. Leads that don't match any rule disappear into an unassigned queue where nobody looks. Every routing system must have a fallback that routes to a manager or catch-all with an alert
• Routing rules that take 10+ seconds to process. Complex enrichment-dependent routing delays lead assignment. For high-intent leads, route on email domain first (fast), enrich and correct later (accurate)
• Round-robin that includes reps on PTO. A lead assigned to a rep on vacation waits 5 days for a response. Remove unavailable reps from the rotation automatically or manually before each absence
• No SLA enforcement. Routing assigns the lead perfectly. The rep doesn't respond for 3 hours. Without escalation at 3-5 minutes, perfect routing with no response SLA is useless
• Overlapping territories. A fintech company in New York matches both the "Fintech vertical" territory and the "East Coast geography" territory. Two reps claim the lead. Define priority: one routing dimension takes precedence
• Routing demo requests and content downloads through the same queue. A demo request is 10x the urgency of a content download. Separate high-intent from low-intent into different routing flows with different SLAs
• Never auditing routing accuracy. If 15% of leads are manually reassigned, routing rules are wrong for 15% of leads. Run a monthly audit. Fix the rules that cause the most reassignments