The Chatbot Promise Checklist
Find every sentence your business says about its chatbot, then make each one true and provable: who it's for, when a person takes over, what happens in a crisis, and the record that shows it.
On October 14, 2026, eight states (Arizona, Arkansas, Idaho, Iowa, Kansas, Montana, Nebraska and West Virginia) each sued OpenAI over ChatGPT, after Florida sued in June. None of them used an AI law. They used consumer-protection law: the kind that asks whether what a business said about its product is true. These are allegations; no court has ruled, and OpenAI disputes them.
The idea isn't new. In 2024, Air Canada's website chatbot told a grieving passenger he could claim a bereavement fare after his flight. He couldn't. The airline argued it wasn't responsible for what the chatbot said. The tribunal disagreed: the chatbot "is still just a part of Air Canada's website." About $650, and a principle.
Your bot's words are your words.Nobody has tested these laws on a support bot yet, and this isn't legal advice. The checks below follow the four words a typical chat widget uses: "Hi, I'm your safe, accurate assistant, here for everyone, always."
Find every sentence about your bot. They live in more places than the widget:
Where it lives: [PAGE / LISTING / AD / POLICY / BOT REPLY]
Proof it's true: [THE TRANSCRIPT OR TEST THAT SHOWS IT]
If no proof, rewrite as: [WHAT THE BOT ACTUALLY DOES]
If your bot isn't meant for kids, say so, and then do something about it. The worst place to be is a policy that says you don't knowingly talk to children while your own logs say you do.
A protection is only as good as the gate in front of it. The complaint says OpenAI's teen rules switch on when a user says they're under 18, or when its age prediction believes they are.
Decide in advance when the bot stops. This is the one to get right.
with the conversation attached, when someone:
- asks for a person
- repeats themselves
- brings up money, health or legal trouble
and does not just drop them. Right away it gives [YOUR LOCAL CRISIS LINE]
and brings in [A REAL PERSON].
Test it in long conversations, not just the first message. California's companion chatbot law leaves out bots used only for customer service. Do it anyway.
What gets read is dates: a dated policy, your test transcripts, a change log, a record of every handoff. Your record should show the safeguard came first, not the week after a complaint. Once a month, have someone on your team play three people:
Save those transcripts. When something does go wrong, write down what happened and what you changed, with the date.
Tested by: [NAME]
Fourteen-year-old: [ROUTED AWAY? Y/N]
Angry customer: [HANDED TO A PERSON? Y/N]
Not okay: [CRISIS LINE + PERSON, RIGHT AWAY? Y/N]
What we changed: [ONE CHANGE, WITH THE DATE]
Start here. Which word is coming off your chatbot's description first: safe, accurate, or always?
Sources
Keep reading free with your library card
One email opens this checklist and all 3 resources in Mathew's library. No account, no password.
Copy every sentence about your chatbot, from your website, app listing, ads, privacy policy and the bot's own greeting, into one list.
Saving works best in your phone's browser. A copy is also in your inbox.