Lead Routing
The rules and automation that assign every inbound lead to the right owner, fast, with an SLA — so no qualified lead waits or falls through the cracks.
Key facts
- In one sentence
- The rules and automation that assign every inbound lead to the right owner, fast, with an SLA — so no qualified lead waits or falls through the cracks.
- Primary owner
- Revenue Operations
- Workflow
- 8 steps, from “Document the rules of engagement” to “Audit routing monthly”
- North-star metric
- Speed to lead — typical target: < 15 min for demo requests; < 4 business hours overall
What is lead routing?
Lead routing is the process of automatically assigning each new lead to the correct owner — an SDR, an account executive, a partner, or a nurture queue — based on attributes like territory, segment, account ownership, language, and lead source, within a defined service-level agreement. It is the connective tissue between marketing's lead generation and sales' follow-up.
Good routing answers three questions instantly and correctly for every lead: Does this lead belong to an account we already own or are working? Who is the right owner given our territory and segment rules? How fast must they respond? The first question — lead-to-account matching — is the one most teams get wrong, and mismatches there cause duplicate outreach, channel conflict, and CRM chaos.
Routing is downstream of lead scoring (which decides whether a lead is worth working) and upstream of sequencing and qualification (what the owner does with it). Its performance is measured in minutes: conversion research consistently shows response within the first hour dramatically outperforms slower follow-up, and the advantage compounds in competitive categories where the first vendor to respond frames the evaluation.
When to implement
Any team with more than one possible lead owner needs explicit routing rules; automate them once lead volume passes roughly 100–200 per month or when average response time exceeds a few hours. Prerequisites: defined territories or segments, deduplicated CRM accounts, and an agreed MQL definition.
Step-by-step workflow
- 1
Document the rules of engagement
Owner: Revenue Operations + Sales leadership
Before any automation, write down who owns what: territory boundaries, segment definitions (SMB/MM/ENT), named-account lists, partner-sourced rules, and what happens on conflicts (e.g., lead from an account with an open opportunity). Routing automates these rules; if they are ambiguous, automation just distributes the ambiguity faster.
- Define territories and segment cutoffs in writing
- Agree conflict-resolution order: open opp > named account > territory > round-robin
- Get sign-off from sales leadership and publish to the team
- 2
Implement lead-to-account matching
Owner: Revenue Operations
Match every inbound lead to existing CRM accounts before assignment, using domain matching first and fuzzy company-name matching as fallback. A lead from an account with an open opportunity goes to the opportunity owner, not the round-robin.
- Enable domain-based matching in your routing tool
- Handle personal-email leads via enrichment before matching
- Define behavior for customer accounts (route to CS, not sales)
- 3
Enrich before you route
Owner: Revenue Operations
Routing decisions depend on fields the form doesn't ask for — employee count, region, industry. Run enrichment synchronously in the routing flow so segmentation happens on real data, and define a default path for leads that fail enrichment rather than letting them stall.
- 4
Build the assignment flow
Owner: Revenue Operations
Implement the decision tree: matched-account rules first, then segment and territory branches, then weighted round-robin within each pool. Respect working hours, vacations, and capacity caps; support instant re-assignment when a rep is out.
- Order rules from most specific to most general
- Configure round-robin with availability and capacity caps
- Route non-ICP leads to a nurture or self-serve path explicitly
- 5
Attach SLAs and escalation
Owner: Revenue Operations + Sales leadership
Every routed lead gets a follow-up SLA based on intent tier — e.g., 15 minutes for demo requests, 4 business hours for content leads. If the SLA is breached, the lead is automatically re-routed to the next available rep and the breach is logged and reported.
- 6
Notify in the tools reps actually watch
Owner: Revenue Operations
Assignment must surface where reps live: Slack/Teams notification with lead context (score, source, key pages viewed) and one-click links to the record and the dialer. CRM-only notifications are where SLAs go to die.
- 7
Handle the edge cases explicitly
Owner: Revenue Operations
Define written paths for: duplicate leads, leads from open-opportunity accounts, existing-customer leads, partner-registered deals, competitor and student signups, and event-list uploads. Edge cases are 20% of volume but 80% of routing disputes.
- 8
Audit routing monthly
Owner: Revenue Operations
Review a sample of routed leads for correctness, measure SLA attainment and time-to-first-touch by segment, and check round-robin fairness. Publish the numbers — routing disputes end when the data is public.
- Report median and p90 speed-to-lead by intent tier
- Check assignment distribution across reps for skew
- Review misroutes and update rules with a changelog
Roles & responsibilities
| Role | Responsibility |
|---|---|
| Revenue Operations | Owns routing logic, tooling, SLA instrumentation, and the monthly audit. |
| Sales leadership | Owns rules of engagement, territory definitions, and SLA policy; arbitrates disputes. |
| SDR / AE team | Responds within SLA; flags misroutes instead of silently reassigning. |
| Marketing Operations | Ensures lead source, score, and campaign context arrive with the lead. |
| Partner manager | Maintains deal-registration rules that protect partner-sourced leads. |
Tool stack
Routing platform
LeanData · Chili Piper · Default · RingLead — purpose-built matching + routing; Chili Piper adds instant meeting booking
CRM native automation
Salesforce Flow · HubSpot workflows — sufficient at low volume and simple rules
Enrichment
Clearbit · ZoomInfo · Clay — synchronous enrichment for segmentation fields
Scheduling
Chili Piper · Calendly Routing — lets high-intent leads book a meeting at form submit — the strongest speed-to-lead play
Notifications
Slack · Microsoft Teams — where SLA timers actually get seen
Key metrics
| Metric | Definition | Formula | Typical target |
|---|---|---|---|
| Speed to lead | Time from lead creation to first human touch. The headline metric of routing. | First-touch timestamp − lead-created timestamp (median and p90) | < 15 min for demo requests; < 4 business hours overall |
| SLA attainment | Share of routed leads touched within their SLA. | Leads touched within SLA ÷ leads routed | > 90% |
| Routing accuracy | Share of leads assigned to the correct owner on the first pass. | Correctly routed ÷ audited sample | > 95% |
| Match rate | Share of leads correctly matched to existing accounts. | Matched leads ÷ leads from existing accounts (audited) | > 90% |
| Re-route rate | Share of leads reassigned after initial routing — a proxy for rule quality. | Re-routed leads ÷ total routed | < 10% |
Common failure points
| Failure | Symptom | Fix |
|---|---|---|
| Routing before matching | SDR cold-calls an account the AE is closing; customer gets prospected. | Lead-to-account matching runs first, always; open-opportunity and customer rules outrank everything. |
| SLA without escalation | Leads sit untouched in a rep's queue while they're on vacation. | Auto-re-route on SLA breach; respect calendars and capacity in the round-robin. |
| Rules nobody can read | Only one admin understands the flow; every change breaks something. | Keep a human-readable rules-of-engagement doc as source of truth; the automation implements it, not the other way around. |
| Enrichment after routing | Enterprise leads land in the SMB queue because employee count was blank at assignment. | Enrich synchronously before segmentation; define a default queue for enrichment failures. |
| Round-robin as dumping ground | Non-ICP leads consume rep time; good leads wait behind junk. | Route non-ICP to nurture explicitly; round-robin only receives leads worth working. |
| No routing telemetry | Disputes are settled by anecdote; nobody knows real response times. | Instrument every assignment and touch timestamp; publish the monthly audit. |
Frequently asked questions
- What is a good speed-to-lead benchmark?
- For high-intent leads (demo/pricing requests), the working standard is minutes, not hours — under 15 minutes is a common SLA, and teams that let hot leads book a meeting directly at form-submit effectively reach zero. For lower-intent leads, same business day is a reasonable floor. Measure your own conversion by response-time bucket to set defensible targets.
- Round-robin or territory-based assignment?
- They compose: territory, segment, and named-account rules decide the pool; round-robin distributes fairly within the pool. Pure round-robin across the whole team only makes sense when reps are interchangeable — rare beyond early stage.
- Do we need a dedicated routing tool or is CRM automation enough?
- CRM-native automation handles low volume and simple trees fine. Buy a dedicated tool when you need reliable lead-to-account matching, weighted round-robin with availability, SLA timers with re-routing, or auditability — usually around the point routing disputes become a weekly occurrence.
- How should leads from existing customer accounts be routed?
- To the account's CS owner or account manager, not the new-business round-robin — with an alert if the lead looks like an expansion signal (new department, new use case). Prospecting your own customers is the most damaging routing failure and the easiest to prevent with matching rules.
- Who should own lead routing?
- Revenue Operations owns the mechanism (rules implementation, tooling, reporting); sales leadership owns the policy (territories, rules of engagement, SLAs). When ownership is split between marketing and sales instead, leads fall in the gap between the two automation stacks.
Download the SOP
The standard operating procedure for this process — purpose, roles, step-by-step procedure with checklists, metrics, and failure modes — is available as a Markdown file you can drop into Notion, Confluence, or any wiki and adapt.
↓ Lead Routing SOP (.md)Related processes
- Lead ScoringA systematic method for ranking leads by fit and engagement so sales works the accounts most likely to convert first.
- MQL-to-SQL HandoffThe agreement and mechanics by which marketing-qualified leads become sales-accepted pipeline — definitions, SLAs, feedback loops, and the accountability between the two teams.
- RevOps ReportingThe system of record for go-to-market performance: one metric dictionary, one funnel, and a reporting cadence that gives leadership numbers they can trust and act on.
Cite this page
“Lead Routing: definition, workflow, roles, metrics & SOP.” b2bprocess.com, updated 2026-07-08. https://b2bprocess.com/lead-routing