Customer communication
When AI gets it wrong in front of a customer
Your automated reply quoted a delivery date you cannot meet, or a discount you do not offer. The customer is holding it in writing. What you do in the next hour matters more than how it happened.
Most advice on this subject is about prevention, which is useful right up until the morning it happens anyway. This is about the morning it happens anyway.
It was your system, so it was you
Start from the position that saves the most time: the customer does not care which part of your business produced the message. It came from your address, with your name on it.
"Our AI made an error" reads as an excuse and invites the obvious reply — that you chose to use it. Businesses that recover well from this skip the explanation entirely and go straight to what they are going to do.
Do you have to honour it?
Often the honest answer is: possibly, and it depends on where you are and how obvious the error was.
In many places a clear mistake — a price with a missing digit, terms you plainly never offer — is not binding, particularly if you correct it quickly and the customer could reasonably have spotted it. A plausible-looking quote that someone relied on in good faith is a much weaker position.
This varies by jurisdiction and by whether your customer is a business or a consumer, who usually has more protection. If the amount is significant, ask someone who knows your law rather than deciding from a web page.
The commercial judgement is often simpler than the legal one. If honouring a wrong quote costs less than the argument, the review and the retelling, honour it and move on.
What to do in the first hour
- Turn off the thing that sent it while you work out how wide the problem is. A pause costs a little; a second customer receiving the same error costs far more.
- Find out who else got it. If one wrong reply went out, check whether fifty did.
- Contact them yourself, from your own address. Not another automated message.
- Decide the remedy before you write, so the message contains an answer rather than an apology and a delay.
- Write down what happened while it is fresh — this is what you will use to fix it properly.
The version that makes it worse
Three responses reliably escalate a recoverable situation.
Defending the output. Arguing that the message was technically ambiguous when the customer clearly read it the obvious way.
Another automated reply. A customer complaining about an automated error who receives an automated apology has now been told twice that nobody is reading.
Silence while you investigate. Two days of nothing is read as evasion. A holding message that says what you are doing and when you will come back is enough.
Then fix the actual cause
Almost every one of these traces back to the same thing: the system was allowed to state something it had never been told.
It did not know your delivery times, so it produced a plausible one. It did not know your discount policy, so it invented something reasonable. The failure was a briefing gap, not a malfunction.
- Supply the real facts — prices, timescales, policies — rather than hoping.
- Instruct it to leave a marked gap when it does not know, instead of guessing. This converts a silent wrong answer into a visible blank.
- Keep a person between the draft and anything that commits you to a price, a date or a promise.
That third one is the line most businesses eventually settle on. Drafting is a genuine time saving; sending unreviewed commitments is where the saving turns into a liability.
The question worth answering honestly
After the immediate problem is dealt with: was this task ever suitable for automation, or did it get automated because it was easy to automate?
Some jobs are worth the occasional error because the volume saving is large and the mistakes are cheap. Some are not, and one bad week is enough to find out which kind you had.