Short answer: Decide the routing rule before the lead arrives, name one owner per lead, and send the notification somewhere a human will see it within minutes. Most routing failures are not complicated logic problems. They are enquiries landing in a shared inbox where everyone assumes someone else has it.
Routing sounds like an enterprise concern. It is not. A two-person business has a routing problem the moment one of them is on a ladder and the other is on the phone. The question "who is dealing with this one?" is a routing question, and if the answer is ambiguous the lead waits.
The three routing models that cover almost everything
Single owner. One person handles all enquiries. Simple, reliable, and it fails the moment that person is ill or busy. Fine for very small teams as long as there is a named backup and the backup knows they are the backup.
Round robin. Leads alternate between people. Fair, easy to explain, and blind to specialisation. Works when everyone can handle everything.
Rule-based. Route by what the enquiry contains: service type, location, value band, language, urgency. More work to set up, much better fit when your team has genuine specialisms.
Most small businesses should start with single owner plus a documented backup, and move to rules only when they can point at real leads that went to the wrong person.
Write the rules in plain language first
Before touching any software, write the rules as sentences a new hire could follow:
- Anything mentioning commercial premises goes to Sam.
- Anything outside our three postcode areas gets the polite decline and a referral.
- Anything marked urgent goes to whoever is on call today, by phone, not email.
- Everything else goes to the shared queue and the first person free claims it.
If you cannot write your rules like that, they are too complicated to survive a busy Tuesday. Complexity in routing does not fail loudly. It fails silently, by leaving one branch of the logic with no owner.
Capture the routing signal at the source
Routing depends on knowing something about the enquiry, which means the capture step has to collect it. This is where routing and qualification meet. If you route by service type but your form has one box marked Message, somebody has to read every message and route by hand, which is the thing you were trying to avoid.
Ask the one or two questions that drive your rules, and no more. A chat conversation is a good place for this because the question can be phrased naturally rather than as a dropdown. Clerkzo captures leads conversationally or through an in-chat form with custom fields, so the routing signal arrives attached to the lead record rather than buried in free text.
Send notifications where humans actually are
Routing to the right person is meaningless if the message lands somewhere they check twice a day. This is the most common breakdown, and it is entirely fixable.
Clerkzo can notify by email, by webhook, or through Telegram. The webhook option matters more than it sounds: it lets a lead trigger whatever your team already lives in, whether that is a project tool, a CRM, or an internal alert channel. The Telegram route matters for the field teams who will never open a dashboard but always have a phone.
Two rules for notifications. First, one notification per lead with one clear owner named, because a message sent to five people is a message owned by nobody. Second, escalate on silence. If nothing changes state within a set window, ping again or reassign. Silence is not agreement, it is usually somebody driving.
Make ownership visible
Every lead should have a state and a name attached to it. In the Clerkzo leads inbox, records move through New, Contacted, Qualified, and Won or Lost, with notes and search on top. The pipeline is the routing audit trail: if something sits in New for two days, the routing failed and you can see exactly where.
Without visible state you get the shared-inbox failure mode, where an enquiry is read by three people, actioned by none, and eventually falls off the first screen. We wrote about that specific gap in why you lose leads between website and inbox, because it is astonishingly common and almost invisible from the inside.
Handle the edge cases deliberately
Three cases break most routing setups, so decide on them in advance:
Out of scope. Someone wants a service you do not offer. Route it to a template reply with a referral. It costs nothing and it generates a surprising amount of reciprocal work over time.
Out of hours. Nobody is on shift. The enquiry should still be captured, acknowledged with an honest expectation, and queued for the morning with priority. That is the practical purpose of after-hours answering: not pretending to be open, but making sure the lead survives the night.
Ambiguous. The enquiry could go to two people. Default to one of them rather than leaving it unassigned. A slightly wrong owner reassigns in thirty seconds. No owner waits indefinitely.
Escalation and handoff
Some conversations should stop being automated immediately. A complaint, a legal question, a visitor who says outright that they want a person. Clerkzo has a human handoff path plus guardrails so the assistant declines rather than improvises when it is out of its depth.
Treat handoff as a routing rule of its own. Decide who receives handoffs, how fast they are expected to respond, and what happens if they do not. An unanswered handoff is worse than no handoff, because the visitor was explicitly promised a person.
Frequently asked questions
Do I need routing software for a two-person business?
No. You need a written rule, a named owner per lead, and notifications that reach a phone. Software helps when volume or specialisation grows.
What is the fastest routing improvement?
Stop routing to a shared inbox. Name one owner per lead. That single change fixes most of the delay, and speed matters more than people think, as covered in speed to lead.
Should routing be automatic or manual?
Automatic for the obvious cases, manual for the ambiguous ones, and always with a human able to reassign. Fully automatic routing with no override tends to strand exactly the leads that were worth the most.
How do I know if routing is working?
Look at how long leads sit in New. If that number is creeping up, the routing rule or the notification path has broken.