Sales & CRM Systems
Lead routing: an owner for every lead, the moment it arrives
Routing decides who takes each inquiry using the rules your team already works by: what the job is, where the customer is, who already knows them, who's on shift and how urgent it is. Then it writes the decision down, so nobody has to ask “is anyone on this?”
Six inquiries. Nobody's name on any of them.
- Web formWater heater leakUnassigned47 min
- PhoneDrain backup, urgentSeen by 3, claimed by none12 min
- EmailQuote: bathroom remodelAnswered twice2 h
- ReferralAC not coolingUnassigned1 h
- Web formAnnual service planWaiting on “whoever's free”3 h
- PhoneToilet leaking, second floorVoicemail, not heard yet25 min
- Water heater leakEast plumbingby 09:47
- Drain backup, urgentEast plumbing · urgent queueby 09:40
- Quote: bathroom remodelEstimatesby 11:00
- AC not coolingHVAC Westby 10:15
- Annual service planService plans queueby 12:00
- Toilet leaking, second floorWest plumbingby 09:55
In a shared inbox, ownership goes to whoever notices first, and “first” depends on who's at their desk. The urgent drain call waits behind a quote request. Two people reply to the same customer with different prices. The Friday 4:55 pm inquiry is still there on Monday.
Routing removes the question. Every lead arrives with a name on it, a reason for that name, and a time by which someone has to act.
Twelve people could take this lead. Four rules get it to one.
12 left · 12 people across four teams can take inbound leads.
East plumbing
- E1
- E2
- E3
West plumbing
- W1
- W2
- W3
HVAC East
- HE1
- HE2
- HE3
HVAC West
- HW1
- HW2
- HW3
Same rules, three different leads
New customer in ZIP 60614 needing plumbing tomorrow. Account owner is skipped, service line, territory and availability narrow it to E2 by rotation, and urgency places it in the standard queue.
An existing customer's request goes straight to W2, who owns the account. The remaining rules aren't needed.
A commercial boiler install matches no service line, so the remaining rules are not reached and the lead goes to the fallback queue, owned by the office manager, with the unmatched pattern logged.
Five questions, asked in the same order every time
01
Account owner
Does this customer already belong to someone?
Existing customers go to the person who already knows them. It's usually checked first, because splitting a relationship costs more than a slower reply.
Watch for: owners who've left. Routing needs to know when an account is orphaned.
02
Service line
Who does this kind of work?
The first real filter for most teams: plumbing or HVAC, new installs or repairs, residential or commercial.
Watch for: requests that fit two lines. Decide which wins before the system has to.
03
Territory
Where is the customer?
ZIP codes, regions or a drive-time radius. Territories should match how your people actually travel, not how a map divides.
Watch for: gaps between territories. Every ZIP needs an answer, even if it's “fallback”.
04
Availability and rotation
Who can take it right now, and whose turn is it?
Shifts, capacity and time off narrow it to people who can act. Rotation, often called round robin, then shares leads fairly among them.
Watch for: round robin on its own. It's fair, but it ignores everything above it.
05
Urgency
How fast does someone need to respond?
Urgent or high-value leads go to a faster queue with a shorter response window.
Watch for: everything marked urgent. Use the scoring that decides urgency, not the customer's subject line.
Every rule set ends in a fallback queue with a named owner. That's what makes “every lead gets an owner” true.
Routing is judged on its bad days
One lead, one missed pickup
- Pickup window · 15 minutes, set per team
- 09:32lead.assignedE2, East plumbing
- 09:47lead.escalatedTeam lead notified
- 09:48lead.reassignedE1, next on shift
No rule matches
The lead goes to the fallback queue and its owner. The pattern that didn't match is logged, so a missing rule gets added once instead of handled by hand every week.
Nobody picks it up
Assignment starts a clock. When the window closes, the lead escalates to a person who can act, then moves to the next available owner. Both steps are recorded.
The CRM is down
The decision is kept and the write to the CRM is retried. An outage delays the update; it doesn't lose the assignment. Repeated failures go to someone to fix.
What routing reads and writes
Reads
Writes
When every input lives in the CRM, its own assignment rules may be enough, and we'll use them. When routing needs live shift data, another system's accounts or a rule the CRM can't express, the decision runs in a small orchestration layer and the result is written back to the CRM, which stays the source of truth for who owns what.
People stay in charge of the rules
- Your team owns the rules. Changing a territory or a rotation is a setting, not a development project.
- Anyone with the right access can reassign a lead; the reassignment is recorded like any other.
- The fallback queue has a named owner who reviews what didn't match.
Worth building when more than one person can say yes
Good fit
- Several people or teams share incoming leads, and who gets which lead changes how fast and how well it's handled.
- Leads arrive after hours, across locations or through more than two channels.
- Existing customers keep landing with the wrong person.
Not the right fit
- One person handles every lead. There's nothing to route.
- Nobody has decided who owns what yet. Routing enforces those decisions; it can't make them.
Questions about lead routing
Is lead routing the same as round robin?
No. Round robin is one rule: take turns among the people who can take a lead. Routing first decides who those people are, by account, service, territory and availability, and then handles what happens when nobody responds.
Can routing run inside the CRM we already use?
Often, yes. Many CRMs include assignment rules, and when they cover your rules we use them. When routing needs data the CRM doesn't hold, like live shifts or another system's accounts, a small orchestration layer makes the decision and writes the owner back to the CRM.
What happens to a lead that matches no rule?
It goes to a fallback queue with a named owner, and the unmatched pattern is logged. Nothing is left unassigned, and the log shows which rule is missing.
Do we need AI for lead routing?
Usually not. Routing works best on explicit rules people can read and change. If any model helps, it's earlier, in qualification, and only where rules can't decide.