RevOps September 23, 2026

Lead Routing: Speed Matters More Than Fairness

Most routing rules are designed to distribute leads fairly between reps. The buyer does not care about fairness, and the cost of the delay dwarfs the cost of the imbalance.

Phin Sutton
Phin Sutton
Co-Founder of grobot
Lead Routing: Speed Matters More Than Fairness, RevOps Source100%Engage62%Reply28%Pipeline15%Closed7%one motion, one set of numbers REVOPS Lead Routing: Speed Matters More Than Fairness Field guide grobot grobotlabs.com

Lead routing is usually designed around fairness (everyone gets an equal share) and fairness is a constraint rather than a goal. The thing being optimised should be time to first response, because that is the variable the buyer experiences and it dominates everything else the routing rules control.

This is for whoever owns the rules and has noticed that some leads never get worked.

Speed Is the Whole Game

An inbound lead has a window of intent and it is short. Someone who filled in a demo form did it while they had a specific problem in mind, and that state does not persist.

The same dynamic governs outbound replies, where teams lose roughly a third of positive responses to follow-up that takes days. A reply sitting four days is usually dead. The person had a moment of interest and it passed.

So the first design question is not "who should own this" but "what is the fastest path to a human." Every rule that adds a step is paid for in response time.

Four Rules Worth Having

In this order, because the order is the priority.

Existing relationship first. If the account has an open opportunity, an assigned owner or a past deal, it goes to that person regardless of anything else. Routing a known account to a new rep is the most visible failure a buyer experiences. They have to re-explain themselves to a stranger from the same company.

Then territory or segment, if you genuinely have specialists. If your enterprise reps sell differently from your SMB reps, that distinction is worth a routing rule. If they do not, skip it, a distinction that exists only on the org chart adds latency for nothing.

Then availability. Route to someone who is working right now, not to whoever is next in the rotation. A lead assigned to a rep on holiday sits until they return, and the rotation is the reason.

Then round robin, as the tiebreaker it should always have been.

The Round-Robin Trap

Pure round robin is the most common design and it fails in a specific way.

It distributes leads evenly and does nothing to ensure they are worked. A rep who is in back-to-back meetings, on leave, or simply not performing receives exactly the same share as your best rep, and the leads sit.

The fix is not a more elaborate algorithm. It is a time-based reassignment rule: if a lead is not touched within a defined window, it goes back to the pool. Fifteen minutes for inbound demo requests, a few hours for lower-intent leads.

That single rule does more for pipeline than any refinement to the distribution logic, because it converts an assignment into a commitment.

Route Replies, Not Just Leads

The part most teams have no rules for at all.

An outbound reply is a routing event. It arrives on LinkedIn, in an email inbox, or in a chat widget, and in most organisations it lands wherever it lands and is handled by whoever notices.

It needs the same treatment as an inbound lead: one place it arrives, an owner, and a response-time expectation. Inside grobot that is Unibox: replies from every channel in one inbox against the same contact record, with Ezra drafting or answering the routine ones so the queue does not build up overnight.

And the exit condition that matters in an agency or multi-rep setup: a reply from anyone at an account pauses sequences for everyone at that account. Two reps working two people at one company is how you lose it.

Keep the Rules Readable

Routing logic accretes. A rule gets added for a campaign, another for a territory change, another for a partner exception, and within two years nobody can explain why a given lead went where it did.

Two disciplines prevent that. Every rule has a written reason and an owner. And every rule gets reviewed when the thing that caused it changes, a territory rule outlives the territory unless someone removes it.

If you cannot explain the routing to a new rep in two minutes, it is too complex, and complexity here is paid for in response time.

Measure Three Things

Frequently asked questions

What should lead routing optimise for?

Time to first human response. Fairness between reps is a constraint, not a goal: the buyer experiences the delay, and the cost of a slow response dwarfs the cost of an uneven distribution.

What is wrong with round-robin lead assignment?

It distributes leads evenly and does nothing to ensure they are worked. A rep on leave or in back-to-back meetings gets the same share as your best rep. Add a time-based reassignment rule (untouched leads return to the pool) rather than a cleverer algorithm.

What routing rules do I actually need?

Four, in order: existing relationship first, then territory or segment if you genuinely have specialists, then availability rather than rotation position, then round robin as a tiebreaker.

Should outbound replies be routed like inbound leads?

Yes, and most teams have no rules for this at all. A reply needs one place it arrives, a named owner and a response-time expectation, plus an exit condition so a reply from anyone at an account pauses sequences for everyone at that account.

Want help putting this to work?

Talk to a grobot strategist about wiring this into your stack.

Talk to a Strategist →

Running outreach for a book of clients? See how benefits agencies run a whole book on one record.