Chatbot Liability: Who Pays When Your Bot Gives a Wrong Answer

Short answer: in most cases, chatbot liability lands on the business running the bot on its website. And that makes sense. Customers see the bot as the company talking, not as some separate party. What worries most owners is pretty concrete: a bot promising a refund, a price or a rule nobody in the company ever signed off on. Below I’ll go through where that risk comes from, what the law covers (and what it doesn’t), and the practical steps that stop a bot from guessing.

Who is responsible when a chatbot gives a wrong answer?

Usually you are. When a chatbot gets something wrong, customers and regulators look at the company that deployed it. Think about it from the customer’s side: the widget sits on your site, wears your brand and answers in your name, so why would they treat it as a third party? Company responsibility for chatbot replies mostly comes from rules you already live with: contract terms, consumer protection, and advertising and pricing rules under national law. How much of the risk the software vendor carries depends on your contract with them. Read it. Just don’t assume the vendor will pick up the bill for a promise the bot made to your customer.

Does the new EU Product Liability Directive cover chatbot mistakes?

Partly. And not for the typical case. The directive covers damage suffered by natural persons, while a wrong answer usually causes pure economic loss. Under the revised EU Product Liability Directive, software, AI systems included, counts as a product for no-fault liability. The damage it compensates is death, personal injury, damage to property, and destruction or corruption of data. Pure economic loss, privacy infringements and discrimination don’t trigger liability under it on their own, and it leaves contract, warranty and fault-based claims alone. So no, it isn’t a chatbot liability law. A bot quoting the wrong price is still a job for ordinary contract and consumer rules.

Where chatbot legal risk actually comes from

Mostly from the bot filling gaps with guesses when your content is missing, outdated or contradicts itself. It gets dangerous on topics where an answer reads like a commitment:

• refunds and returns
• prices and discounts
• delivery times
• warranty terms
• eligibility rules
• anything medical, legal or financial

Here’s the thing. AI chatbot misinformation usually starts with the source material, not just the model. An old price list, two versions of the same policy, a vague FAQ - each one gives the bot room to improvise. And a disclaimer won’t close that gap. A little note saying “the bot can make mistakes” is no substitute for correct content.

How to limit chatbot liability before you go live

Keep the bot on your own verified content, make it admit when it doesn’t know, and review its answers on risky topics before launch. In practice that looks like this:

1. List the topics the bot must never decide, such as refunds, custom prices and exceptions.
2. Write short, unambiguous source pages for each policy.
3. Remove outdated and duplicate documents.
4. Set a fallback answer that points to a contact page or email address instead of guessing.
5. Test the bot with the questions customers really ask, including the tricky ones.
6. State in the widget that the binding terms are in your published policies.

If I had to pick one, it’s step four. Setting up fallback answers that avoid guessing is simple, honestly.

Keeping answers correct after launch

A bot is only as accurate as the content it reads. Prices change, policies change, and the bot needs to know the same day. Give one person ownership of policy and price changes, and put bot content updates on the same checklist as website updates. Go through the conversation logs regularly and look for questions the bot answered badly or couldn’t answer at all. Then fix the source page, not the symptom. Do you need a dedicated editor to keep the knowledge base current? Nope. A steady routine does the job.

What to do when the bot has already said something wrong

Fix the source content first. Then reach out to the customer and agree on a fair outcome based on your terms and local consumer law. Save the conversation record exactly as it happened (don’t tidy it up), and check whether other customers got the same answer. If the disputed promise involves money, talk to a lawyer who knows consumer law in your country, because this article isn’t legal advice.

Bottom line: chatbot liability stays manageable when the bot reads only verified content and says “I do not know” instead of guessing. If you’d like help setting that up, have a look at our plans with implementation support. And for a wider view of the risks, our posts on AI risk cover related questions.

FAQ