What is lead routing?

Lead routing
Lead routing is the rule that decides which salesperson or team receives a new inquiry, applied automatically as the inquiry arrives rather than when someone gets around to looking.

What lead routing means in practice

Territory, product, size and rotation are the four rules almost everyone uses, alone or stacked.

Speed matters more than the rule. Research on response times keeps finding the same shape: an inquiry answered within minutes converts far better than the same inquiry answered the next day.

Phone inquiries are where routing quietly fails. A web form lands in a system that applies rules; a missed call lands nowhere, and no rule ever runs on it.

That gap is usually the biggest one in a small company's sales process, and it is invisible because nothing is recorded to look at.

What people get wrong

A roof leak, from ring to callback in 12 minutes

Say a roofing company has three estimators split by ZIP code. At 12:40 on a Tuesday, with the office at lunch, a homeowner calls about a leak around a skylight.

In the old setup, that call rings out. She leaves no message, and no record of her exists anywhere except the phone log.

In the routed version, the call gets answered and her name, number and the problem are captured as text. The record lands in the company's CRM at 12:44. A rule reads the ZIP, assigns it to the estimator for the east side, and texts him the summary. He calls back at 12:52 from the truck and books a Thursday inspection.

Nothing clever happened there: the phone call became a record fast enough for the same rules that handle web forms to run on it. Whether that record reaches your CRM directly or through Zapier depends on which CRM you use, so check the integration matrix first.

Audit your last twenty phone leads

You can test your own routing in half an hour. Take the last twenty phone calls from new customers and answer three questions for each. Who owned it? How long until the first callback? What happened in the end?

The owner column is usually the revealing one. Web leads will each have a name beside them. Phone leads often have a blank, or whoever happened to pick up, which isn't a rule.

Two cases need a decision before they come up. Repeat callers should go back to the person already working with them, even if the rotation says otherwise. Nothing annoys a buyer like starting over. Ties need a default, so a ZIP on the border has one named owner.

Set a time limit too. If the assigned person hasn't called back within an hour, the lead should move to someone else. A lead sitting untouched with a name on it is worse than one with no owner, because everyone assumes it's handled.

How GreetKeeper handles it

Every call GreetKeeper answers produces a record with the caller's name, number and reason, so a phone inquiry becomes something a rule can act on.

You can push that into your own system. The integration matrix states what writes natively and what goes through Zapier, because that difference matters here.

Qualifying questions run during the call, so the inquiry arrives already sorted rather than as a note saying somebody rang.

Lead routing questions

What is the fastest sensible response time?

Minutes rather than hours. The gap between five minutes and an hour is larger than most teams believe, and the phone is where it is easiest to win.

Should phone leads go to the same rotation as web leads?

Usually yes, for fairness. What matters more is that they enter the same list at all, rather than living in a call log nobody reads.

Can an inquiry be routed on what the caller said?

Yes, when the reason is captured as text. That is the practical advantage of a transcript over a call record with a duration on it.

Hear it take one of your calls

Two minutes, your own scenario, no card.