AI Lead Routing: How to Get Every Inquiry to the Right Person

Earlier this summer we sat down with a business owner who runs crews across two counties, and he told us about a call that had been bothering him for weeks. Someone phoned the main line about a sizeable job. The person who happened to answer took a message for "the right person," except there were three plausible right people and no rule for choosing between them. The message went into a group chat, everyone assumed someone else had it, and when it finally got checked days later, it held a first name and no phone number. The inquiry did not go to a competitor on price. It went quiet because nobody owned it. This guide is about the system that prevents exactly that: lead routing, the set of rules that decides who owns each inquiry, and what AI adds to it.

What is lead routing, and why does it usually break?

Lead routing is the step between "an inquiry arrived" and "a specific person is working it." In most small businesses that step exists, but it lives in people's heads. The office manager knows Maria handles the north half of the territory, Dave takes the commercial work, and anything unusual goes to the owner. That works right up until the office manager is out, or the inquiry arrives on a channel nobody watches, or two of those unwritten rules point at different people.

The failure mode is rarely dramatic. An inquiry gets forwarded instead of assigned, and a forward carries no deadline. It sits unread in an inbox that belongs to everyone and therefore to no one. Routing breaks not because people stop caring but because the rules were never written down, so the system cannot run without the one person who memorized them.

What routing rules should a small business start with?

You do not need enterprise territory management. Most businesses already route informally on four dimensions, and writing them down is the whole first step:

• By service line. A water heater call goes to plumbing, a panel upgrade goes to electrical, a design inquiry goes to whoever scopes design work. This is the rule most teams apply without naming it.
• By territory. If your crews or salespeople split a coverage area, the inquiry's address or city decides the owner. Territory rules matter most when driving time is part of the cost of every job.
• By value. An inquiry that mentions a full remodel, a portfolio of properties, or a multi-site rollout deserves a senior person on it from the first touch. A rule as simple as "anything that sounds five figures goes to the owner" is a value rule.
• By availability. The best-matched person is a poor owner if they are on vacation or buried for two weeks. Availability rules check the calendar before assigning, which stops the common pattern where the busiest person accumulates the most new leads.

Start with the one dimension that causes the most confusion today. If inquiries stall because nobody knows whose patch they fall in, write the territory rule first. If they stall because everything defaults to the owner, write the service-line rule.

When does round-robin assignment make sense?

Round-robin hands each new lead to the next person in rotation, and it earns its place when leads are genuinely interchangeable: a sales team where anyone can work any inquiry, or an agency where reps cover the same territory and services. It keeps distribution fair, which matters more than it sounds, because uneven lead flow is one of the quiet resentments inside sales teams.

The caveat is that round-robin is a fallback, not a strategy. It answers "who is next?" rather than "who fits?". A sensible setup applies the fit rules first, service, territory, value, and only round-robins within the group that qualifies. Pure rotation across a team with different specialties sends the panel upgrade to the drainage specialist once a week, and everyone learns to trade leads informally, which puts you back where you started.

What should happen when nobody responds?

This is the rule most routing setups skip, and it is the one that would have saved the two-county owner's inquiry. Assignment without a deadline is a suggestion. An escalation rule adds the deadline: if the assigned owner has not made contact within, say, 30 minutes during business hours, the lead moves to a named second owner, and if it stalls again, it lands with a manager or the owner of the business.

Escalation is not an accusation. The assigned person is usually mid-job, on a roof, or in a showing, and the research says that is the normal state: Salesforce's State of Sales research, drawn from surveys of thousands of sales professionals, found reps spend less than 30% of their time actually selling, with the rest going to admin, meetings, and coordination. A routing system that assumes the first owner is always free is designed around a person who does not exist. A good one assumes the opposite and plans the second and third hop in advance.

How is AI routing different from the assignment rules in my CRM?

Most CRMs can assign leads off a form field: if the dropdown says "Plumbing," send it to the plumbing queue. That works exactly as far as your forms are structured, which is not far, because real inquiries arrive as free text, voicemail transcripts, and emails that never touched a dropdown.

AI routing reads the inquiry the way a person would. "Our water heater went out and we're up in Fullerton" contains a service line and a territory, and an AI agent extracts both, checks them against your rules, and writes the result into the CRM as structured fields rather than a note someone has to interpret. It can also read signals a form never captures: urgency in the phrasing, a mention of multiple properties, a returning customer's name. The routing decision is still your rules; the AI's job is to apply them to unstructured input, at any hour, and to log why it chose the owner it chose. Our guide to keeping CRM records accurate automatically covers the record-keeping half of that loop, and the CRM automation service is where we build both halves together.

One boundary worth naming: routing decides who owns the inquiry, not how fast the first reply goes out. The first-reply problem is its own system, and we build it as the speed-to-lead responder. The two pair naturally, an instant first reply buys time, and routing decides who continues the conversation, but they fail independently, and plenty of businesses have a fast autoreply feeding a routing gap.

How do I know if routing is my actual problem?

Pull your last twenty inquiries and answer two questions for each: who owned it, and when was that decided? If the honest answer to the first is "whoever picked it up" or the answer to the second is "at the morning meeting," routing is a real gap. Other tells: inquiries that get re-forwarded more than once, group-chat messages that start with "did anyone call this guy back," and any inquiry whose contact details exist only in a voicemail. The fix does not start with software. It starts with writing down the rules you already half-follow, then giving a system the job of applying them every time.

FAQ

What is AI lead routing?

AI lead routing is software that reads each incoming inquiry, identifies the service, location, and likely value from the text itself, and assigns an owner under rules you define. Unlike form-based CRM assignment, it handles unstructured inquiries such as voicemails and emails, and it escalates automatically when the assigned owner does not respond.

Do I need a CRM before setting up lead routing?

A CRM helps but is not a prerequisite. Routing needs three things: a written set of rules, a place to record who owns each inquiry, and a notification channel your team actually checks. Plenty of first versions run on a shared pipeline board. That said, a CRM is where routing pays off long-term, because the assignment history shows which rules work.

How fast should the escalation timer be?

Match it to how your customers buy. For urgent home services, 15 to 30 minutes during business hours is reasonable, because the caller is often working down a list. For considered purchases, a few hours can be fine. The exact number matters less than having one, since an escalation rule with a generous timer still beats an assignment with no deadline.