lead-routing-rules

$npx mdskill add Significant-Gravitas/skills-catalog/lead-routing-rules

Use this when leads go unassigned, land with two people, or wait too long.

SKILL.md

.github/skills/lead-routing-rulesView on GitHub ↗
---
name: "lead-routing-rules"
description: "Write lead routing rules that cover every case once, with a fallback and an owner."
triggers: ["lead routing", "assign leads", "routing rules", "lead assignment", "territory rules"]
version: "1"
---

# Lead routing rules

Use this when leads go unassigned, land with two people, or wait too long.

## List the cases

From the current rules and a dated lead export, list every case the rules must
handle: region, company size, product, source, existing account, existing
owner, partner-sourced, and leads with missing fields. Count how many leads in
the last 90 days fell into each case, and how many had no owner after a day.

## Write the rules

Write the rules in order, first match wins. Each rule has:

- the condition, using fields that exist and are filled;
- the owner or queue it routes to;
- the time the owner has to respond;
- the backup owner when the first is away or at capacity.

End with a fallback rule for anything unmatched, owned by a named person.

## Test against real leads

Run the draft rules on the last 90 days of leads on paper. Report leads that
matched no rule, matched more than one, or would change owner. Show the change
in leads per owner.

Never reassign a lead or edit routing in the CRM yourself, and do not guess a
missing region or size. The sales lead approves the rules before anyone turns
them on.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.