Define the routing inputs
Use fields that are available and trustworthy at assignment time. Geography, product interest, account ownership, customer tier, language, and consent may matter; enrichment that arrives later should not silently change past decisions.
Name the fallback for missing or conflicting values. An unassigned queue with an owner is safer than a lead disappearing because no rule matched.
Order rules and exceptions
Write precedence explicitly: existing account ownership may override territory, strategic accounts may override round robin, and leave coverage may override the normal owner. Keep exceptions time-bounded and attributable.
Store the rule version and reason on the assignment event so an operator can explain the outcome.
- Eligibility
- Priority
- Capacity
- Tie-breaker
- Fallback
- Audit reason
Test distribution and response
Replay a representative historical sample before enabling the new logic. Compare assignment counts, time to first action, reassignment, conversion, and the share landing in fallback.
Fair distribution is not always equal distribution; state the business goal and the constraint being optimized.
Run a test set containing every rule boundary and missing-field combination, then confirm each result includes an owner and an explainable reason.