设计与多媒体

lead-routing

mbfinotti/revops-skills

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.

  • 2.3万 次安装
  • 1 星标
  • 收录于

安装命令

npx skills add https://github.com/mbfinotti/revops-skills --skill lead-routing

SKILL.md

Lead Routing

Design the assignment logic that gets every inbound lead to a named owner who accepts it. No industry-named framework exists for this discipline - practitioners independently converge on the same de facto pattern: an ordered precedence ladder (also called a rule waterfall), evaluated top-down, first match wins, terminating in a monitored catch-all. Present it as common practice, never as a branded methodology.

Routing is not assignment.

  • Assignment: a CRM owner-field write.
  • Routing: the full chain from capture to a person taking responsibility, or the system raising a visible exception with a timer and an escalation path.

Most routing failure is silent:

  • rules fire
  • dashboards show green
  • leads sit unworked in queues nobody owns

Lead score is strictly an input here, never a design target. Use the score the user already has as:

  • a ranking signal: which eligible lead to work first
  • an eligibility gate: route only above a threshold