Every lead that arrives without an owner is a small bet that someone will notice it. Sometimes they do. More often it sits in a shared queue while two reps each assume the other has it. Lead routing is the workflow that removes that bet: it decides who owns a new lead at the moment it is created, without a human in the loop.

Start with the Question, Not the Tool

Most CRMs can route leads. The harder question is what you want routing to optimize. Fairness among reps? Matching leads to the person with the right expertise? Speed of first response? Keeping accounts with whoever already knows them? These goals pull in different directions, and a rule set that tries to honor all of them equally becomes unreadable.

Write one sentence: “A new lead should go to ___ because ___.” If you cannot finish it, stop and decide before building anything.

The Common Approaches

Round robin hands leads to reps in turn. It is simple and feels fair, and it works well when leads are roughly interchangeable and the team is similar in skill and capacity. It falls apart when reps are on holiday, when leads differ in size, or when someone is already overloaded.

Territory-based routing assigns by geography, industry, company size or language. It suits teams where context matters, since the rep who knows a region or sector can respond with more relevance. The cost is maintenance: territories change, reps leave, and a poorly defined boundary produces leads that fit two territories or none.

Weighted or capacity-based routing gives some reps a larger share, for example because they are senior, part-time or still ramping up. It is useful, but the weights need a named owner who reviews them regularly, or they go stale.

Account-based routing sends a lead to the existing owner of the matching company. This is almost always worth layering on top of the others, because nothing irritates a customer like three people from the same vendor reaching out within a week.

Compare Before You Choose

Approach	Best when	Watch out for
Round robin	Leads are similar, team is balanced	Absent reps, uneven lead value
Territory	Expertise or region matters	Overlaps, gaps, outdated boundaries
Weighted	Capacity differs across the team	Weights that are never revisited
Account-based	Existing customers or open deals	Matching on messy company names

Most real setups combine two. A typical order is: check for an existing account owner first, then apply territory, then fall back to round robin among whoever is available.

Order of Rules Matters

Routing rules are evaluated in sequence, and the first match usually wins. Put the most specific rules at the top and the broadest at the bottom. Then, importantly, add a final catch-all rule that assigns to a named person or queue when nothing else matches. Without it, a lead with an unexpected country value or a blank field falls through and sits owned by nobody, which is the exact problem you set out to solve.

Also decide what should happen when a rep is unavailable. Some platforms let you mark users inactive or out of office so they are skipped. Check your vendor’s current documentation for how this works rather than assuming.

Protect the Inputs

Routing is only as reliable as the fields it reads. If territory depends on the “Country” field and your web form lets people type anything, you will route on typos. Convert routing fields to picklists wherever you can, and decide in advance how to handle blanks. For company-based matching, use website domain rather than company name.

Add a Safety Net for Speed

Assignment is not the same as action. Add a follow-up rule: if a lead has had no logged activity within an agreed window, notify the owner and then their manager, or reassign it. Set that window based on what your sales process realistically demands, and avoid so many escalation steps that the notifications become wallpaper.

A Hypothetical Example

A small software reseller has four reps, two of whom cover distinct regions and two who handle everything else. The admin builds rules in this order. First, if the lead’s email domain matches an existing account, assign to that account owner. Second, if the country is in region A or B, assign to the matching regional rep. Third, everything else goes round robin between the other two. Finally, a catch-all assigns to the sales manager with a task to triage. In the first week, the manager’s queue catches several leads with a blank country, which reveals that one form did not mark that field as required. The fix takes five minutes and the catch-all did its job.

Test with Real Records

Before turning routing on, create a handful of test leads that exercise each branch: an existing customer’s domain, a territory match, a blank field, a duplicate email. Run them through and confirm the owner each time. Keep these test cases in a short document so you can rerun them whenever rules change. Mark test records clearly so they do not reach real reps or reports.

Review It on a Schedule

Routing quietly rots. People change roles, territories shift, and new lead sources appear. Put a quarterly check on the admin calendar: who is receiving leads, who is not, and how many leads hit the catch-all. A growing catch-all count tells you a rule has stopped matching reality.

Frequently Asked Questions

Should managers assign leads manually instead? Manual assignment works at very low volume. As soon as leads arrive outside working hours or in bursts, delay creeps in. Automated rules with a manual override for exceptions is the usual balance.

How do we handle leads that match two territories? Define a tiebreaker in advance, such as company headquarters location or the larger of the two regions, and document it so reps are not left arguing about it.

What about leads from existing customers? Route them to the account owner first. If the owner is unavailable, notify them and a backup rather than assigning the lead to someone unfamiliar with the relationship.

Can we change owners after assignment? Yes, and you should allow it with a reason. Just keep a record of the change, so you can spot patterns of rules that routinely get overridden.

How often should rules be reviewed? At least quarterly, and immediately after any team change or new lead source goes live.

Next Step

List the rules your team follows informally today, such as “Priya takes the northern accounts”. Write them in order, add a catch-all at the bottom, and you have your first routing draft.