Lead Routing: Rules, Logic, and SLAs
Lead routing assigns inbound records to the right owner under a time commitment. The two things that break it are missing fallback rules, which send unmatched leads into an unmonitored queue, and unenforced SLAs. Route on the account rather than the lead, and alert a manager on breach rather than the person who missed it.
- Design the fallback first. Unmatched leads landing nowhere is the most common silent leak in B2B.
- Route on account, not on lead, or two reps will work the same company from different angles.
- An SLA without an automated breach alert is a documented intention.
- Alert the manager, not the rep. The person who missed the SLA is not the person who will change the number.
- Median response time matters more than almost any channel optimisation available to you.
Why routing is worth getting right
Speed to first contact moves conversion more than almost any channel change available to a B2B company, and it costs configuration rather than budget. A lead contacted within the hour converts materially better than the same lead contacted the next day — not because the lead changed, but because the buying window was open and you were the first credible response in it.
Most companies have a documented SLA and no enforcement, which means the gap between the documented commitment and the actual median is where a meaningful share of the marketing budget quietly goes.
The assignment models
| Model | Assigns by | Good for | Breaks when |
|---|---|---|---|
| Round robin | Even distribution in turn | Homogeneous teams, undifferentiated leads | Reps differ in skill or capacity |
| Territory | Geography or segment | Field motions, regional markets | Territories overlap or are unbalanced |
| Named account | A pre-assigned list | ABM and enterprise | New accounts fall outside every list |
| Score-based | Lead score to rep tier | Mixed-quality inbound | The scoring model is not trusted |
| Capacity-weighted | Current open workload | High volume, variable capacity | Capacity data is stale |
Most mid-market B2B companies end up with a hierarchy rather than a single model: named account first, then territory, then score-based within territory, then round robin as the tie-break. That is fine and usually correct — provided the hierarchy is written down and strictly ordered, because ambiguous precedence is what produces disputed ownership.
The fallback rule nobody builds
Every routing rule needs a defined destination for records that match nothing. Without one, unmatched leads land in an unmonitored queue and are never worked — and because nobody receives them, nobody reports the problem.
This is the single most common silent leak in B2B revenue systems. It is invisible in every standard report, because reports count what was assigned rather than what was not.
- 01Define an explicit catch-all owner
A named person, not a queue and not a team alias. Queues absorb records; people notice them.
- 02Alert on every fallback assignment
A record hitting the fallback means your rules have a gap. It should be treated as an exception to investigate, not as normal operation.
- 03Report fallback volume weekly
If it is rising, your rules have drifted from your market — usually because you started selling into a segment nobody added a rule for.
- 04Fix the rule, not the record
Reassigning the individual lead solves today. Adding the missing rule solves it permanently, and it takes about the same time.
Making SLAs real
An SLA is a number plus an enforcement mechanism. Most companies have the number.
| Lead type | Reasonable SLA | Escalation |
|---|---|---|
| Demo or contact request | Under 1 hour in business hours | Manager at 2 hours |
| High-intent behavioural signal | Same business day | Manager at 24 hours |
| Content download, high fit | 24 hours | Manager at 48 hours |
| Trigger event | 48 hours | Reassign at 5 days |
| Low fit | No SLA — nurture | None |
The escalation column is the part that makes the difference, and the design detail that matters is who gets alerted. Alert the manager, not the rep. The rep already knows they have not called; a notification to them changes nothing. A notification to their manager changes the median within a fortnight.
Routing with context attached
A routed record should arrive with everything the owner needs to act, or the SLA clock is being spent on research rather than contact.
- Why it routed to them — which rule fired, so ownership disputes resolve without a meeting.
- The triggering signal and when it happened.
- Enriched firmographics so the rep is not looking the company up.
- Prior history — previous opportunities, past contacts, and any support interactions.
- Suppression status — whether an open opportunity or a recent touch already exists.
Delivering this as a task with a due date rather than an email notification is a small change with a disproportionate effect on compliance, because a task appears in the place reps already work.
What to measure
- Median time to first contact, by source and by owner. Use the median for the typical case and the 90th percentile to find the tail.
- SLA breach rate, by owner and by team, published weekly.
- Fallback assignment volume — the leading indicator that your rules have gaps.
- Leads with no activity after 7 days — the direct measure of what is leaking.
- Reassignment rate — high numbers mean the routing logic disagrees with reality.
The fourth is the number worth putting in front of leadership. Counting leads that were assigned and never touched turns an abstract routing discussion into a specific, uncomfortable, and immediately actionable figure — and it is usually larger than anyone expects. Where routing sits in the wider system is covered in the GTM tech stack, and the score it routes on in lead scoring that sales trusts.
Want this diagnosed on your own numbers?
The RADAR™ Scan scores your revenue engine in 2 minutes — 12 questions, a 0–100 score, and your gate verdict. No email required.
Run your RADAR™ Scan→Questions this raises.
What is lead routing?
What is the best lead routing model?
Why do leads get lost in routing?
What is a good lead response time SLA?
How do you enforce a lead response SLA?
Related guides.
Four signal families ranked by predictive strength, each with a decay window — plus how to weight them without building a scoring model nobody trusts.
GTM EngineeringSeven layers, how data should actually flow between them, realistic costs by stage, and the three failure modes worth designing out.
GTM EngineeringThe technical operator who builds go-to-market systems instead of running plays — what the role owns, what it pays, and why it appeared.
GTM EngineeringFirst we build your pipeline. Then we build the machine that scales it.
Every engagement starts with the RADAR™ Reveal — a 2-week audit with a scored report, gate verdict, and roadmap. Yours to keep, whatever you do next.