Lead Routing

by mbfinotti2dedb3934ca7MITListed Oct 8, 2026Updated Oct 8, 2026Repository updated 3 weeks ago

Design the assignment logic that routes inbound leads to sales reps - rule precedence and waterfall ordering, lead-to-account matching, territory assignment rules (geography, segment, industry, named accounts), round-robin variants (straight, weighted, capacity-based, availability-aware), fallback catch-all queues, SLA escalation and reassignment, and safe rollout of routing changes. Use whenever the user mentions lead routing, lead assignment, territory assignment, round-robin, lead distribution, "who gets this lead", a lopsided round-robin, or leads sitting unworked in a CRM queue - even if they never say "routing". Covers B2B account-based and B2C/PLG high-volume routing. Do NOT use for designing the lead score itself - use mbfinotti/revops-skills@lead-scoring instead.

  1. 2dedb3934ca7Currentcommit 2dedb39Published Oct 8, 2026

Source and attribution

Source:mbfinotti/revops-skillsinskills/lead-routingat commit2dedb39

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal