Notes

Your chatbot's answer is your company's promise

For heads of customer service, travel, banking, and e-commerce operations, and the risk and legal teams responsible for what AI agents tell customers and who stands behind it.

GembaOS is a zero-trust governance runtime for enterprise AI agents: policy-decided access, single-use clearance tokens bound to exact parameters, and accountable human approvals, running on-premises or in a private VPC.

This article examines the simplest way an AI agent can inflict severe financial and legal damage on an enterprise without touching a single production database: by stating an unauthorized commitment that the law subsequently forces the company to honor.

In November 2022, a passenger visited Air Canada’s website to book flights following the passing of a family member. Seeking clarification on bereavement fare policies, the passenger consulted the airline’s official AI-powered customer service chatbot.

The chatbot provided clear, plausible, and reassuring advice: the passenger could purchase standard full-price tickets immediately and submit an application for a retroactive bereavement refund within 90 days. Relying on this explicit instruction, the passenger purchased the tickets.

When the passenger subsequently submitted the refund claim, Air Canada rejected it. The airline’s actual, static policy stated that bereavement rates could never be claimed retroactively once travel had occurred. The passenger filed suit with the British Columbia Civil Resolution Tribunal.

Air Canada’s legal defense was striking: the airline argued that the chatbot was “a separate legal entity that is responsible for its own actions” and that the customer should have cross-referenced the static policy page elsewhere on the site.

The tribunal rejected this argument in its entirety:

  1. No separate legal existence: An enterprise chatbot is not an independent contractor or third party. It is a direct digital representative of the brand.
  2. Duty of care: The enterprise owes consumers a duty of care regarding all representations made across its official touchpoints.
  3. Negligent misrepresentation: Holding the airline liable, the tribunal ordered Air Canada to pay damages and costs.

While the financial damages in this initial case were modest, the precedent was seismic: what an AI agent tells a customer constitutes a binding representation by the enterprise.

Rebooking after flight disruption, fee waivers, compensation following delivery delays, goodwill vouchers, and discount matches—these represent the highest-volume inquiries in enterprise customer support.

Because modern LLMs are trained to be helpful, agreeable, and persuasive, they naturally generate fluent, empathetic, and contextually plausible promises. When an unconstrained conversational model is deployed to front-line customer service, a dangerous illusion is created:

DimensionUnconstrained ChatbotGembaOS Governed Architecture
Official Customer ResponseFreeform text generated spontaneously by the modelCanonical wording derived from verified corporate policy rules on a shared work item
Policy InquiriesThe model’s probabilistic recall of internal documentsExact quotes from verified reference standards, or automatic escalation to a human representative
Financial CommitmentsDirect promises made in conversational chat (“We will refund $200”)Separated from chat: an approval request requiring human sign-off before a clearance token can issue
Post-Incident AuditEphemeral chat transcript with no legal accountabilityWORM audit log recording the proposal, the approver, the verified policy, and the clearance token

Three architectural rules before an agent speaks to customers

To protect against misrepresentation liability, enterprises must implement three structural controls:

1. Official commitments are actions, not prose

A refund, compensation voucher, or policy exception must never be promised within the conversational chat thread. The conversational agent has zero transactional authority. It can draft a structured proposal, but that proposal remains inactive until a designated human supervisor cryptographically signs the authorization.

2. Verified policy text over generated summaries

Where customer questions touch upon legal terms, cancellation rights, or eligibility criteria, the agent must not improvise explanatory prose. Official determinations must cite canonical policy blocks directly approved by compliance and legal teams.

3. Structural separation of duties

The system that talks to the customer must not be the system that executes financial payouts. If a customer is eligible for a refund, the front-line agent issues an intake ticket. The governance runtime routes that ticket through the approval chain, validates real-time account balances, and executes the refund via single-use clearance tokens only after human sign-off.

Summary

The lesson of Moffatt v. Air Canada is clear: disclaimers and terms-of-service footers cannot protect a company when its AI agent makes an explicit representation to a customer.

An AI agent’s explanation must never be allowed to turn into an accidental promise. By stripping conversational models of execution authority and enforcing human-signed clearance tokens for every financial commitment, GembaOS ensures that companies remain in complete control of their promises and their liabilities.

Explore live scenarios

See how GembaOS enforces governed financial actions:

Questions this note answers

What did the tribunal decide in the Air Canada chatbot case?

The chatbot told a customer that a bereavement fare could be claimed retroactively after travel, directly contradicting the airline's official policy. The tribunal found negligent misrepresentation, ruled that the airline is fully liable for all information on its digital properties regardless of format, and awarded damages to the passenger.

Does placing a disclaimer under the chat window solve this liability?

No. A disclaimer ('AI may make mistakes') merely warns users of potential inaccuracy; courts have established that it does not insulate an enterprise when a customer reasonably relies on official brand communication. The remedy is structural: preventing conversational agents from holding direct execution authority.

How does GembaOS prevent an agent from making unauthorized promises?

GembaOS enforces strict separation between communication and execution. Official responses on a customer ticket are derived from verified policy text rather than freeform generation. Furthermore, any financial movement (refunds, goodwill vouchers, fare waivers) cannot be triggered through chat; it requires an approval request, human sign-off, and a single-use clearance token.

Sources

As of September 2026 GembaOS holds no certification; the control mappings on this site are self-assessed, not audited. GembaOS is in its design partner stage. Read about the design partner program.

Last updated: · GembaOS v0.2