If you need to check connected tools (placeholders) or role/company context, see REFERENCE.md.
Lead Routing
Document or refine lead routing rules and criteria: who gets which leads, when, and why. Use for RevOps, onboarding, and process documentation. This skill works with user input; when CRM or project tracker is connected, it can reference existing routing logic or tickets.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ LEAD ROUTING │
├─────────────────────────────────────────────────────────────────┤
│ ALWAYS (works standalone) │
│ ✓ Gather: segments, criteria, owners, round-robin vs. assignment │
│ ✓ Structure: rules table (criteria → owner/queue), exceptions │
│ ✓ Output: routing doc with rules, SLA, escalation │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM~~: Existing assignment rules, queues, ownership │
│ + ~~project tracker~~: Routing tickets, process docs │
└─────────────────────────────────────────────────────────────────┘
Output Structure
- Rules table: Criteria (segment, source, score, region), Owner/queue, Priority.
- Exceptions: Special cases, override rules.
- SLA: Response time, handoff time.
- Escalation: When and to whom to escalate.
Data Sources (per REFERENCE.md)
CRM (if connected): Assignment rules, queues, ownership, lead source/score.project tracker (if connected): Process docs, routing tickets.- User input: Segments, criteria, owners, round-robin vs. assignment.
1---2name: lead-routing3description: Document or refine lead routing rules and criteria. Who gets which leads, when, and why. Trigger with "document lead routing", "lead routing rules for [team/segment]", or use the /document-lead-routing command.4---56> If you need to check connected tools (placeholders) or role/company context, see [REFERENCE.md](../../REFERENCE.md).78# Lead Routing910Document or refine lead routing rules and criteria: who gets which leads, when, and why. Use for RevOps, onboarding, and process documentation. This skill works with user input; when ~~CRM~~ or ~~project tracker~~ is connected, it can reference existing routing logic or tickets.1112## How It Works1314```15┌─────────────────────────────────────────────────────────────────┐16│ LEAD ROUTING │17├─────────────────────────────────────────────────────────────────┤18│ ALWAYS (works standalone) │19│ ✓ Gather: segments, criteria, owners, round-robin vs. assignment │20│ ✓ Structure: rules table (criteria → owner/queue), exceptions │21│ ✓ Output: routing doc with rules, SLA, escalation │22├─────────────────────────────────────────────────────────────────┤23│ SUPERCHARGED (when you connect your tools) │24│ + ~~CRM~~: Existing assignment rules, queues, ownership │25│ + ~~project tracker~~: Routing tickets, process docs │26└─────────────────────────────────────────────────────────────────┘27```2829---3031## Output Structure3233- **Rules table:** Criteria (segment, source, score, region), Owner/queue, Priority.34- **Exceptions:** Special cases, override rules.35- **SLA:** Response time, handoff time.36- **Escalation:** When and to whom to escalate.3738---3940## Data Sources (per REFERENCE.md)4142- **~~CRM~~** (if connected): Assignment rules, queues, ownership, lead source/score.43- **~~project tracker~~** (if connected): Process docs, routing tickets.44- User input: Segments, criteria, owners, round-robin vs. assignment.
propane-ai