Route page
Route · Lead qualification
Score, disqualify, and hand off only sales-ready leads with clear reason codes.
Goal + expectation
Convert a raw lead batch into an outreach-ready cohort with strict pass/fail logic.
Time estimate: 30–45 minutes for one batch scoring cycle.
Execution priority
- Run one checklist loop end-to-end before branching scope.
- Capture one proof artifact and one measurable verification signal.
Steps
- Define pass threshold (fit, urgency, contact confidence).
- Score each lead with reason codes and disposition.
- Disqualify low-fit leads and capture disqualifier reason.
- Assign owner and next action for approved leads.
- Export approved cohort to outreach workflow.
Tool choice
Use lead scoring guide by default. Open compare only when qualification tooling is uncertain.
Recommended tools
AI lead scoring for B2B services
Practical scoring structure for fit and urgency decisions.
Open scoring guideSimple lead routing rules
Use this to assign ownership and stage handoff cleanly.
Open routing rulesBest AI tools for lead qualification
Use compare page when tool lane choice blocks execution.
Open compareChecklist
- Pass threshold is documented before scoring starts.
- [object Object]
- Failed leads include one disqualifier reason.
- Approved leads include owner and next action date.
Verification
Verify approved cohort has owner, reason-to-contact, and disposition for every kept lead.
Expected outcome
- Outreach team receives only scored and owner-assigned leads.
- Lower wasted sends on bad-fit prospects.
- Clear feedback loop to improve next lead-gen batch.
Evidence instrumentation
Evidence packet and verification
Define the output packet, verify the checkpoint, and record one measurable signal before moving forward.
Checkpoint cadence: Capture baseline before execution, then verify at day-1 and day-7 checkpoints.
Handoff rule: Do not switch tools/routes until one verified packet is saved.
Decision support
Choose your next action
- Why this option: Each option maps to how quickly you need results and how much guidance you want during execution.
- For whom: Teams deciding between direct execution and compare-first self-serve paths.
- When to choose: Pick before step 1 so checklist decisions stay consistent across the route.
- What to do next: Select one path, complete this checklist once, then move to the next route.
Route handoff
Choose the next move while this output is fresh
- Primary next step: Route · Multichannel follow-up — continue the cluster loop with the packet from this route.
- Secondary fallback: Use this if blockers appear and you need to re-check bottleneck priority.