Revenue Systems
Lead Routing
Every lead has an owner within a defined time, or the rule failed.
- Part of
- Revenue Systems
- Owned at
- Workflows layer
- Typical effort
- 2 to 4 weeks
- Runs on
- HubSpot, Salesforce, Zoho, Odoo or Pipedrive
- Part of the discipline
- What is revenue operations
Why it breaks
The operating problem
Assignment stays manual, first come first served, or based on who happens to be available. Leads land with the wrong person, sit unowned overnight, and nobody is accountable when the first touch never happens.
Self-check
Signs you need this
Routing failures are measured in hours. If nobody can tell you who owns last night's leads, the rule does not exist.
- Leads wait overnight for an owner.
- Assignment depends on who is watching the inbox.
- Large accounts land with a junior rep.
- No alert fires when nobody touches a lead.
- Territory disputes get settled by argument.
Page boundary
Where this capability ends
Lead Management defines the lifecycle and the rules. Lead Routing implements assignment. Qualification executes the conversation that follows.
Lead Management
Define lifecycle, ownership, prioritization, nurture and recycling rules.
Workflow Automation
Triggers, rules, actions, exceptions and escalation.
Qualification
Consistent decisions on fit, intent, need, timing and next action.
Concrete intervention
What Revops delivers
Routing is a rule set with a clock attached. Every rule names an owner, a condition and the time within which the first touch must happen.
- RulesRouting rule set: fit, intent, territory, language, offer, capacity
- MatrixAssignment SLA per lead tier
- RulesCapacity and load balancing rules
- RulesFallback and unowned-lead rules
- RulesReassignment and recycling rules
- DefinitionRouting audit log requirement
- DashboardSpeed to lead and unowned lead dashboard
The reasoning model
How ROUTE applies
Routing is the T of ROUTE made explicit: the moment a signal acquires an owner and a deadline.
Recognize
Detect the lead the moment it is created.
Organize
Confirm it carries the data routing depends on.
Understand
Read fit, tier, territory, language and available capacity.
Trigger
Assign an owner and start the SLA clock.
Execute
Hand it over, then verify the first touch actually happened.
The operating architecture
Revops OS mapping
Routing lives in Workflows and writes directly into Control, because the SLA clock it starts is also the measure it is judged on.
- 01
Data
Territory, language, segment, tier, owner, capacity.
- 02
Context
The fit and intent read that decides the tier.
- 03
Workflows primary layer
The assignment rules, fallbacks and reassignment logic.
- 04
Action
The first touch by the assigned owner.
- 05
Control
Speed to lead, unowned leads, SLA breach by tier.
Outcomes
What changes
Speed to lead is the fastest-moving metric in revenue operations. It responds within days of a rule being enforced.
- Every lead owned within its SLA.
- Unowned leads visible in real time.
- Assignment auditable after the fact.
- Load spread against capacity rather than luck.
- Speed to lead measured per tier.
Questions
Frequently asked
Can routing handle territory and language at once?
What happens when nobody is available?
How is this different from Lead Management?
Next step
Where this gets repaired.
Routing is one of the shortest engagements on this site, because it repairs a single gap: the one between a lead arriving and a human seeing it.
