Customer Trust and the Cost of Your First Public AI Mistake

Customers do not experience your architecture. They experience a sentence with your name on it. When that sentence is wrong, the argument that “the AI said it” lands the way “the intern said it” would have landed, except the intern did not speak at the scale of a website, and the intern could be asked what they meant. The model cannot. Trust, after the first public mistake, is rebuilt by showing a change in how sentences are allowed to leave, not by a post that says you take the issue seriously.

The case law and the market have already supplied the examples. Air Canada told a grieving passenger, through its website chatbot, that a bereavement fare could be claimed after travel. The policy page said otherwise. The tribunal refused the idea that the bot was a separate entity. In February 2023 Google’s Bard demo included a factual error about a satellite; Reuters reported that Alphabet shed on the order of $100 billion in market value in the session. Different stakes, same mechanism: a public sentence, an identifiable company, an audience that does not grant a hallucination discount.

Why the apology fails

The standard crisis statement promises a review, a model update, and a commitment to accuracy. Customers have learned what that sequence means. The review will be internal. The model update will not be visible. The next mistake will sound just as confident. Trust is not a tone. It is a prediction that the next interaction will be governed. If nothing in the customer’s experience changes — no clearer policy, no easier path to a person, no visible correction of the specific claim — the prediction does not change.

There is also a fairness problem the apology skips. The customer who relied on the wrong sentence has often already paid, travelled, or declined another offer. Air Canada’s passenger had flown. A correction that arrives as a lesson for the company, without a remedy for the person, teaches the market that reliance is the customer’s mistake. The tribunal did the opposite. It treated reliance as reasonable. Your recovery design should assume a future decision-maker will do the same.

What to do in the first week, and how to prevent a second

In the first week, find the sentence. Not the topic. The sentence. Preserve it. Identify who could have stopped it and why they did not. If the answer is that nobody was assigned, say that internally without euphemism. Offer the customer the remedy the correct policy would have given, or a better one, quickly. Speed of remedy is the only part of the apology people can verify.

Then change the gate. Customer-facing assistants should be bound to the current policy, not to a pile of pages in which the current policy is merely the most popular. When the assistant and the policy disagree, the assistant loses, and the disagreement is ticketed. A human sees the exact outbound words for the classes of promise that cost money: fares, credits, coverage, delivery, exceptions. The EU AI Act’s oversight language — people able to interpret outputs and intervene — is a good design test even for uses the Act does not classify as high-risk. A footer that says “AI-generated” is not intervention.

Publish, where you can, the rule you corrected. Customers trust companies that show the rule more than companies that show the model. You do not need to publish weights. You need to publish the bereavement rule, the return window, the coverage trigger, in the same place the assistant lives, and keep them identical.

The internal audience is also the public

Staff read the incident. If leadership’s lesson is “don’t get caught,” staff will route around the sanctioned bot and draft answers in personal tools. Seventy-eight percent of AI users already bring their own. A public mistake followed by a ban, with no usable alternative, increases that share. The next error will be harder to find because it will not be in your log. Samsung’s restriction after a leak made sense as a pause. As a permanent strategy it hides the work. Recovery includes a path staff prefer to their phones, because the public brand is whatever path they actually use.

Marketing will want to move on. Let them move on only after the gate exists. The FTC’s warning on AI claims is a constraint on the comeback campaign. Do not announce that the assistant is now “trusted” or “accurate” because you retrained something. Announce the control a customer can understand: a person checks promises over a threshold; the policy page and the bot cannot diverge without an alert; here is how to reach a human. Claims you can demonstrate are the only claims that repair anything.

The second mistake ends the argument

Customers will forgive a first error if the second interaction proves the system changed. They will not forgive a second error of the same kind. The second error says the apology was a holding statement. It is also the moment journalists, regulators, and plaintiff firms stop treating the incident as a glitch and start treating it as a practice. A public demo error moved a market in a day. A repeated customer-facing error moves a reputation more slowly and more permanently, because each screenshot confirms the last.

Design the fortnight after the incident as a control sprint, not a communications sprint. Freeze the class of promise that failed. Route it to humans. Sample every answer in adjacent classes. Publish the corrected rule where the assistant lives. Tell staff, in writing, what they may not paste into personal tools while the freeze holds, and give them the sanctioned draft that already contains the corrected rule. If you only freeze the website bot, the phone channel will recreate the sentence by lunchtime.

Then look for siblings. The bereavement rule was wrong because a stale answer and a current page were both allowed to speak. Search for other pairs: a return window in the bot and a different window in the terms; a coverage phrase in sales macros and a different phrase in the policy. Each pair is a future screenshot. Retire one side this fortnight. The tribunal’s point was that customers are not obliged to know which of your pages is the real one. Neither are your new employees.

Report to the board in sentences, not themes. What was said. Who relied. What remedy was given. What gate now stops a repeat. What remains unfixed. A board that receives “we have reinforced our commitment to accuracy” has not been briefed. A board that receives the sentence and the control can govern. Claims you cannot demonstrate should stay out of the comeback, including the claim that the problem is solved.

Trust is a lagging indicator. The leading indicators are contradictions found, promises routed to a person, and time-to-remedy for the customer who already relied. Put those three in the weekly customer review until they are boring. Boring means the operating change took. A campaign means it did not.

What “sorry” must contain

Name the sentence that was wrong. Name the remedy for people who relied on it. Name the rule that replaces it, and the hour the old source was withdrawn. Name the person who now sees that class of promise before it is sent. Leave out the sentence about your commitment to innovation. Customers cannot test a commitment. They can test the next answer. Your repair will be judged the same way the Bard error was: by the next transcript, not by the statement.

Search the siblings in the same week. Two numbers for one noun, anywhere a customer or a seller can see them. Each pair gets an owner and a retirement date. Report the open pairs to the board until there are none. Do not claim the channel is now safe in the abstract. Claim the pairs you closed. Trust is the customer’s ability to predict you. Prediction is one version of the rule, in every tool your staff actually use.

A call to chief marketing and customer officers

Assume the screenshot. Design the assistant as if the worst answer will be attached to a complaint. That is not cynicism. It is how Air Canada’s case was proved. Then rehearse the recovery before you need it: who freezes the bot, who authorises the remedy, who changes the rule, who tells the board the sentence rather than the vibe.

Trust after a public AI mistake is not a communications project. It is an operating change the customer can feel on the next visit. If they cannot feel it, they are right not to come back.

References

• CBC News, Air Canada found liable for chatbot’s bad advice
• Moffatt v. Air Canada, 2024 BCCRT 149
• Reuters, Alphabet shares dive after Bard error
• Regulation (EU) 2024/1689
• Microsoft and LinkedIn, 2024 Work Trend Index
• CNBC, Samsung restricts generative AI
• U.S. FTC, Keep your AI claims in check