You paste in a review, press the button, and the reply looks fine. Then you read it a second time and spot a refund you never offered. That's the usual symptom, and it comes from how these tools work.
What the tool is actually doing
An AI writing tool of this kind is a large language model. It doesn't read the review the way a person does, and it doesn't know your business. It predicts which words are likely to come next, based on the text you gave it and the patterns it learned from a huge amount of writing.
That's why the output sounds smooth. It's also why smooth isn't the same as true. Wikipedia describes hallucinations as fluent text that appears factually sound but is factually incorrect.1
For review replies, a hallucination might be:
- a staff member's name you don't employ
- an opening time or policy the tool guessed
- an apology for something the customer never complained about
- a promise to fix a problem you haven't looked into
Cause one: the tool had too little to go on
If you paste only the review, the tool fills the gaps with guesses. A short review gives it very little, so it falls back on stock phrases like "we value your feedback".
The fix is to give it more. Wikipedia describes prompt engineering as designing and refining the instructions given to an AI model to get more accurate, relevant or useful output.2 For you, that means adding a few lines about your business and the tone you want. What to give the tool covers exactly what to include.
Cause two: the tool copied a pattern
Prompts can include a few examples for the model to learn from.2 If you paste one of your old replies as an example, the tool tends to copy its shape. That helps with voice. It can also mean every reply opens the same way.
If your replies are starting to look alike, vary the example you give it, or ask for a different opening line. Keeping your own voice goes further on this.
Cause three: it can't see what happened
The tool has no record of the job, the order or the visit. It can't know whether the customer is right. So it may agree with an unfair complaint, or argue with a fair one.
Before you ask for a draft, decide what you actually know. Check the booking, the till record or your own notes. Then tell the tool the facts you've confirmed, and tell it what you haven't.
Cause four: it doesn't know the reply is public
Your reply is publicly posted under the customer's review, and the person who wrote the review is notified when you reply.3 The tool doesn't weigh that. It may repeat details from the review, add order information, or sound far too casual or far too stiff for a public page.
That's a human job. What never to put in a reply lists the details to keep out.
A short routine that catches most problems
- Give the tool the review, a few facts you've checked and the tone you want.
- Ask for a short draft, not a finished reply.
- Read it slowly and mark every claim: a name, a time, an offer, an apology.
- Delete or fix any claim you can't back up.
- Read it out loud. If it doesn't sound like you, change it.
The tool saves you the blank page. It doesn't save you the reading. Editing the draft before posting has a fuller checklist.
Reference list
- Large language model, Wikipedia
- Prompt engineering, Wikipedia
- Manage customer reviews, Google Business Profile Help