Skip to content
Rawleaf

Guide

How to use AI to reply to enquiries quickly, without sounding like a robot

A plain-English guide for small UK businesses on using AI to answer customer enquiries quickly and in your own voice, and where a person must stay involved.

By Rawleaf · · 7 minute read

When someone gets in touch with a business, they're often getting in touch with a few others at the same time. The one that replies first, clearly and helpfully, is usually the one they remember.

The trouble is that in a busy team, nobody owns the inbox. Enquiries arrive while everyone is with customers, on site or in meetings. They get read on a phone, mentally parked, and answered hours later, or not at all, because everyone assumed someone else had replied.

AI can help with this. It can send a fast, useful first reply at any hour. But done badly, it sounds like a call centre script, annoys the people you most want to impress, and occasionally says something you'd never have agreed to. This guide is about doing it well.

What makes a reply sound robotic

Most people can spot an automated reply in a sentence. It usually comes down to a few things:

  • It doesn't answer the question. "Thank you for your enquiry, a member of our team will be in touch" tells the customer nothing they didn't already know.
  • It's padded. Three lines of thanks and reassurance before anything useful.
  • It's in a voice that isn't yours. Overly formal, overly cheerful, or full of phrases nobody in your team would ever say.
  • It pretends to be a person. And then gets found out, which is worse than being upfront in the first place.

What a good AI reply does instead

A good first reply sounds like your most helpful member of staff on a good day. In practice that means:

It answers what was asked, if it can. If someone asks about prices, opening times or whether you cover their area, and you've given the assistant the answer, it gives it. Straight away, in the first line.

It uses your wording. You give it examples of replies you were happy with, the phrases you use, and the ones you don't. It follows them. This is the single biggest difference between a reply that sounds like you and one that doesn't.

It's short. A few sentences, not a page.

It gives one clear next step. A booking link, two questions it needs answered, or when a person will be in touch. Not a menu of options.

It's honest about what it is. Something as simple as "I'm the assistant for the team here, and I can help with the basics" is enough. People mind being misled far more than they mind talking to an assistant that's useful.

What can go out automatically, and what should wait for a person

This is the most important decision you'll make, and it's yours to make. A sensible starting line:

Fine to send automatically, in wording you've approved in advance:

  • acknowledging an enquiry and saying when a person will reply;
  • answering factual questions you've written the answer to, such as opening times, areas covered, standard prices you publish anyway, or what to bring;
  • asking for the details your team always needs, such as a postcode, photos or preferred times;
  • sending a booking link or confirming a booking.

Should wait for a person to approve:

  • anything that commits the business, such as a price for a specific job, a discount, a deadline or a promise;
  • anything about payments, refunds or money owed;
  • decisions about people, such as whether someone is suitable for a role, a property or a service;
  • professional advice, including anything clinical, legal, financial or about safety;
  • important or unhappy customers, complaints, and anyone who asks to speak to a person.

In these cases the assistant can still help. It can draft the reply so a person only has to check it, and tell the customer honestly that someone will be in touch.

What you need before you start

The quality of the replies depends on what you give the assistant. Before trying anything, gather:

  • Your ten most common enquiries, and the answer you'd give to each. Look back through your inbox and messages to find them.
  • Five or six replies you were proud of. These show the assistant your tone better than any description.
  • Your handover rules. Which topics always go to a person, who that person is, and how quickly they should reply.
  • A list of things it must never say. For example, never confirm a price that isn't on the published list, never promise a date.

Writing this down is useful on its own. It often shows that different people in the team are giving different answers to the same question.

A simple way to try it this week

You can test the idea with a general-purpose AI assistant before building anything:

  1. Put your common questions, answers and example replies into one short document.
  2. Pick five real enquiries from the last month and remove anything personal: names, addresses, phone numbers, email addresses. Don't paste customer details into a consumer AI tool.
  3. Ask the assistant to draft a reply to each, using only the information in your document, in the same style as your examples, and to say clearly when it doesn't know something.
  4. Compare its drafts with what your team actually sent.

You'll quickly see which enquiries it handles well, and which ones still need a person.

Where to be careful

It can be confidently wrong. If the answer isn't in what you've given it, a poorly set-up assistant may make one up. Tell it to say "I'll check with the team" instead, and test it with questions it shouldn't be able to answer.

Keep the information current. If your prices or opening hours change, the assistant needs to know the same day. Out-of-date answers are worse than slow ones.

Make handover easy. A customer who asks for a person should get one, and the person should see the whole conversation so the customer doesn't have to repeat themselves.

Mind people's data. Enquiries contain personal details. Once you go beyond testing, use business tools set up properly for UK GDPR, with the right agreements in place. Our guide to AI and UK GDPR for small businesses covers the basics.

When it's worth automating properly

Testing by hand tells you whether the idea works. Building it properly means the assistant:

  • picks up enquiries from wherever they arrive, such as your website, email, WhatsApp or a booking platform;
  • replies using your approved wording and current information;
  • passes anything outside its limits to the right person, with the conversation attached;
  • holds drafts that need approval until someone has checked them; and
  • follows up if a customer goes quiet.

That's the kind of thing we build in an AI Pilot Build, which starts from £5,000. If you're not sure enquiries are the right place to start, our AI Health Check looks across your whole business and ranks the options first.

More for your industry: AI for tradespeople, AI for letting agents, AI for clinics, AI for accountants