What is lead routing?

The plain version

An enquiry arrives. Something has to decide: who owns this, how urgent is it, and how do they find out? That decision, and the rules behind it, is lead routing.

In practice it usually involves four things:

1. Assignment. Which rep, team, or queue gets it.
2. Enrichment. Attaching what you know about the company before the rep sees it.
3. Prioritisation. Whether this one interrupts someone or waits in a list.
4. Fallback. What happens when the assigned person does not pick it up.

Most teams implement the first three and skip the fourth. The fourth is where leads die.

Why the fallback matters more than the rules

Reading what sales and RevOps people write about this, the complaints are almost never “our routing logic is wrong”. They are variations of “the lead went nowhere”:

“Broken lead routing system deletes 300 high intent inbound leads across multiple channels.”

“How do you handle lead routing once you have 1,000+ inbound leads/month?”

A routing system that works perfectly during office hours and silently drops anything arriving at 7pm on Friday is not a working routing system. It is a working routing system for two-thirds of the week.

What to check in your own setup

• What happens to a lead that arrives at 2am?
• What happens when the assigned rep is on holiday for a week?
• What happens when the same person fills the form twice?
• Does anything alert you when a lead has been sitting unowned for an hour?
• Can you answer any of these from data, or only from memory?

That last one is usually the honest problem. If you cannot see unowned leads, you do not know whether this is working.

A note on vocabulary

You will also see this called “speed to lead”. That phrase has real search demand, more than “lead routing”, but roughly half of it comes from real-estate investors buying leads rather than B2B sales teams, and practitioners rarely use it unprompted. We wrote about getting this wrong ourselves.