Guides · AI, CRM and follow-up
What should a service business automate first with AI?
Automate the first reply to a new enquiry. It is the step most service businesses are slowest at, and it is the one where speed changes the outcome most. Follow-up on quiet leads and booking reminders come next. Quoting, pricing and anything with an upset customer stay with a person.
AI automation means software that handles a repeating task in your business, such as replying to an enquiry, asking your usual questions or updating your CRM, without someone typing each message. This guide ranks the jobs worth automating in the order we would do them, and says which ones are not worth the effort. If you want the full service, see our AI automation page.
What is the first thing to automate?
The first reply to a new enquiry. Someone fills in a form, sends a Messenger message or texts a number at 8pm. Right now that message waits until you are free. Automating the reply means they hear back in minutes, answer two or three of your qualifying questions, and land in your CRM with those answers attached.
The best-known data on this is a Harvard Business Review study of 1.25 million sales leads across 42 companies. Businesses that contacted a lead within an hour were about seven times more likely to qualify it than those that waited longer. The study is US data from 2011, so read it as a direction, not a promise for your trade. The direction is clear, though, and it matches what we see in the accounts we run: the business that replies first usually wins the job.
Nothing else about your business has to change for this to work. Same team, same quotes, same phone. The only change is that the first message no longer waits for you. For what that looks like day to day, read what AI agents actually do for a small business.
What should you automate second?
Follow-up on leads that go quiet. This is the job people forget, not the job they dislike. A quote goes out on Tuesday, the customer says they will think about it, and nobody checks back because Thursday is a busy day.
A follow-up sequence fixes that with no willpower required. In our experience a good one is short: a check-in the next day, a second nudge a few days later, then it stops. Each message reads like it came from you, because you wrote it once. Anyone who replies is flagged for a call.
Tone matters here. Write each message the way you would text a customer yourself, plain and short, with no "just circling back" filler. A follow-up that sounds like a form letter gets ignored, and one that sounds like you gets answered. Keep the number of messages low. Three polite follow-ups feel like service. Eight feel like pressure, and customers remember that.
Are booking reminders worth automating?
Yes, and they are the easiest win on this list. A text the day before a site visit, with the time, the address and a way to reschedule, costs you nothing per message once it is set up. It cuts the no-shows where a tradesperson drives across town to an empty driveway.
The same goes for a review request after a finished job. Send it the day the job closes, while the customer is still pleased. Ask once, and make it one tap.
How do the jobs compare?
Here is the order we would build them in, and who keeps the job.
| Job | Automate? | Why |
|---|---|---|
| First reply to an enquiry | Yes, first | Speed decides who wins the lead |
| Qualifying questions | Yes, with the reply | Same questions every time, answers filed in the CRM |
| Follow-up on quiet leads | Yes, second | The step people forget |
| Booking reminders and review requests | Yes, third | Low risk, saves you chasing |
| Quoting and pricing | No | Needs judgement from having done the job |
| Complaints and upset customers | No | A person needs to listen |
| Answering a phone call | No | A caller wants a voice, not a script |
The pattern is simple. Automate the repeatable, low-judgement steps that happen every week. Keep the steps where a customer is deciding whether to trust you.
What is not worth automating yet?
Anything you have not mapped. An automation copies a process. If your process is still "it depends who picks up the phone", automating it makes the inconsistency faster. Write down who does what, in what order, before you build anything.
Two other cases are usually not worth it. The first is a business with very few enquiries. If you get three a week and answer each one within the hour from your phone, an automation has nothing to fix. The second is a big-ticket sale where the first conversation is the sale, such as a renovation consult or a legal matter. Automation can book that meeting. It should not run it.
We would also hold off on anything that needs data you do not yet have. A fancy reporting dashboard on top of a messy CRM just shows the mess in colour.
What does this look like for a real week?
Take a heat pump installer getting thirty enquiries a week across a web form, Messenger and a landing page. Before automation, the owner replies between jobs. Evening enquiries wait until morning, and some wait until Monday.
After automation, each enquiry gets a reply within minutes. The reply asks whether it is a new build or an existing home, and how many bedrooms. Those answers go into the CRM. At 8am the owner opens a short list of qualified leads and calls the best ones first. A lead that went quiet gets a nudge the next day. The day before a site visit, the customer gets a reminder text.
That is the whole change. The owner still quotes, still visits and still closes. What disappears is the gap between a customer asking and a business answering, and the pile of small chasing jobs that fill an evening.
How do you know it is working?
Watch three numbers for the first month: how long the first reply takes, how many enquiries reach a qualified stage, and how many of those turn into booked visits. If the first reply is fast but nobody books, the questions are wrong, not the speed.
Read the actual conversations every week, at least at the start. You will spot an awkward question or an answer that sounds off within a few reads, and each fix improves every future enquiry. An automation you never read is one you cannot trust.
Keep a baseline too. Note how long replies took before you switched it on, so the comparison is honest rather than remembered.
What do you need in place before you start?
Two things: a CRM and a person who owns the handoff. The CRM is where every enquiry, answer and outcome gets recorded. Without it, automation moves the mess from your inbox into a chat log.
The owner of the handoff is whoever gets notified when a lead is qualified and actually picks it up. The automation's good work is wasted if a qualified lead sits unread overnight. If both exist, a first automation takes days, not months, to build. In the accounts we run, the slow part is almost never the software. It is writing down how you sell.
If you already run paid ads, the first reply matters even more, because every slow reply wastes money you already spent. Work out what a lead costs you with the ad spend calculator. If you want a second opinion on the ads feeding those enquiries, our free ads audit is the place to start.