AI lead follow-up for service businesses
Find where enquiries stall before you add a tool. A worksheet, a worked example, and checks you can use with your team.
First, find the gap
AI lead follow-up can help a business read a new enquiry, reply with the right details, and give the team a clear next step. But the right fix depends on where the lead gets stuck.
If few people enquire, look at who visits the site, what you offer, and whether the form works. If enquiries arrive but go quiet, trace what happens after they come in. This guide covers that second problem.
Start with a manageable set of recent enquiries in your own approved business tools. Include some that went well and some that stalled. A small sample can uncover faults. It cannot tell you how often those faults occur across all your leads.
What counts as a useful reply?
A receipt says, “We got your message.” A useful reply answers the request, asks for a detail needed to move it on, or gives a confirmed next step. An alert sent only to your team is not a reply to the customer.
A useful reply can come from a person or a system. Record which. Measure the wait from when the enquiry arrived to when that reply was sent. Keep any receipt message in its own column.
Use this follow-up worksheet
Make one row per enquiry in a sheet your business has approved for these records. Use a reference code instead of names or message text. Keep the sheet in your own tools; there is nothing to upload here.
| Field | What goes here |
|---|---|
| Reference and source | Your own reference code, plus where it arrived, such as the website form or email. |
| Arrival | Date, time and time zone. Use the same time zone for the reply. |
| Receipt | Time of any receipt message. Keep this apart from a useful reply. |
| First useful reply | Time sent, what step it enabled, and whether a person or a system sent it. |
| Owner | The role or person who was due to act next. |
| Next step and due time | The agreed action and when it was due. Was it done? |
| Outcome | Still open, booked, quoted, won, lost, or not a fit. Record the date checked. |
| Exception | A repeat enquiry, missing detail, failed tool, or other reason the normal path did not work. |
Use “unknown” when the record is missing. Use “none” only when you have checked and found no reply or action. Do not turn a gap in your records into a claim that no one replied.
A lead that waited overnight
The next check is who owned the lead overnight. If no one was assigned, fix that gap first. If the team always needs an address, a system may be able to ask for it sooner. It must not make up a price or promise a visit.
This example does not show that a quicker reply would have won the job. You would need later records to judge that.
Choose the fix that fits the gap
- No clear owner: name one and agree how someone else takes over when they are away.
- The same detail is often missing: improve the form or ask one clear follow-up question.
- The same next step is often late: use a rule, task or reminder in the tools you already have.
- Requests vary in how they are written: AI may help read them and prepare or send a reply within rules you have approved.
- A quote sits without a next step: agree who follows up and when to stop. A fast first reply alone will not fix this.
A CRM holds the lead record. A workflow moves work between steps. AI can help with a task inside that workflow. You may need a clearer process, a simple rule, or a fuller build. They solve different gaps.
Kata's website enquiry reply service covers the first response: an email from your own address based on the request and your rules, with your team able to take over. The wider checks in this guide are not a promise that one setup covers every sales step.
Test the awkward cases
Before a system sends real messages, test with made-up leads. Check a repeat form, missing contact details, a job outside your scope, unclear pricing, an absent owner, and a tool that is down.
Agree which messages can go out on their own, which need review, and who gets an alert when the process fails. Test a request to stop follow-up. Make sure a person can take over with enough context to help.
Measure what changed
Save a starting period before making the change. Then compare a later period using the same rules. Keep these measures apart:
- How long leads wait for a useful reply, including the slow cases.
- How many leads have an owner and a completed next step.
- How many reach a booking or quote.
- How many turn into signed work, once enough time has passed.
Record counts as well as rates. Note changes in ads, price, season and lead quality. A faster reply is a process result; it is not, by itself, proof of more sales.
We use the same before-and-after discipline in Kata's own search visibility experiment. That record starts with what we could measure and what was still unknown.