This page is for UK businesses whose enquiries arrive from a website form, Google Ads, Facebook lead ads, live chat or WhatsApp, and then sit in an inbox until someone has a spare moment. I set up the automation that catches every enquiry, replies within seconds, decides who should handle it and keeps chasing until a person has made contact.
Lead generation automation does not create demand. Your ads, search visibility and reputation do that. What it fixes is the stretch between someone asking a question and someone answering it, which is where many paid-for enquiries quietly go cold.
What changes when enquiries are handled automatically
The person who filled in the form gets an acknowledgement straight away, on the channel they used, telling them what happens next and when. The right member of staff gets an alert with the details already in front of them, rather than a forwarded email with half the fields missing. If nobody has made contact within the time you set, the system reminds them, then escalates.
You also get a record. Every enquiry lands in one place with its source, the campaign that produced it and what happened to it. That is the information you need to judge which marketing is worth paying for, and a notification email alone never provides it.
Who it suits, and who it does not
It suits service businesses where the first reply decides who wins the job: trades, clinics, solicitors, estate agents, training providers, B2B suppliers and anyone else whose customer is likely to contact two or three firms at once. It suits businesses with more than one person taking enquiries, because shared inboxes are where ownership gets lost. It also suits anyone spending money on ads who cannot say what happened to last month’s leads.
It is not worth building if you receive a handful of enquiries a month and answer each one yourself within the hour. A good phone habit beats an automation there. It is also the wrong starting point if the problem is too few enquiries; that is a job for your ads, landing pages or search visibility first.
What I build
Capture from every source
Website forms, Google Ads lead form assets, Facebook and Instagram lead ads, chat widgets, WhatsApp and booking tools all feed one destination, usually a CRM or, for very small teams, a shared spreadsheet. I connect them with native integrations where they exist and a webhook where they do not. Campaign data travels with each lead, so a form filled in from a tagged ad keeps its UTM parameters instead of arriving as an anonymous email.
An instant, honest first reply
Each enquiry gets a reply written for your business: what you received, who will be in touch and roughly when, plus anything useful in the meantime, such as a booking link or the documents to have ready. Out of hours, it says so rather than pretending someone is at a desk.
Qualification and scoring
A few well-chosen form questions do most of the work. I use the answers to sort enquiries into simple bands, for example ready to book, needs a quote, or outside your area. Where you have enough history to justify it, I add lead scoring based on what your past customers looked like, not on guesses about engagement.
Routing and alerts
Rules decide who owns each enquiry by service, postcode, value or rota, and the owner is alerted by email, SMS, Slack, Teams or a CRM task. This is lead routing, and the important part is the fallback: what happens when the owner is on holiday or the rule matches nobody.
Follow-up until someone answers
If a lead has not been contacted within your agreed window, the owner is reminded and then a manager is told. If the prospect goes quiet after a quote, a short sequence checks in at sensible intervals and stops the moment they reply or book.
Outcomes back to your ads and reports
When a lead becomes a sale, that result can be sent back to Google Ads as an offline conversion and to Meta through the Conversions API, so the bidding learns from customers rather than form fills. I check that the underlying conversion tracking actually records real enquiries before building anything on top of it.
Decisions to make before anything is automated
Automation copies whatever process you already have, faster. Before I build, we agree a few things in writing:
- Who owns a new enquiry, and who covers when they are away.
- How quickly a person must make contact, in working hours and outside them.
- What counts as a qualified lead, in words your team would use.
- Which channel the first human contact uses: phone, email or WhatsApp.
- How long enquiry data is kept, and when it is deleted.
If these answers differ depending on who you ask, that is useful to know. It is usually the real reason leads are being missed.
How a build runs
- Map the current journey. I submit test enquiries through every source and record where each one ends up and how long it takes.
- Agree the rules. The decisions above, plus reply wording and alert recipients, in a short document you sign off.
- Build in your accounts. The CRM, automation platform and messaging tools belong to you, not to me.
- Test with fake leads. Every source, every routing rule, out-of-hours behaviour and the failure alerts.
- Go live and watch. I check the first real enquiries against the source platforms to confirm nothing is dropped. How long this monitoring runs is agreed before work starts.
What breaks, and how I prevent it
A frequent weak point on small business sites is a form that sends a notification email and nothing else. When that inbox fills up or the person leaves, enquiries vanish without anyone noticing. Every build I set up writes the lead to a record first and sends alerts second.
Other regular problems: lead ad submissions that are only ever downloaded by hand, so they wait days; connections that stop silently when a password changes or a form field is renamed; duplicate records when the same person enquires twice; and phone numbers stored in so many formats that SMS alerts fail. I add a daily check that compares lead counts between the source and the CRM, and an alert when an automation errors.
UK GDPR and PECR in the follow-up
Replying to the question someone asked is not the same as marketing to them. Under UK GDPR you need a lawful basis for holding the enquiry, a privacy notice that explains it and a retention period you stick to. Under PECR, promotional emails or texts that go beyond answering the enquiry need consent, or must meet the soft opt-in conditions, which include giving an easy way to opt out when the details are collected and in every message. I keep the service replies and any marketing sequence separate so the rules for each are clear, and I note which tools process the data, because some automation platforms store it outside the UK. This is practical set-up, not legal advice.
What you receive
- A working capture, reply, routing and follow-up system in accounts you own.
- A one-page diagram of how an enquiry moves through it.
- Written notes on every automation: what triggers it, what it does and how to switch it off.
- A test log showing each source and rule was checked.
- A short walkthrough recording for whoever will look after it.
What it costs
The price depends on how many sources need connecting, whether a CRM is already in place and how much of the follow-up runs on messaging channels. Each quote is written after a free first call, in GBP, and agreed in writing before work starts, including any ongoing support. Automation platforms and messaging tools carry their own subscriptions, which you pay directly.
Next step
Send me a list of where your enquiries come from and roughly how many arrive in a typical month. I will tell you where I think leads are slipping and what I would build first. You can book a free 30-minute call, or email contact@sudeshnathapa.com.