Lead summary to routing decision
Lead routing breaks when AI assigns a queue nobody can defend.
Use a visible routing rule to decide whether a lead should be pursued, nurtured, enriched, or skipped before it disappears into a silent CRM queue.
The routing leak
Fast assignment is useless when the next owner cannot see the reason.
Lead routing should turn a fresh lead summary into an owner and a next action. It fails when the rule is hidden, the source is ignored, missing fields are treated as facts, or every ambiguous lead gets pushed to the same queue.
The practical standard is simple: the record must show the route, the rule that fired, the evidence behind the rule, the confidence level, and the action the owner should take next.
Source is not weighted
A demo request, referral, support handoff, and cold reply should not receive the same urgency.
Missing data is hidden
The system routes on guessed segment, territory, or account status instead of flagging the gap.
Owner logic is unclear
Sales sees an assignment but not the policy or reason code that created it.
No action follows the route
The lead is assigned, but nobody knows whether to call, enrich, qualify, nurture, or close the loop.
Central action object
Lead routing rule builder
Paste one lead summary and your current routing policy. The output should produce one route, the rule that fired, the missing fields, and the next action.
Copy-ready prompt
You are a sales operations routing assistant.
Input:
LEAD_SUMMARY:
[PASTE COMPANY, ROLE, SOURCE, MESSAGE, STATED NEED, INTENT CONFIDENCE, MISSING INFO, CRM STATUS, TERRITORY, AND ANY EVIDENCE]
ROUTING_POLICY:
[PASTE THE CURRENT RULES FOR PURSUE, NURTURE, ENRICH, SKIP, OWNER QUEUES, TERRITORY, ACCOUNT OWNERSHIP, AND EXCEPTION REVIEW]
Task:
Build one lead routing decision. Choose exactly one route: pursue, nurture, enrich, or skip.
Return this exact output format:
- recommended route
- rule fired
- owner or queue
- evidence used
- missing fields
- confidence level
- exception flag
- next action
Decision criteria:
Rank the route by evidence strength, ICP fit, urgency, source priority, data completeness, account ownership, and risk of sending the lead to the wrong owner.
Rules:
- do not invent company size, territory, account status, budget, authority, or urgency;
- if a missing field blocks the route, choose enrich instead of guessing;
- if the lead is not a fit, suppressed, invalid, or irrelevant, choose skip and explain why;
- if the lead fits but lacks urgency or a current need, choose nurture;
- if the lead has clear fit, current need, and enough owner data, choose pursue;
- cite the exact field, message phrase, CRM value, or policy rule behind each important point;
- keep the decision short enough to paste into CRM.
QA check:
Before finalizing, list any confident statement that lacks evidence. Replace that statement with Unknown or route the lead to enrich.
Decision grid
Use pursue, nurture, enrich, or skip as routing lanes, not vague statuses.
| Route | Use when | Required proof | Next action |
|---|---|---|---|
| pursue | The lead matches ICP, names a current problem, and has enough fields for owner assignment. | Source, company, role, stated need, account status, owner rule. | Assign owner and send the first response or qualification step today. |
| nurture | The lead has possible fit but no near-term problem, weak urgency, or no direct buying path. | Fit signal plus a reason active sales is premature. | Add to the correct nurture path with a review date and context note. |
| enrich | The lead may be valuable, but a missing field blocks route, owner, or first reply. | The exact missing field and why it changes the decision. | Send to enrichment with a minimum field list, then rerun routing. |
| skip | The lead is invalid, not a fit, suppressed, duplicate without action, or unrelated to the offer. | Clear disqualifying evidence or policy rule. | Close, suppress, merge, or mark no action with the reason code visible. |
Example input
Route from the lead summary, not from a raw notification.
- Company
- Northstar Operations Group
- Role
- VP Operations
- Source
- Inbound operations automation page
- Stated need
- Inbound demo handoffs are inconsistent and urgent requests need faster routing.
- Intent confidence
- Medium-high. The lead names a workflow problem and a planning deadline, but budget is unknown.
- Missing fields
- CRM platform, current inbound volume, and existing account status.
Example lead to route output
The route should explain what happens next and why.
recommended route
pursue, with enrichment attached before the first workflow review. The lead has a current operational pain and a planning deadline.
rule fired
SOURCE_INBOUND_NEED_PLUS_DEADLINE: inbound source, stated handoff problem, VP Operations role, and planning deadline.
owner or queue
Inbound sales operations queue. Assign the owner who handles handoff, routing, and CRM process requests.
missing fields
CRM platform and inbound volume should be enriched or asked in the first reply. Budget remains Unknown and should not be inferred.
next action
Reply today with one clarifying question about inbound volume and offer a short review before the planning meeting.
Quality boundary
AI can classify the lead, but the routing policy must stay visible.
Allowed
Suggest a route from supplied source, company, role, message, CRM status, territory, and approved policy.
Not allowed
Invent missing ownership, create new routing rules, assume budget, or hide the reason code.
Escalate
Use human review for conflicting owner rules, existing customers, suppressed contacts, duplicates, or high-value accounts.
Rerun
After enrichment fills the blocking fields, rerun the same rule so the final route has evidence.
The routing decision is trustworthy when the next owner can read the record and understand the assignment in under one minute.
Use the output
Turn the route into a CRM action, not just a label.
Update the record
Store route, owner, reason code, confidence, missing fields, and next action together.
Protect exceptions
Send low-confidence or conflicting records to review instead of forcing them into a normal queue.
Connect enrichment
When the route is blocked, enrich only the fields required to decide owner or first response.
Connect the playbook
After routing, the sales playbook should define qualification, outreach, follow-up, and CRM hygiene.