Lead Routing & Assignment, end to end

The rule types, and what each is good for

Territory routing sends leads by geography, a state, a city, a cluster of districts. It works when the sale is genuinely local: site visits, regional relationships, language. It fails when applied to a product sold identically everywhere, where it adds a constraint with no benefit.

Industry or segment routing sends leads by what the buyer does. This is usually the highest-value rule, because sector fluency compounds: a rep who has sold to twelve manufacturing firms handles the thirteenth conversation better than a generalist. Where a team has real specialisation, routing on it beats routing on anything else.

Source routing separates channels that behave differently. Enquiries from a marketplace, a paid form and an inbound referral arrive with different intent and different junk rates, and often deserve different reps or a different first response.

Deal-size routing sends larger opportunities to more experienced closers. It is easy to over-apply, value at entry is often a guess, and routing on a guessed number sends good leads to the wrong desk with confidence.

Round-robin distributes evenly across available reps. It is the correct default when no other signal separates the leads, and the wrong primary strategy when several do. Even distribution and correct distribution are not the same objective.

The fallback rule is the one that matters

Most routing setups are built by listing the clean cases: this sector goes here, that city goes there, big deals go to the senior closer. The leads that break the setup are the ones with a missing field, an unrecognised sector, or a city nobody added to the map, and those are disproportionately the messy, high-intent enquiries that arrived through an unusual path.

So the rule that decides what happens to everything unmatched carries the most weight. A fallback that routes to a named manager, with a time limit, is enough. A fallback that routes to a shared pool is only enough if somebody owns clearing that pool on a schedule, which in practice means naming a person rather than a team.

The metric worth watching is age, not volume: how long the oldest unowned lead has been sitting is the cleanest single indicator of whether routing is covering the pipeline at all.

Where Leadkaun stops, plainly

Leadkaun does not do rules-based routing, and this guide would be dishonest if it implied otherwise. There is no rule engine, no territory model, no round-robin distribution and no automatic assignment on import. Assignment is manual: an admin or manager opens a lead and assigns it to a named rep, one at a time. Leads that arrive through CSV import or the Google Sheets connection land unassigned until someone gives them an owner.

If automatic routing is a hard requirement for your team, a large floor, high daily volume, a real territory structure, that requirement belongs to your CRM, and the buyer guide below ranks the tools that do it well. We are not one of them, and pretending otherwise would waste your evaluation time.

What Leadkaun does is the layer after ownership. Every lead is graded A–F across Fit, Intent and Quality the moment it lands, regardless of who owns it. Once a lead has an owner it takes a position in that rep's Priority Queue, re-ranking as signals arrive and sinking as intent decays. That is a different problem from routing, and most teams find it is the one actually costing them deals: not that the lead went to the wrong rep, but that the right rep never got to it in time.

The two are complementary rather than competing. A team can run CRM-side routing rules for ownership and Leadkaun for what to do with the leads once owned, and that is the configuration we see most often.

Handling leave, exits and reassignment

Routing rules are written for a stable team and immediately meet an unstable one. Someone is on leave, someone leaves the company, someone moves territory. The rules that matter here are not about new leads but about existing ones: what happens to forty open leads when their owner stops working them.

The requirement is that a transfer carries history. A reassigned lead should arrive with its grade, its logged conversations and its follow-up record intact, so the new owner starts from context rather than from scratch. A transfer that resets a lead to a blank record is not a transfer. It is a new lead with an old phone number, and the receiving rep treats it accordingly.

For temporary absence, pausing new work is better than reassigning open work. Churning ownership costs more in lost context than it saves in coverage.

Setting routing up without over-engineering it

Start with one rule and a fallback. For most Indian B2B teams that means routing on sector where specialisation genuinely exists, even distribution for everything else, and a named manager on the fallback. That configuration covers the majority of leads correctly and, more importantly, covers all of them.

Then measure two numbers for a fortnight: the age of the oldest unowned lead, and the share of leads whose first contact happened on the day they arrived. Both are direct readouts of whether ownership is working, and both move before anything appears in conversion data.

Add complexity only where those numbers say it is needed. Routing setups accrete rules that made sense once, and every additional rule increases the surface where a lead can fall between two conditions. The setups that survive a year are usually simpler than the ones drawn on the whiteboard.