How to use AI to reply to WhatsApp customers without sounding like a bot
The short answer
Give it real facts about your business before you worry about tone. A reply sounds robotic when it is generic, and it is generic because the writer had nothing specific to say. Once it knows your prices, your hours, what you actually sell and what you never promise, it stops hedging, and the hedging was what sounded like a bot.
The WhatsAssist team ·
Most advice about this is about tone. Write shorter sentences, use contractions, add an emoji. That advice is not wrong, but it treats the symptom.
A reply sounds like a bot when it is vague. “Thank you for your enquiry, we will get back to you shortly” is not badly worded. It is a sentence written by something that had no idea what you sell, so it said the only thing that is true of every business. Fix the vagueness and most of the robot goes with it.
Start with facts, not with a prompt
The single highest-value thing you can do is give it specifics before you touch the wording.
Look at your last fifty customer messages and write down what the answers actually depend on. For most small businesses it is a short list:
- what you sell and what each thing costs
- what you do not sell, and what you will not promise
- delivery, collection, and what each costs where
- hours, and the exceptions
- how a booking or an order actually works
- the four or five questions you answer every single week
You can hand that over as pasted text, a PDF, an image of a price list, or an export of a WhatsApp chat where you already answered these things well. A chat export is often the best of these, because it contains your real answers in your real words rather than a tidied-up version you wrote for the occasion.
The difference this makes is not subtle:
Without facts: “Thanks for reaching out! Could you let me know a bit more about what you’re looking for?”
With facts: “The olive one is 2,400 and we have it in medium and large. Delivery in the city is 150 and takes two days. Which size do you want?”
The second is shorter, warmer and more human, and none of that came from tone instructions. It came from knowing the price.
Set one voice, and be honest that it is one voice
You can tell it how to sound: formal or casual, how much detail, whether to use the customer’s name, which phrases you always use and which you never use. The never-say list is worth more attention than people give it. If you never guarantee a delivery date, write that down, because that is a sentence you do not want written on your behalf on a busy Tuesday.
Be aware of the shape of this: you are setting one voice for your business, not a separate personality for each type of customer. If you want your wholesale enquiries handled differently from your retail ones, the lever is which topics get handed back to you, not a second tone.
There is no number of messages after which it suddenly sounds like you. It improves as you give it more real examples of your own answers, and the fastest way to get there is to feed it the conversations where you already sounded right.
Answer first, then ask
The most common structural mistake is asking before answering. A customer sends “how much is delivery?” and gets back “Could you tell me your postcode?” That is a reasonable question and it still feels like an obstacle.
Better is to answer what can be answered, then ask for the one missing thing:
“Delivery in the city is 150 and takes two days. Outside the city it depends on where you are, so send me your area and I will confirm.”
Same information requested, and the customer has been given something. Ask for one detail at a time, never three.
Decide what it should not touch
This is the part that matters most and gets the least thought.
Good candidates for automatic handling are the questions where you would have typed the same answer anyway: prices, availability of a standard item, hours, delivery, what is included, how to book, where you are.
Hand back to yourself anything where being wrong is expensive:
- refunds, cancellations and anything about money going backwards
- a customer who is already annoyed
- complaints, and anything that mentions a previous problem
- wholesale, bulk and partnership enquiries
- medical, legal or safety questions, if your trade touches any of those
- anything involving a promise about a date you cannot control
You configure that as a list of topics that get escalated to you instead of answered. Spend real time on this list. It is the difference between a tool that saves you an hour a day and one that costs you a customer.
Know what happens by default
Be clear about this before you switch it on, because it is not what people assume. Once setup is finished, WhatsAssist answers a customer message by itself, on every plan. There is no screen where you are asked to confirm each one.
One switch in the app turns that off. With it off, every reply waits in the app for you to read, edit and send instead. Plenty of people run it that way for the first week, and it is a sensible way to start: you get to read what it would have said, on your real customers, before you let it speak for you.
Either way, a reply that fails one of our safety checks does not go out. It becomes a draft with the reason attached and waits for you in the app. It never fails silently, and you can see the reason it stopped.
On the Free and Basic plans the first message it composes in a conversation carries a short line saying a reply assistant wrote it. That is deliberate. A customer who finds out later feels tricked, and a customer who is told up front mostly does not care.
Three replies, before and after
A price question.
Weak: “Thanks for your message! Our team will get back to you with pricing shortly.”
Better: “The standard service is 3,500 and includes the site visit. The extended one is 6,000 and adds the follow-up. Which suits you?”
A booking enquiry.
Weak: “Please share your details and we will check availability.”
Better: “We are open Tuesday to Saturday, 10 to 7. Tell me the day that works and I will get you a time.”
A question you cannot answer.
Weak: “Yes, that should be fine.”
Better: “I want to check that properly rather than guess. Give me a little while and I will come back to you today.”
The third one is the important one. A reply that declines to invent an answer is worth more than a confident wrong one, and “should be fine” is how a small business ends up honouring something it never meant to offer.
Where to start this week
Write your prices, hours and delivery terms into it. Write your never-say list. Write your escalation topics. Then leave the send switch off for a week and read what it would have said to real customers. You will learn more from that week than from any amount of tone tuning.
If you are still deciding whether this is the right category of tool at all, the comparison with template autoresponders is the honest version, and what happens when a reply is wrong is worth reading before you turn anything on. Otherwise, what it does and what it costs are both a page away, and the first 100 messages are free.