Lead routing for SDR teams: fast, owned, no double calls
How to route leads to SDRs: answer inbound interest fast, give every lead one owner, and stop two reps calling the same prospect.
E.164
normalised
38
duplicates
12
DNC removed
Lead routing decides which SDR works which lead, and how fast. Get it wrong and two things happen: hot inbound interest waits in a queue until it goes cold, and two reps call the same prospect about the same client.
Routing is not a one-off assignment rule. It is three questions answered every time a lead moves: who may work it, who is working it now, and when does that end.
Three ways routing breaks
Slow handoff
An inbound lead waits in a shared inbox while interest fades.
No single owner
Everyone can see the lead, so nobody is sure it is theirs.
Double calls
Two SDRs open the same lead minutes apart and both dial.
Speed matters most on inbound
A prospect who just downloaded a guide or asked for pricing is thinking about the problem right now. An hour later they are in meetings; a day later they have forgotten the form. The usual cause of slow follow-up is not lazy reps but a lead that has no owner: it lands in a shared view and everyone assumes someone else has it.
Route the lead to a named SDR the moment it arrives, and make the first touch that SDR’s next task, not a line in a report.
Route by roster, not by round robin
Round robin spreads leads evenly across everyone. That works for one product and one team. It breaks for agencies and multi-product teams, where only some reps know a given client’s offer, language or market.
Route by roster instead: each client project has a named list of SDRs, and only they see its leads. Adding a freelancer to one client gives them that client’s leads and nothing else.
Lock the lead while someone works it
Rosters decide who may work a lead. Reservation decides who is working it. When an SDR opens a lead, it is soft-locked to them for a limited time; others on the roster see it is taken and move on.
The lock must expire on its own. A reservation that waits for the rep to release it will leave leads stuck with someone who went home, changed clients or left.
A routing setup that holds up
- 1
Roster each client
A named list of SDRs per project decides who sees its leads.
- 2
Assign inbound at once
New interest goes straight to one SDR as their next task.
- 3
Reserve on open
Opening a lead locks it to that SDR for a limited time.
- 4
Expire automatically
Stale reservations are released without anyone remembering to.
- 5
Rebalance weekly
Managers move leads between rosters as capacity changes.
Measure it
Track time from lead created to first touch for inbound, and the number of leads touched by more than one SDR in the same week. The first shows whether routing is fast; the second shows whether ownership holds.
Dialbrew handles this with per-project rosters and lead reservation that expires by itself, see lead routing in Dialbrew. For spreading work across a team, see lead distribution, and for what happens after the first call, the lead lifecycle.