Lead routing without a CRM

An enquiry with no owner sits. Not because anyone decided to ignore it, but because three people saw it, each assumed one of the others had it, and by the time somebody checked it was two days old.

That is a routing failure, and it is the most common one in small businesses. It is also entirely solvable without buying anything.

The CRM sales pitch conflates two different things: the mechanism for assigning an enquiry, and the system for managing a pipeline. The first is genuinely simple. The second may be worth paying for, later, for different reasons.

It is worth solving the first on its own before concluding you need the second. Plenty of businesses buy a CRM to fix a routing problem, discover that the routing problem is still there because nobody configured the assignment, and now have a subscription as well.

The cheapest routing happens before any logic runs, by having different enquiries arrive in different places.

A support form and a sales form can deliver to different sheets, or different tabs, or different destinations entirely. No rules, no assignment step, no ambiguity about ownership: the destination is the routing.

This works whenever the distinction is obvious from context, which it usually is. The form on the careers page and the form on the pricing page are not the same enquiry and do not need to share a queue.

It also degrades well. If nobody maintains it, enquiries still land in a sensible place, which is not true of a rule engine that has drifted.

Where one form must serve several purposes, a single short dropdown does the routing work. What is this about, with four or five options that map to owners.

The important design constraint is that the options should reflect who handles the enquiry rather than how you describe your services. A visitor cannot know your org chart, but they can tell you whether they are an existing customer.

Keep the list to the distinctions that actually change the owner. Every additional option is one more chance for a visitor to guess wrong, and a wrong routing is worse than no routing because it creates false confidence.

This is one of the few form fields that clearly earns its place, because it changes what happens next.

Distributing enquiries evenly between people sounds fair and is frequently the wrong model for a small team.

It optimises for balanced workload, which matters when everyone is interchangeable and the constraint is capacity. In a small business people are not interchangeable, and the constraint is usually knowledge rather than time.

Routing by subject gets a better answer faster. Routing by availability gets an answer faster but sometimes worse. Routing by rotation gets neither reliably.

The place rotation earns its keep is a genuinely undifferentiated queue where any of several people could handle anything, which is rarer than the software assumes.

Whatever the mechanism, the output should be a single visible column in the sheet saying who owns each enquiry.

It sounds trivial and it is the whole point. An unowned row is visibly unowned, a filter shows everyone their own list, and the question of who is dealing with this has a written answer rather than a social one.

Add a status column beside it with a small vocabulary: new, replied, waiting, closed. Between the two, you have most of what a small business actually uses a CRM for.

Both belong in the same sheet as the enquiry, because a status kept somewhere else stops being updated within about a fortnight.

If everybody receives every notification, nobody is alerted, because a message sent to everyone is addressed to no one.

Sending different forms to different addresses, or filtering by the routing field, means the person who should act is the person who is told. That single change usually does more for response time than any amount of exhortation.

Keep a shared copy somewhere for visibility, but make the actionable alert specific.

And remember that notifications are not a reliable transport, so the sheet remains the record and the alert is a convenience layered on top.

Some enquiries will land with the wrong person, because the visitor guessed or the categories did not fit.

The rule that matters is that reassignment must be trivial and explicit: change the owner column, say so in a note, done. What kills a routing system is silent handoff, where somebody assumes somebody else has picked it up. That is the same failure as an unowned enquiry, arriving later in the process under a different name, and it stays invisible until a customer chases.

It is also worth watching how often it happens. A high misroute rate is telling you the options on the form do not match how enquiries actually arrive, which is a ten-minute fix to a dropdown.

Treat the misroute rate as a metric rather than an annoyance and the routing improves on its own.

Routing to a person is fragile in exactly one predictable way, which is that people are sometimes away.

The lightweight answer is a named fallback for each route rather than an availability system. If the owner column can hold a second name, it is enough. If not, a note in the sheet saying who covers whom is enough.

What does not work is routing to an individual with no fallback and hoping. That is how an enquiry sits for a fortnight during somebody's holiday, and it is one of the largest contributors to the slow tail.

Check the unowned and unreplied rows weekly. It takes a minute and catches everything this section describes.

There are real thresholds, and they are not about lead volume.

You need one when the relationship has a history worth keeping, when several people work the same account and need to see each other's activity, when the pipeline has stages that require reporting, or when compliance requires an audit trail of contact.

None of those are routing. Routing is a field, an owner column and a filter, and a business that has not solved routing will not have it solved by buying software.

The graduation decision is worth making on its own merits, when the spreadsheet is failing at something specific rather than because it feels unprofessional.

Different forms to different destinations wherever the distinction is obvious. One short routing dropdown where a single form must serve several purposes. An owner column and a status column in the sheet. Notifications addressed to the person who should act. A named fallback per route. A weekly glance at what is unowned.

That covers the routing needs of most businesses under a few hundred enquiries a month, costs nothing, and fails visibly rather than silently, which is the property that matters most.

The visible-failure point deserves the emphasis. A routing rule inside a tool that nobody opens can be wrong for months. An empty owner cell in a sheet somebody looks at daily is noticed the same week, and that difference is worth more than any amount of routing sophistication.

Do I need routing rules at all?

Should I use separate forms or one form with a dropdown?

Is round robin assignment worth setting up?

What happens when the owner is on holiday?

How do I stop enquiries falling between people?

What if the visitor picks the wrong category?

When should I actually buy a CRM?

Can I automate assignment from the routing field?