Skip to article
The Design Office of Nick Sloggett
WorkWritingExperimentsResumeEmail
Back
Essay·Feb ’24·2 min read

The chatbot is part of the website

A Canadian tribunal held Air Canada liable for what its chatbot told a customer. Whatever an interface says is the company’s policy, so a generated answer has to point at the rule it came from.

Typeface

Jake Moffatt asked Air Canada’s chatbot about bereavement fares. The bot told him he could claim the discount after booking. The airline’s policy page said the opposite, and Air Canada refused the refund.

On February 14, British Columbia’s Civil Resolution Tribunal ruled against the airline and ordered it to pay about CA$812. Air Canada had argued that the chatbot was “a separate legal entity that is responsible for its own actions.” Tribunal member Christopher Rivers rejected that, writing that the chatbot “is still just a part of Air Canada’s website.”

That sentence is a design principle, and it came from a tribunal.

One voice, whatever is generating it

A customer reads a website as one thing. The policy page, the booking flow and the little chat window in the corner all speak for the company. Nobody reading a confident answer stops to ask which team built that box, or whether it’s the box allowed to make mistakes.

A customer can’t tell which part of your product is allowed to be wrong, so no part of it is.

That’s an old rule. A wrong price on a product page or a confusing refund screen was always the company’s problem. What’s new is a surface that writes its own sentences, and a company willing to argue the sentences weren’t its own.

Point at the rule

The design fix is plain, and a disclaimer won’t do it. Small print under a chat box doesn’t help someone booking a bereavement fare who trusts the screen in front of them. As Skift’s report notes, the right answer was already on the airline’s own policy page.

What helps is an answer that points at the rule it came from. If the bot says bereavement fares can be claimed later, it should quote and link the line in the policy that says so. If no such line exists, it shouldn’t say it. That also gives the team a test: any answer about money or eligibility that can’t cite a source is a bug.

I learned a version of this at Apple, designing a controller app for people who adjust their own neurostimulation therapy. Each adjustment screen drew the range the clinician allows and marked where you are in it. Nobody would accept a screen that guessed at those limits. A refund policy is lower stakes than a therapy setting, but the principle is the same. When a screen states a rule, it should get it from the rule.

The trade

A bot that cites sources will answer fewer questions, and “I can’t answer that, here’s the policy page” feels worse in a demo than a fluent paragraph. I’d take that trade every time. CA$812 is a small bill. The bigger cost was arguing, in public, that the airline’s website wasn’t really the airline.

Previous← Design for the other 86 percentNextA key is a permanent promise →

© 2026 Nick Sloggett

EmailLinkedIn (opens in new tab)ResumeRSS