Lead Routing: Who Owns a Lead, and When
Lead routing is the set of rules that assigns every new lead to one named owner the moment it arrives, and sets how fast that owner must respond. The rules match a lead to an existing account first, then pick an owner for the rest by a method such as round robin or territory. A lead with no reply inside the window moves to a backup owner.
A plane crossing the country talks to a long chain of air traffic controllers, and at every moment exactly one of them is responsible for it. The handoff happens out loud. One controller tells the pilot which frequency to call next, and the pilot checks in with the new one. No flight drifts through a stretch of sky that nobody is watching.
Leads at a startup drift all the time. A demo request comes in on a Friday afternoon and lands in a shared inbox. Two reps see it, and each assumes the other one took it. Someone finally replies on Tuesday, after the buyer has booked a call with a competitor.
Lead routing gives every new lead its controller. Two questions decide whether yours works. Who owns a lead the moment it arrives, and how long can it wait before it moves to someone else?
How lead routing works
A routing rule runs the moment a lead enters the CRM and writes one name into the owner field. That name stays until the lead becomes a deal or leaves the pipeline. A working setup has five parts:
- Trigger: the event that starts the rule, such as a form fill or a demo request.
- Match: a check for an existing contact or company, so a lead from a current account goes to the rep who already knows it.
- Method: the rule that picks an owner for everyone else.
- Clock: how long the owner has to make first contact.
- Fallback: the backup owner who takes the lead when the clock runs out, or when the first owner is away.
The owner field does the real work. A lead with a name on it has someone accountable for the next touch. A lead without one belongs to the whole team, which means nobody.
Lead routing methods
Teams argue most about the method, and the right one depends on how your sales team divides its work.
| Method | Assigns by | Best fit | Watch for |
|---|---|---|---|
| Round robin | The next rep in a rotation | Reps who sell the same thing to the same buyers | A rep on vacation keeps getting leads unless the rotation skips them |
| Territory | Region, industry or company size | Reps who specialize | Territories fall out of balance as some fill faster |
| Account owner | Whoever owns the company already | Leads from companies in your CRM | Duplicate company records send the lead to the wrong rep |
| Shared queue | Whoever claims it first | Two or three reps in one room | The fastest rep takes the easy leads, and the hard ones wait |
Most startups combine two of these. Check for an account owner first, then rotate whatever is left. Add territories only when your reps start to specialize.
When one person sells: routing still matters with a single seller. Name that person on every lead, set the clock, and name a backup for the days they're out. Your first sales hire then inherits a rule instead of an inbox.
Response time and reassignment
A controller who hands a plane to the next sector doesn't assume the handoff worked. The pilot has to check in. Your routing needs the same confirmation, and the clock provides it.
Speed matters more than most founders expect. Researchers audited 2,241 US companies for Harvard Business Review in 2011. Firms that tried to reach a web lead within an hour were nearly seven times as likely to qualify it as firms that waited even an hour longer. Almost a quarter of the companies never answered at all.
Set the clock in hours, then decide what happens as it runs:
- Reminder: the owner gets an alert partway through the window.
- Reassignment: an untouched lead moves to the backup owner when the window closes, and the CRM records the move.
- Review: the weekly pipeline meeting looks at every lead that changed hands, and asks why.
The response window itself belongs in the handoff rule that marketing and sales sign together. MQL vs SQL covers that rule and the definitions behind it.
When speed isn't the problem: a fast reply to someone who doesn't fit your buyer still wastes a rep's hour. If reps keep rejecting what routing hands them, fix the lead definition before you tighten the clock.
Common routing mistakes
Most routing failures start in the data underneath the rule, so check these before you blame a rep:
- An inbox as the router: a shared inbox shows everyone the lead and assigns it to no one.
- Matching on email address: a buyer who writes from a new address becomes a new lead for a new rep. Match on the company's domain, and merge duplicates before they reach the rule.
- Two systems writing the owner: a sync from another tool can overwrite the owner a rep was just given. Let the CRM alone write the owner field, and make every other tool read it.
- No home for edge cases: a lead with a blank company field or an address outside every territory falls through. Send whatever the rule can't place to one named person.
CRM data hygiene covers the duplicate cleanup that keeps the match step honest.
Deciding who owns each lead
Air traffic control works because ownership is never in doubt, even for a minute. Your leads need the same: one name from the moment they arrive, and a clock that moves them when nobody answers. With one seller, set that up in your CRM this week. With several, add the account match and a rotation, and review every reassigned lead each week.
Routing is one piece of revenue operations, my deepest specialty. It's part of the RevOps role in my fractional CMO engagements, for a company whose brand is fine but whose systems lose leads.
Never let a lead fly without a controller.
Common questions
Should lead routing run in the CRM or in a separate tool?
Lead routing should run in the CRM whenever the CRM can handle it, because the CRM holds the contact record and the owner field. A separate routing tool earns its cost once the rules need territories and capacity limits that the CRM's own workflows can't manage cleanly.
How should lead routing handle a rep who's out of office?
Lead routing should skip a rep who's out of office, so new leads don't sit for days in an unread queue. Most CRM rotations let a manager pause a rep, and the backup owner picks up anything already assigned that crosses its response window.
Who should own a lead from a company that's already a customer?
A lead from a company that's already a customer should go to whoever owns that account, usually an account manager or a customer success lead. That person knows the relationship, and can bring in sales when the lead turns out to be a real expansion opportunity.
When should a startup add territories to its lead routing?
A startup should add territories to its lead routing once its reps specialize by region or company size, and a lead in the wrong hands starts losing deals. Before that point, a simple rotation keeps the workload even and is easier to audit.