Lead Routing Matrix
Ensure every qualified opportunity reaches the correct person, team, calendar, workflow, or next step — so qualification results in an assigned owner and next action, never an unassigned CRM record.
Link
3
Link Name
Qualification
Role
control
Loop Step
Repair
Purpose
Ensure every qualified opportunity reaches the correct person, team, calendar, workflow, or next step — so qualification results in an assigned owner and next action, never an unassigned CRM record.
Governing Principle
Routing turns a classification into ownership. A qualified opportunity with no owner and no next action is a leak, even if it was qualified perfectly. Every routing outcome must end with a named owner and a concrete next action.
Routing Factors
- Note
- Configurable. No business uses all of these; enable only the factors that apply.
Rule Schema
- Note
- Every routing rule must define all of these fields. A rule without an owner and a next action is invalid.
- Fields
- trigger_condition; qualification_state; destination; primary_owner; backup_owner; response_expectation; escalation_rule; next_action; logging_requirement
Starter Rules
- Trigger condition
- High-intent, in-scope, immediate timeline
- Qualification state
- high_intent
- Destination
- Best-available qualified owner / live calendar
- Primary owner
- On-duty senior intake/sales rep
- Backup owner
- Intake manager
- Response expectation
- Fastest tier (RLR-11)
- Escalation rule
- If unclaimed within SLA, escalate to manager (RLR-15/RLR-26)
- Next action
- Book or warm-connect now
- Logging requirement
- Log owner, timestamp, and booking attempt
- Trigger condition
- Qualified, in-scope, normal timeline
- Qualification state
- qualified
- Destination
- Assigned owner by request_type/territory
- Primary owner
- Owner per request_type map
- Backup owner
- Pool / round-robin
- Response expectation
- Standard qualified tier
- Escalation rule
- Reassign if no action within SLA
- Next action
- Advance to booking or scheduled follow-up
- Logging requirement
- Log assignment + next action date
- Trigger condition
- Potential fit, not ready
- Qualification state
- nurture
- Destination
- Long-term nurture workflow (Link 4 / RLR-25)
- Primary owner
- Nurture owner / automation with named human owner
- Backup owner
- Intake manager
- Response expectation
- No urgent SLA
- Escalation rule
- Revisit at defined date
- Next action
- Enroll in nurture with revisit date
- Logging requirement
- Log nurture enrollment + revisit date
- Trigger condition
- High-value / sensitive / complex
- Qualification state
- escalate
- Destination
- Named senior owner
- Primary owner
- Designated escalation owner
- Backup owner
- Secondary escalation owner
- Response expectation
- Immediate human handoff
- Escalation rule
- If owner unavailable, secondary owner assumes within SLA
- Next action
- Warm handoff with full context
- Logging requirement
- Log escalation reason, owner, acceptance
- Trigger condition
- Evidence of genuine non-fit
- Qualification state
- disqualified
- Destination
- Respectful decline + referral where possible
- Primary owner
- Handling responder
- Backup owner
- n/a
- Response expectation
- Courteous close
- Escalation rule
- n/a
- Next action
- Record disqualification reason (RLR-21); refer out where possible
- Logging requirement
- Log evidenced non-fit reason
- Trigger condition
- Not enough evidence to classify
- Qualification state
- insufficient_information
- Destination
- Return to qualification / incomplete-info follow-up (RLR-19)
- Primary owner
- Handling responder
- Backup owner
- Intake manager
- Response expectation
- Prompt recovery attempt
- Escalation rule
- Escalate after defined recovery attempts fail
- Next action
- Gather missing evidence before any disqualification
- Logging requirement
- Log missing fields + recovery attempts
Edge Case Handling
- Case
- no_matching_owner
- Handling
- Route to a default named fallback owner (never leave unassigned) and flag for rule review.
- Case
- owner_unavailable
- Handling
- Fail over to the backup owner within the response expectation; log the failover.
- Case
- routing_conflict
- Handling
- Apply a documented priority order (e.g. escalation > urgency > territory) so exactly one owner results.
- Case
- incomplete_qualification
- Handling
- Do not force a destination; return to RLR-19 recovery and hold as INSUFFICIENT INFORMATION.
- Case
- high_intent_opportunity
- Handling
- Bypass normal queue to fastest owner/calendar; escalate if unclaimed within SLA.
- Case
- after_hours_opportunity
- Handling
- Apply the Link 2 after-hours model (RLR-14): acknowledge, route to coverage, hand off next business day with context.
- Case
- manual_override
- Handling
- Allow a named person to override routing with a logged reason; overrides are audited.
- Case
- system_failure
- Handling
- Fall back to a monitored manual queue with a named owner; never silently drop a lead.
What To Measure
Whether qualified opportunities reach the correct owner with a next action, and how often leads land unassigned, mis-routed, or in a fallback/failover path.
How To Interpret
Unassigned or fallback-heavy routing means the rules do not cover real cases; frequent overrides mean the rule logic is wrong and should be updated, not worked around.
Action That Follows
Fix routing rules to cover the observed cases, confirm every rule ends in an owner + next action, and wire escalation to RLR-15/RLR-26.
Owner
Revenue operations owner maintains the routing matrix and the owner/territory maps.
How To Implement
Enable only the routing factors that apply, define each rule with all required fields, set a default fallback owner, encode failover and conflict priority, and connect after-hours routing to RLR-14.
How To Test
Send test leads through each rule (including no-owner, owner-unavailable, conflict, after-hours) and confirm each ends with exactly one named owner and a logged next action.
When To Remeasure
Re-audit with RLR-16 at 14 and 30 days; review routing accuracy in RLR-38.
How To Know It Improved
Correctly-routed-of-qualified rises, unassigned/mis-routed records fall, failover works when tested, and every qualified lead in the sample has an owner and next action.
Consolidation Note
Reuses and improves ShiFt's prior lead-routing / territory-management guidance; the public lead-routing-territory-management resource page remains the outward-facing explainer and is not modified. RLR-20 is the canonical operational routing instrument behind it.
Data Minimization
Route on factors that determine the correct owner and next action; do not attach sensitive prospect data to routing records beyond what the receiving owner needs.
Delivery Status
content_ready_delivery_pending
How to implement
Install the change exactly as the playbook describes; log it on the Repair Plan.
How to verify
Installing a workflow is implementation, not closure. QA the repair before you trust it.
Related in this link
Rather not do this part yourself?
You can repair your Revenue Chain yourself with this Kit — or bring in ShiFt at any point. You do not need to finish the DIY path first.
Done with you
Revenue Leak Scan
A ShiFt specialist runs the diagnosis with you and hands you a prioritized repair plan.
Get My Revenue Leak ScanDone for you
ShiFt RevenueOS
ShiFt installs and operates the full Revenue Chain system for you — ConvertOS included.
See RevenueOS