How to route leads to the right person

Decide the routing rules explicitly

Write down what determines who handles an enquiry. Common rules, in rough order of usefulness:

By service. Different work needs different knowledge, and the wrong person quoting badly costs more than a delay.

By geography. For a business spanning Greater Houston, routing by area to the person or crew covering it avoids promises nobody can keep.

By value or complexity. Large or complex jobs to whoever handles those well.

By availability. Round-robin or first-available among people who can all handle the work.

By existing relationship. A returning customer goes back to whoever they dealt with, which matters more than any efficiency gain.

Pick the primary rule and make the others secondary. Trying to apply four rules at once produces ambiguity, and ambiguity is what leaves enquiries unclaimed.

Make ownership unambiguous

Every enquiry needs one named owner from the moment it arrives. A shared inbox where everyone can see everything and nobody owns anything is the most common cause of slow response.

Set it up so that:

• One person is assigned immediately, automatically where possible
• The assignment is visible to everyone
• Unclaimed or unanswered enquiries escalate after a set time
• Someone owns the enquiries that fit no rule

That last one matters. Every routing scheme has edge cases, and they are precisely the enquiries that disappear.

Set a response clock

Routing is pointless if the recipient is slow. Define the standard — an hour during working hours is achievable for most local businesses — and make missing it visible rather than silent.

Escalation should be automatic: if an enquiry is not acknowledged within the window, it reassigns or alerts someone else. This is a small piece of configuration and it prevents most lost enquiries.

Route by channel as well

Different channels carry different urgency:

• Phone calls are immediate by definition
• Emergency form submissions need the same treatment as calls
• Routine enquiries can follow the normal queue
• Existing-customer questions should not sit behind new business

A single queue treating all of these identically delays the urgent ones.

Capture enough to route correctly

Bad routing usually comes from insufficient information. The enquiry form or the intake question should establish service type and location, because those are what most rules depend on.

If the form asks nothing, everything routes to one person who then re-routes manually, which adds a delay to every enquiry.

Handle the geography honestly

Greater Houston is large enough that routing to whoever is nominally free is not the same as routing to whoever can actually attend. A crew on the far side of the metro is not available in any practical sense.

Route by who can realistically get there, and be straightforward with the customer about timing rather than assigning optimistically and rescheduling later.

Then measure it

Track time to first response by owner, by channel and by service. The pattern shows whether the problem is the routing rules, a particular person's workload, or a channel nobody is watching. Without those three cuts of the data, routing problems get blamed on individuals when they are usually structural.