It is 6pm on a Tuesday, an enquiry lands, and with no lead routing rules in place both owners assume the other will ring back. Nobody does, and the customer books your competitor. We get asked about lead routing on every audit call. It sits inside our wider CRM guide for UK trades.
How to set up your routing rules this week
The fix is rarely complicated. Here is the sequence:
- Pick a model: round-robin shares leads evenly, skills-based sends each job to the owner who fits.
- Set a priority order so no lead lands in two inboxes.
- Add a fallback timer: if the first owner has not opened a lead in two minutes, it moves on. That is how firms that answer inside a minute win.
- Route by availability, so anyone on a job or away drops out of the rotation.
- Measure call-backs and booked jobs over 30 days against the old way.
Where routing rules quietly go wrong
Three patterns show up again and again.
- Routing everything at once. Start with one source, get it clean, then add the rest; the response-time numbers UK small businesses see reward tight sources.
- Leaving the thinking to the software. A CRM follows the rules you give it; decide who owns which jobs yourself.
- Forgetting the customer. If a rule sends an emergency to the owner two hours away, tear it up.
What to do next
You are already ahead of most owners who never write a rule down. Go deeper with the full lead management guide, or get it built: our CRM software handles routing and follow-up in one place.
What the data says
We work on lead routing every week with UK plumbers, dentists, accountants and aesthetic clinics. Round-robin keeps it fair, skills-based keeps it fast. Get it right and the phone rings; get it wrong and you fund your competitor's ads. We pair routing with automated appointment reminders.
Both the UK Equality Act 2010 and Schema.org publish UK-applicable research that confirms the pattern; skim them for the numbers, or see the trade sites behind them in our recent work.
Related cluster posts
From the same pillar — these dig into adjacent subtopics:
