Lead Routing Skill - Skills & Toolkits | Soto Systems Lab

Lead Routing Skill

Value Proposition: Tool-agnostic by design. Interrogates your routing setup, routes you into Design, Audit, or Diagnose mode, and produces logic you can hand to whoever configures your routing tool.

#RevOps#Routing#Skills#Speed-to-Lead#RingLead#LeanData#Salesforce

Last Updated: 2026-06-12

A routing skill that does one job: help you think through lead and contact routing logic, independent of which tool runs the assignment. It does not configure RingLead, LeanData, Chili Piper, Zoominfo Routes, or native CRM rules. It produces the rules you hand to whoever does.

On first invocation, it asks five calibration questions, then routes the conversation into one of three modes — Design (building routing from scratch), Audit (checking if what you have is working), or Diagnose (something is broken). Each mode produces a different kind of output: a rules document, a structured audit reading, or a root-cause-plus-fix.

What to Have Ready Before You Start

Five questions, one screen of typing. The skill will not proceed on guesses — if you skip a question it will ask again.

What tool runs assignment today — RingLead, Zoominfo Routes, LeanData, Chili Piper, Default, native CRM rules, manual, or nothing yet.
What routing model you run or want to run — round-robin, territory, named account / ABM, hybrid, unclear, or designing from scratch.
Why you're here right now — designing routing, auditing what exists, diagnosing a break, or planning a redesign. This picks the mode.
Who owns the routing config day-to-day — RevOps, Sales Ops, a Salesforce admin, a vendor, or nobody clearly. The output is formatted differently depending on whether you implement directly or hand off.
What "good" looks like in 90 days — one sentence. Faster speed-to-lead, even distribution, fewer SLA breaches, less cherry-picking, redesigned territories. The skill calibrates every recommendation against this target.

If you don't have answers to all five, the skill will help you derive them before doing anything else.

For Best Results

This skill is tool-agnostic by design. To specialize it for your stack, load the skill and paste this prompt:

Rewrite this skill so every reference to "your routing tool" is replaced with [RingLead / LeanData / Zoominfo Routes / native Salesforce rules] specific language. Keep the logic identical. Where the skill asks me to configure a rule, point me to the specific UI path or feature name.

When you switch tools, reload the original and respecialize. The logic survives the migration.

Pairs With

Salesforce Data Hygiene — if the diagnosis surfaces matching breaks, duplicate accounts, or enrichment gaps, run that next. Bad data underneath routing produces broken routing no matter how good the logic is.
Pipeline Visibility — if the symptom is "we don't know if routing is working," run Pipeline Visibility first to see whether the breakage is showing up in pipeline creation, conversion, or velocity. Then come back to this skill with a more specific symptom.

# Lead Routing — Bundle A tool-agnostic skill for designing, auditing, and diagnosing B2B lead and contact routing. ## What's in this bundle - **`SKILL.md`** — the full skill file. Calibrates to your setup, routes you into one of three modes (Design / Audit / Diagnose), and produces logic you can hand to whoever configures your routing tool. ## How to specialize this skill for your stack The skill is intentionally agnostic. It does not assume RingLead, Zoominfo Routes, LeanData, Chili Piper, Default, or any specific tool. To specialize it for your stack, ask your AI to rewrite the skill with your tool's vocabulary and configuration paths. Example prompt to give Claude, Glean, or your AI of choice once the skill is loaded: > Rewrite this skill so every reference to "your routing tool" is replaced with RingLead-specific language. Keep the logic identical. Where the skill asks the operator to configure a rule, point them to the specific RingLead UI path or feature name. Keep the calibration, the mode router, and the decision tree intact. The logic does not change. Only the surface does. That way the skill stays useful as you switch tools (or as your current tool gets renamed, acquired, or sunset). ## How to install - **Claude Skills** — upload this bundle as a ZIP in claude.ai → Settings → Skills. - **Claude Projects** — paste `SKILL.md` into the project's custom instructions. - **Custom GPTs / other LLMs** — paste `SKILL.md` into the system instructions field. - **Glean Skills** — upload this bundle as a ZIP in Glean → Settings → Skills.

For Best Results

Pairs With

Skill Bundle Explorer