Overview
A lead routing planner helps sales operations turn routing logic into a reviewable table before leads hit sales. This playbook installs a lead routing rules table and a routing policy document so owners, territories, fallback queues, SLAs, and rule gaps are visible in one place.
It is built for teams that are still managing routing in a spreadsheet, a scattered SOP, or tribal knowledge. Salesforce describes lead assignment rules as a way to assign leads to users or queues in its assignment rules documentation, but the planning work usually happens before anyone should touch automation.
Why you should make lead routing reviewable
Lead routing breaks quietly. One source stops sending territory data, a rep changes roles, a new segment launches, or two rules claim the same lead. The next thing you know, a good hand-raise is parked in the wrong queue while everyone assumes the process is fine.
The cost is not just administrative mess. Harvard Business Review's classic analysis of online sales lead response is still a useful reminder that fast, clear ownership matters when buyer interest is fresh.
This playbook keeps the replacement boundary narrow. It replaces a routing rules spreadsheet or SOP, not a CRM, lead scoring model, enrichment workflow, or notification system. The value is a clean operating surface: sales ops can see which rules are ready, which owner mappings are missing, which territories need backups, and which fallback queues need policy decisions.
Step-by-step
- 1Confirm the brand, routing scope, lead sources, routing dimensions, owners, queues, territories, fallback expectations, and SLA that should guide the first pass.
- 2Install or reuse the lead routing rules table with enough structure to record rule conditions, source coverage, territories, owners, backups, required data, status, confidence, gaps, and next actions.
- 3Draft the routing policy document so sales operations has one plain-language source of truth for scope, matching order, fallback handling, review rules, and what remains out of scope.
- 4Map each practical routing rule from the user's spreadsheet, SOP, notes, territory plan, or supplied examples, keeping conflicting or incomplete rules visible instead of smoothing them over.
- 5Review the table for owner gaps, missing fallback queues, territory holes, stale owners, overlapping rules, and rules that rely on lead fields the source does not reliably capture.
- 6Summarize ready rules, blocked rules, policy decisions, and the few next changes sales operations should approve before routing reaches live sales motion.
- 7On the optional monthly cadence, review the same installed table and policy for stale owners, new lead sources, territory changes, and unresolved gaps.
Frequently asked questions
Does this replace CRM lead assignment?
No. It replaces the planning spreadsheet or SOP behind routing decisions. CRM implementation, automatic assignment, and notifications are separate workflows.
What inputs are needed?
Bring the lead sources, routing dimensions, owner or queue map, territory notes, fallback policy, and SLA. Existing spreadsheets or SOPs make the first pass faster, but the installed workspace is useful even when the first run starts from rough notes.
How is this different from a lead intake tracker?
A lead intake tracker reviews individual leads after they arrive. This playbook reviews the rule system that decides where leads should go before sales handoff.
How often should sales operations review it?
Run it before a new campaign, territory change, sales capacity shift, or CRM admin update. Use the monthly cadence when routing rules change often enough that stale owners or fallback gaps can create real handoff risk.