lead-routinglisted

# 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 Do not design or tune the scoring model itself. That is the sibling skill `mbfinotti/revops-skills@lead-scoring`. ## Interview - Ask before designing anything. - One question per message. - Offer multiple-choice options when possible. - Skip a question only when the user already answered it. - What creates a lead, and through which ingestion paths - web form, API, list import, chat, scheduling tool, CRM sync, manual entry? - Which lead attributes are reliably populated at capture (country, company size, indust