Direct answer: if an AI booking assistant invites a UK consumer to choose an ATOL-protected flight or flight-inclusive package, the booking system — not the model — must already show ATOL protection clearly and transparently **in close proximity to the price**, plus the known flight facts the Civil Aviation Authority lists in ATOL Standard Terms 1.4A and 1.4B, and the protecting ATOL holder name and number before the consumer concludes the offer (AST 1.4C). Freeform chat copy is not a substitute for those disclosures.
That is the operator question Kaize is answering here. We are a UK AI product studio for travel and hospitality. This page is about **pre-choice disclosure architecture** for AI-assisted booking flows. It is distinct from when travel AI changes a booking after sale and from Package Travel Regulations 2026 journey changes. Those matter. They are not this problem.
Primary evidence is first-party CAA material: the Official Record Series 3 schedule of ATOL Standard Terms (including AST 1.4A–1.4D as published for the April 2026 update cycle), the CAA’s Compliance with ATOL Standard Term 1 guidance, and CAP3208 on the AST 1.3 advertising clarification effective 1 April 2026. No invented client conversion rates, no fictional ATOL audit outcomes.
Why this is a booking-UI problem, not a prompt problem
ATOL Standard Term 1 is about information consumers must receive before and after sale. AST 1.4A is explicit: wherever a consumer is invited to choose a service that is ATOL protected (or can be combined into one), the consumer must be made aware — clearly, transparently, and **in close proximity to the display of the price** — that the service is ATOL protected. Timing depends on the transaction type: as soon as the consumer is invited to choose a Single-contract Package; as soon as selections mean a Multi-contract Package is being offered; or for Flight-Only, as soon as date, origin and destination are selected.
AST 1.4B adds the known operational facts that must be displayed clearly, transparently and prominently at the same invitation stage when the ATOL holder knows them: flight dates and times; departure and arrival airports (including connecting airports for indirect itineraries); whether the flight is direct or indirect; airline name; whether hold luggage is part of the ATOL protected booking; whether transfers form part of the package; and details including price of extra luggage or transfer options that can also be purchased.
AST 1.4C then requires, as soon as reasonably practicable and in any event before the consumer concludes their offer, clear notice that the service is ATOL protected **and** the name of the ATOL holder (or notified trading name) and its ATOL number. AST 1.4D extends the same duty when travel services are advertised through a third-party website: the required information still has to reach the consumer as soon as they are invited to choose those services, and before contract conclusion.
A large language model that “remembers to mention ATOL” in prose does not satisfy “close proximity to the display of the price” or the structured flight facts list. Those are layout and data-availability requirements on the invitation-to-choose surface.
What changes for chat, agents and assisted booking
Conversational booking compresses the classic funnel. The same legal invitation to choose can appear as a card in WhatsApp, a side panel in an agent desktop, or a tool result rendered beside a chat reply. The channel does not waive AST 1.4A–1.4C. If your AI assistant is the surface that presents price and invites selection, that surface must carry the mandated disclosures — or the selection action must open a controlled booking component that does.
What the assistant may draft
- Explanatory copy that helps a consumer understand options **after** the structured disclosure card is already on screen
- Questions that gather preferences without presenting a selectable ATOL-protected price
- Internal summaries for agents that do not themselves constitute the consumer invitation to choose
What the assistant must not own
- Inventing or omitting ATOL protection status next to a selectable price
- Paraphrasing away airline, airport, timing, luggage or transfer facts that AST 1.4B requires when known
- Presenting a “book this” control before AST 1.4C holder name and number are shown
- Relying on a website footer ATOL statement as a substitute for proximity-to-price disclosure at the moment of choice
That split matches how Kaize thinks about controlling AI agents that access booking systems: the model assists; the system of record and compliance surfaces remain deterministic.
Build the disclosure card as a product component
Treat AST 1.4A–1.4C as a booking-component contract, not a content guideline.
- **Price proximity:** ATOL-protected status must sit next to the price the consumer is invited to choose — not three scrolls away in chat history
- **Known-facts binding:** populate AST 1.4B fields from GDS/NDC/PMS/package APIs; if a field is unknown, do not invent it, but do not hide fields you already know
- **Holder identity before offer conclusion:** ATOL holder name/trading name and ATOL number must appear before the consumer completes the offer path (AST 1.4C)
- **Third-party surfaces:** if you sell via a partner site or embedded widget, AST 1.4D still requires the same information to reach the consumer at invitation to choose
- **Agent and AB members:** holders remain responsible for ensuring agents and Accredited Body members present the same information
Wire the component into every path that can create a licensable invitation: classic web checkout, mobile web, in-app chat with selectable offers, agent-assisted screen share, and any tool-calling agent that returns bookable offers to a UI.
Advertising is adjacent — do not confuse it with choice disclosure
CAP3208 clarifies ATOL Standard Term 1.3 on advertising ATOL-protected products, with effect from 1 April 2026. That is about how ATOL protection is referenced when you advertise or promote to UK consumers. It is related compliance work for marketing and paid media teams. It does not replace AST 1.4A–1.4C on the booking invitation itself. An advert that says “ATOL protected” still leaves you needing proximity-to-price and flight-fact disclosure when the consumer is invited to choose a specific service.
How this fails when AI is bolted on
The failure mode looks like other travel AI that passes testing and breaks in production: the demo chat books a scripted package with perfect ATOL wording; production returns partial NDC offers, missing luggage flags, or partner widgets that show price without the protection line. Or the model generates a confident “this is ATOL protected” sentence while the selectable price card has no protection marker at all.
Instrument the booking UI, not the prompt log. Log whether the disclosure component rendered with protection status, holder identity, and which 1.4B fields were known versus unknown at invitation time. If those events are missing, you do not have evidence of compliance — you have a transcript.
What Kaize will and will not claim
This article is systems and product guidance for UK travel operators, OTAs, agents and travel-tech teams implementing AI-assisted booking. It is not legal advice, not a CAA endorsement, and not a claim that Kaize has audited any named ATOL holder. It does not invent client booking volumes, conversion lifts or enforcement outcomes.
If you want a structured review of where AI belongs in booking journeys — and which disclosures must stay deterministic — start with Kaize’s AI Opportunity Review.
FAQ
Can we put ATOL information only in the final terms checkbox?
AST 1.4A requires awareness in close proximity to the price when the consumer is invited to choose the service — earlier than a late terms checkbox. AST 1.4C still requires protection status plus holder name and number before the offer is concluded. Terms text alone is not the proximity-to-price control.
Does a chat summary of the itinerary satisfy AST 1.4B?
Only if the required known facts are displayed clearly, transparently and prominently at the invitation-to-choose stage. A buried conversational paraphrase is a weak substitute for a structured offer card bound to booking data.
What if our AI suggests flights before price is shown?
Browsing without a selectable price is different from inviting the consumer to choose a priced ATOL-protected service. The moment you attach a selectable price (or equivalent choice control) to an ATOL-protected or combinable service, AST 1.4A’s proximity requirement applies.
Is this legal advice?
No. ATOL compliance remains with your ATOL accountable person, compliance owners and counsel. This page explains how AI booking UIs interact with the published Standard Terms so product and engineering teams do not treat disclosure as optional generated text.