# Lead Routing — Standard Operating Procedure > Source: https://b2bprocess.com/lead-routing > Last updated: 2026-07-08. Adapt owners, tools, and thresholds to your organization. ## 1. Purpose 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. ## 2. Scope & prerequisites 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. ## 3. 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. | ## 4. Procedure ### Step 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 ### Step 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) ### Step 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. ### Step 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 ### Step 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. ### Step 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. ### Step 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. ### Step 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 ## 5. Metrics to monitor | Metric | Definition | Formula | 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% | ## 6. Known failure modes | Failure | Symptom | Corrective action | | --- | --- | --- | | 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. | --- This SOP is maintained as part of the B2B process encyclopedia at https://b2bprocess.com. Check the source page for the latest revision.