Letting AI handle first replies, without losing the personal bit
You are on a job, or with a patient, and a message comes in. “Do you cover Hythe? Can you do Saturday?” If that sits unanswered until the evening, there is a good chance the person has already messaged someone else.
The first reply often decides who gets the work. That does not mean a chatbot should run the business. It means a common question, a name and number, or a time to talk can be handled while you are busy, as long as the important conversations still come to you.
By Mike Dunkling, founder of Zatheo in Ashford, Kent.
What’s changed
Most small businesses do not have a lead problem as much as a reply problem. A form arrives while you are with a customer. A call goes to voicemail after hours. A Messenger or Instagram message sits until Monday. The person on the other end is trying to get an answer, and they will often take it from whoever replies first.
People now expect a quick response, including in the evening, and the same business is often taking enquiries from a website form, a phone, Messenger, Instagram and text, with no single place that shows what is waiting.
AI can take some of that first reply, if you set it up carefully. We build chatbots on GoHighLevel Conversation AI for website chat, Messenger, Instagram DMs and SMS. WhatsApp and voice AI can be added later. The assistant answers from your own information, not the whole internet, and it should say plainly that it is an AI assistant. It can take enquiry details, offer a booking link and pass anything it should not handle to a person.
Behind the scenes, AI automation can also sort new enquiries, tag them and draft a reply for you to check. That is a different job from a public-facing chatbot, but it solves the same delay.
What it means for your process
The change is not “let AI talk to customers”. It is “decide what the first reply is allowed to do, then keep everything else”.
| Before | After |
|---|---|
| You, or nobody, answers whenever you next look at your phone | Common questions get a useful first reply at once, and you pick up the ones that need a person |
| The same questions, “Do you cover my area?”, “What does it cost?”, “When can you come?”, are typed out again and again | Those answers live in a source the assistant uses, which you keep up to date |
| Website forms, missed calls and social messages live in different inboxes | They land in one CRM, with an alert, so nothing relies on you remembering to check |
| Follow-up happens if you have time | A booked call, a missed-call text or a short follow-up sequence happens as a matter of course |
| You find out a week later that someone asked something the bot got wrong | You review conversations, correct weak answers and tighten the limits |
What you still do yourself is the work that needs judgement: a quote, a complaint, advice, an unusual job, or a conversation with someone who is already upset. You also own the source information. If the hours, prices or areas change, the assistant’s answers have to change too.
A 90-day plan
Weeks 1-2: see where first replies are failing
For a fortnight, write down every enquiry, how quickly it got a useful reply, the channel, and whether the person booked or went quiet. Include the ones that never got a reply.
If you only get a handful of enquiries a week and you already reply quickly, a chatbot may not be worth it yet. A clearer form and a missed-call text back may do more. If the same questions arrive after hours, or sit in Messenger over the weekend, that is the work a first-reply assistant is for.
List the ten questions you are asked most often, and write the answers you are happy to stand behind, including “we will need to speak to you about that”. Those answers become the source, whether you install a bot or not.
Month 1: fix the basics, then decide what to automate
Before you add a chatbot, make sure an enquiry cannot disappear. Forms should go somewhere you see immediately. A missed call should get a text back. One person, or one inbox, should own the follow-up for the day.
Then choose one job for AI, not five. The most useful first job is usually answering those ten questions, taking a name and number, and offering a time for a call. Keep prices, advice and complaints for a person, unless you have published a price and are happy for the assistant to repeat it.
If you want the public-facing assistant, we set it up on GoHighLevel Conversation AI and connect the channels you actually use. If you mainly need faster follow-up, start with automation and lead handling instead. AI automation projects start from £3,000. Chatbot fees are confirmed on a call, because they are not published here yet.
Test with the awkward questions as well as the easy ones, and make sure a visitor can reach a person without a fight.
Months 2-3: review the conversations and keep the limits tight
Once it is live, read the conversations. Look for wrong answers, questions it should have passed on, and new questions to add to the source, and correct them promptly. If your services or hours change, update the source the same day. If you also update the site by chatting with an assistant, keep the two consistent.
Use the same months to close the loop after the job. A review request, sent once the work is finished, with a direct Google link, is follow-up too. The rules for that are in from word of mouth to a steady flow of enquiries.
At the end of 90 days, judge the set-up on enquiries and bookings captured, and on whether the answers were right, not on how many chats it had. If it is not earning its keep, switch it off.
Common mistakes
Letting the assistant invent an answer. If it does not know, it should say so and pass the question on. A wrong price, or a confident “yes, we cover that town” when you do not, is worse than a delayed human reply.
Hiding that it is an AI assistant. People should know what they are talking to, and they should be able to reach a person.
Installing a bot when the real problem is the website or the inbox. If the site is unclear, or forms go to an address nobody checks, a chat window will not fix it.
Setting it up and never reading the transcripts. Services, prices and questions change. A chatbot that is not reviewed will drift.
Trying to replace the team. The aim is to take the repetitive first reply off you. Anything that needs judgement stays with a person.
How Zatheo can help
We set up automation and lead handling so forms, phone and calendar feed one CRM, with instant replies, missed-call texts and follow-up. Projects from £3,000. For AI that sorts enquiries and drafts replies for your team to check, see AI automation, also from £3,000. AI chatbots on website chat, Messenger, Instagram DMs and SMS are a related service: AI chatbots. We will tell you if a chatbot is not the right next step.
If you would like us to look at how enquiries reach you now, and where they are being lost, Book a free 30-minute call.
Frequently asked questions
Will a chatbot replace my staff or me?
No. The assistant handles common questions, takes details and books calls. Quotes, complaints, advice and anything unusual stay with a person.
Which channels can it work on?
Website chat, Facebook Messenger, Instagram DMs and SMS, managed in one place. WhatsApp and voice AI can be added later.
What if it gives a wrong answer?
Any AI tool can get things wrong, which is why we limit what it answers, base its replies on your own information, and pass prices, advice and complaints to a person. Regular reviews after launch catch and fix weak answers.