Agree the principles before the rules
Start with what you are optimizing for: response time, expertise, fairness, relationship continuity, or coverage of strategic accounts. Rules that try to satisfy everything become unmanageable. Choose a priority order, such as existing owner first, then named account, then territory, then round-robin, and document it. Having leadership sign off on the order prevents disputes later, because the rules reflect a decision, not an administrator's guess.
- State the objective behind routing in plain language.
- Rank the criteria so conflicts have a defined resolution.
- Obtain sales leadership approval before building.
Defining territories
Territories can be based on geography, industry, company size, product line, or a combination. Choose the dimensions that reflect how your market actually behaves and how your team is organized. Keep the number of territories manageable, since each adds maintenance. Balance them by opportunity potential as well as by headcount, and plan how to adjust as markets shift. A territory model that cannot be changed easily is a liability.
Decide how to treat accounts that span territories, such as multinational customers with several buying centers.
Account ownership, named accounts and overlays
Existing customers should usually route to their account owner, and strategic accounts to named teams. Specialists such as solution engineers or partner managers often overlay territory owners rather than replace them. Define how credit and visibility work for overlay roles. Clear data on parent and child account relationships is essential, because ownership rules often depend on hierarchy.
Sales Cloud implementation →Round-robin, queues and capacity
When several people can take a lead, round-robin distributes it fairly, but fairness is not the same as fit. Include availability, so leads do not go to someone on vacation, and capacity limits so a person is not overloaded. Queues with clear service levels work for teams that share responsibility. Escalate leads that are not accepted or contacted within a set time, so nothing sits idle.
Our Salesforce consulting →Lead quality, deduplication and matching
Routing assumes the lead is real and not already known. Match incoming leads against existing contacts and accounts before assigning, so the right owner sees the activity. Clean obvious duplicates and spam, and define how leads from partners or events are handled. Poor matching creates the worst experience: a customer contacted by a second representative who did not know about the first.
Monitoring and changing the rules
Measure time to first contact, acceptance rate, conversion by source and owner, and the volume of unassigned leads. Review the rules quarterly or when the organization changes. Keep an audit trail of rule changes so you can explain why a lead was routed as it was. Publish the rules where sales teams can read them, which reduces the number of ownership complaints reaching management.
Decisions to settle before configuration starts
- Priority order. Rank existing owner, named account, territory, and round-robin.
- Territory dimensions. Choose geography, segment, or product lines.
- Service levels. Set time limits for acceptance and first contact.
- Overlay roles. Define credit and visibility for specialists.
A realistic first 90 days
- Days 1 to 30. Document current routing, agree principles and priority, and clean account hierarchies.
- Days 31 to 60. Build and test the rules with sample leads, and set up queues and escalations.
- Days 61 to 90. Go live in one region, monitor speed and acceptance, and refine before extending.
Pitfalls to avoid
- Too many rules. Complexity causes errors and disputes. Keep to the essentials.
- No escalation. Without time limits, leads stall silently.
- Ignoring account hierarchy. Ownership rules fail when relationships are unclear.
- Set and forget. Markets and teams change, so the rules must be reviewed.
