How to Route Website Leads to the Right Person

A commercial grounds maintenance firm has four people who handle new enquiries. A contract tender comes in through the website on a Friday afternoon. By Monday nobody has replied, because each of the four assumed one of the other three had picked it up. The lead was not lost to a competitor or to price. It was lost to routing, or rather the absence of any.

Routing is a decision you make once, not per lead

Lead routing answers one question: when a new enquiry arrives, whose is it? Answered well, that answer is automatic and immediate. Answered badly, it becomes a small negotiation every single time, and negotiations eat the hours a fresh lead does not have. What you want is a rule simple enough that it never needs discussing and fair enough that nobody tries to game it.

A shared inbox is not a routing method

Sending every enquiry to a group address feels like routing because everyone can see it. In practice it is the lack of routing. Responsibility is spread across the whole group, so the confident people take the promising leads and the awkward ones are left. Nothing records who is dealing with what, two people occasionally ring the same lead within an hour of each other, and when something is missed there is nobody to ask about it. A group inbox can be a holding area at most, and a lead has to leave it with one name attached within minutes.

The three common ways to assign a lead

By hand

A manager or a coordinator looks at each new lead and gives it to someone. This is the most flexible option, because the person routing can weigh up who is free, who knows the sector and who is having a quiet week. It struggles on volume and on cover: if the coordinator is in a meeting or on holiday, the leads queue behind them. It suits a low number of high-value leads, where a couple of minutes of thought per lead is clearly worth spending.

First come, first served

Leads go to a shared list and reps claim the ones they want. It rewards being quick, which sounds healthy, but it also rewards whoever has time to sit watching the list and penalises the ones actually on the phone with customers. Over a few months it tends to concentrate leads on one or two people and to breed resentment in the rest. It works as a fallback for leads nobody has claimed, not as the main method.

Round-robin

The system deals new leads out one at a time across the active team, the way you deal cards. Everyone gets an even share, the assignment is instant, and there is no doubt about whose lead it is. The trade-off is that it is blind: it has no idea that the seventh lead is a major tender that ought to go to your most experienced estimator. You deal with that through reassignment, not by giving up on the rotation.

Why not route by rules

The obvious next step looks like rules: leads from the north go to one person, leads mentioning irrigation go to another, leads over a certain size go to the senior estimator. Rule-based routing carries a cost that is easy to underrate. The rules need updating every time someone joins, leaves or changes patch. They grow gaps, a lead that matches nothing, and overlaps, a lead that matches three rules at once. And they are hard to see into: when a lead goes to the wrong person, finding out why means reading through the whole rule set. For most teams under about ten people, an even rotation plus quick manual reassignment reaches the same result with none of the upkeep.

Reassignment for specialists

Round-robin gets the lead to somebody fast. Reassignment gets it to the right somebody. The pattern that works: the lead is assigned automatically on arrival so it is never without an owner, the owner reads it within a few minutes, and if it needs a specialist they hand it over on the spot with a note saying why. The first owner stays responsible until the handover is accepted, so nothing falls into the gap between them. Keep the reassignment quick and informal; if it takes a form and a manager's sign-off, people will simply hang on to leads they should be passing along.

After hours and weekends

A lead that arrives at eight on a Friday evening will not get a real response until Monday at most small firms, and that is acceptable as long as it is handled the moment Monday starts. What is not acceptable is that lead being invisible until somebody trips over it. Two things prevent that: the lead is assigned on arrival whatever the hour, so it is already in someone's list first thing, and there is a fallback owner, often an administrator or the team lead, who catches anything the rotation cannot place. The Monday routine is then straightforward: the fallback owner clears the weekend's unassigned and overdue lists before touching anything else.

Check the routing is actually working

A routing method can look fine on paper and still leak. Once a month, check three things: the spread of new leads across the team, which a round-robin should keep close to even, so a large skew means somebody is inactive in the system or leads are being reassigned heavily; the number of leads that sat unassigned for more than a few minutes; and the time from assignment to first contact for each person. If leads are even but one person's first contact is always slow, that is a workload conversation. If the leads themselves are lumpy, the rotation setup needs a look.

A routing setup that holds

1. New web leads are assigned automatically the moment they are captured, on an even rotation across whoever is active
2. The new owner is told straight away, rather than left to discover the lead
3. Anything the system cannot place falls back to one named person
4. The owner can reassign in seconds, with a note, when a lead needs a specialist
5. Someone owns the unassigned and overdue lists and clears them daily, first thing after a weekend

That is enough structure for almost any small team. It is quick, it is fair, and it does not need a rules engine or a full-time administrator to keep it upright.