Inbound lead routing: who gets the lead, and why

Two decisions, not one

Ask a team how leads are routed and you will usually get an answer about assignment: round robin, or by territory, or whoever picks it up. That is half the question.

Segmentation comes first and decides which pool a lead sits in. Assignment comes second and decides who inside that pool owns it. Configuring assignment without segmentation means every lead is treated as the same kind of lead, which is only true if your buyers are all the same, and they are not.

The reason this matters more than it sounds: segmentation is what makes the qualification standard applicable. A single set of criteria stretched across genuinely different buyers produces either a standard too loose to mean anything or one that disqualifies half your market. Segment first and each pool can have criteria that fit it.

What to segment on, and what to ignore

One rule: segment on attributes that change who can serve the lead or how it has to be handled. Everything else is decoration that makes a diagram look thorough.

For WorkStore, the exclusive India partner for the Dyson Airblade series, the attribute was state. Inbound arrived from the website, from paid media and from referral partners, and the first step was pooling all of it and bucketing it by state before anything else happened. That is not an obvious choice until you look at the product: commercial hand dryers and air purifiers sold to facilities and procurement teams at hotels, hospitals, commercial real estate and managed office operators. Installation, service and delivery all vary by state, so state decided who could actually fulfil the order. India is not one market for a physical product, and treating it as one is how enquiries sit in a queue nobody can act on.

For a software company selling internationally, the equivalent attributes are usually time zone, because coverage decides response time, and deal size, because it decides whether the lead should reach an SDR or go straight to an account executive. For a company with distinct product lines it is the product. The test is always the same: if the boundary would not change the next action, do not draw it.

Two attributes is usually enough. Teams that segment on five end up with pools too small to staff and rules nobody can hold in their head, which is a slower path to the same failure as not segmenting at all.

Why round robin underperforms, and when it is fine

Round robin is the default in almost every CRM because it is the easiest rule to justify internally. It distributes leads evenly between reps. That is a fairness objective, and fairness between reps is not the same thing as getting the buyer to the right person quickly.

What round robin cannot see:

• Who is actually available. A rep in a two hour meeting, on leave, or at the end of their shift receives leads at the same rate as anyone else.
• Who knows the segment. The rep who has closed four hospitality deals is a better answer for the fifth than whoever is next in the rotation.
• Where the buyer is. Assigning a London enquiry to a rep asleep in Singapore satisfies the rule and loses the hour that mattered.

Round robin is genuinely fine when every rep is interchangeable, all sit in one market, and the deal is simple enough that expertise does not change the outcome. It gets weaker with every one of those that stops being true. The usual upgrade is not a sophisticated algorithm: it is round robin inside a segment, with an availability check, which is a small change and recovers most of the loss.

Whatever rule you pick, assign to a named individual. A shared inbox or an unassigned queue is the single most reliable way to make a lead nobody’s responsibility, which is the ownership failure described in speed to lead.

What a handover has to carry

Routing usually ends in a handover, and most handovers pass a record: name, company, phone number, maybe a form field. The receiving rep then re-runs discovery that has already been done, which costs the buyer their patience and tells you nothing about whether qualification is working.

A handover should pass the reasoning. For WorkStore, qualified leads went to the client’s own sales team with the answers attached against each of the four criteria used on the call: budget, genuine need, timeline, and the number of units required. The receiving salesperson could see not only that the lead had cleared the bar but on what basis.

That has a second benefit worth more than the time saved. When acceptance rates are disputed later, and they always are, a handover that records the reasoning makes the standard auditable. Without it, an argument about lead quality is two teams asserting different memories of the same calls.

Routing rules decay, and nobody notices

Routing is configured once, usually during a CRM implementation, and then encodes an organisation chart that changes underneath it. Reps leave, territories get redrawn, a product line is added, someone changes shift. The rules keep firing.

The symptom is specific and easy to check: leads assigned to people who no longer own that segment, or to accounts that have left the company. Pull last month’s inbound, group by assigned owner, and look for names that surprise you. Then check for leads with no owner at all, which is the same failure in its purest form.

Reviewing the rules once a quarter is enough. What is not enough is assuming that because routing was correct when it was built, it is correct now.

Related reading

Routing is one of four things that decide whether inbound converts. The others are response time, a written qualification standard, and whether the team working the leads is coached against it.

Where the routing rules live is a CRM decision, covered in HubSpot vs Salesforce. The measurement side is in improving MQL to SQL conversion, and the case for reporting acceptance rather than lead volume is in GTM for marketing leaders.