Routing is one of the least visible and most argued-about parts of revenue operations. A lead lands with the wrong rep, two reps claim the same account, or an enterprise prospect waits a day in a queue. Usually nobody can say exactly which rule caused it.
The black-box problem
Routing logic tends to grow by accumulation. Each new segment, region or exception adds another condition, often in a different tool. After a few years, the system works for most cases but no one can predict what it will do with an unusual one.
Attach a reason to every assignment
The simplest improvement is also the most powerful: record why each assignment happened. Not just the owner, but the rule that matched, the data it used and the rules it skipped.
““Assigned to Mid-Market West because employee count is 640 and HQ is in Denver. Skipped Enterprise rule: below 1,000 employees.””
With that sentence attached, reps can see for themselves why a lead landed where it did. Disputes become questions about data or policy, not accusations of unfairness.
Make rules testable
- Keep routing rules in one place, in plain, readable language.
- Simulate any change against last quarter’s leads before publishing it.
- Track overrides — frequent manual reassignments show where a rule is wrong.
- Review rules on a schedule, not only when something breaks.
Explainable routing doesn’t just reduce friction. It gives RevOps the evidence to improve the system and the credibility to defend the decisions it makes.