Direct answer: before a UK travel or hospitality business lets an **AI booking assistant, chat checkout or voice agent** bind a consumer on a phone, web, app or messaging channel, regulation 13 of the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 requires the trader to give or make available the **Schedule 2** information in a clear and comprehensible manner appropriate to that channel — **before the consumer is bound**. Where the contract is concluded by electronic means and creates a payment obligation, regulation 14 adds a second hard gate: key Schedule 2 facts must be shown **directly before the order**, and the order control must be labelled so the consumer **explicitly acknowledges an obligation to pay**. An agent that “confirms” a hotel night, car hire day, leisure experience or non-package travel service without that stack is not clever conversion. It is a distance-selling control failure.
That is the operator question Kaize is answering here. We are a UK AI product studio for travel and hospitality. This is **not legal advice** and not a substitute for reading the live SI text, GOV.UK distance selling guidance, CAA consumer-law guidance for flights and holidays, or counsel for your product mix. It is a **control-stack** article: what must already be true on the distance channel before AI is allowed to complete a consumer sale. It sits beside — and does not replace — our CMA AI-agents consumer-law controls, our Consumer Rights Act unfair-terms notices, our DMCC drip-pricing total-price controls, our PTR insolvency cover gate, and our ATOL AST-14 booking-assistant disclosure. This article is narrower: **CCR 2013 pre-contract information (and honest cancellation-status disclosure) must be live** before the AI may bind the consumer on a distance contract that the Regulations actually cover.
Why travel teams keep getting CCR wrong when they add AI
Most UK travel operators already have a website checkout that legal reviewed years ago. The failure mode in 2026 is not “we have no T&Cs”. It is that a **generative booking assistant** can reach the same “confirm and pay” state through WhatsApp, an in-app concierge, a voice IVR, or a multi-turn web chat — **without replaying the Schedule 2 surface** the classic checkout showed. Regulation 13 is medium-agnostic for distance contracts: the information must be given or made available in a way **appropriate to the means of distance communication used**. If the means is a chat bubble with limited space, regulation 13(4) still requires a core set of Schedule 2 facts on that means, with the rest provided another appropriate way — not “buried in a PDF after charge”.
Three scope facts operators must encode before the model is allowed near a pay button:
- **Packages are largely outside CCR** — regulation 6 excludes contracts within the scope of the package-travel regime (now the UK Package Travel and Linked Travel Arrangements Regulations). Package sales need the PTR / ATOL stack we cover elsewhere, not a pretend 14-day CCR cooling-off story.
- **Passenger transport cancellation rights are carved out of Part 3** — regulation 27(2)(c) means the CCR 14-day cancel right does not apply to passenger transport services (GOV.UK lists bus, train and flight tickets among the exclusions).
- **Date-specific accommodation, vehicle rental, catering and leisure often have no CCR cancel right** — regulation 28(1)(h) excludes those services when the contract provides for a **specific date or period of performance**. Schedule 2(o) still expects the trader to tell the consumer clearly when they **will not** benefit from a right to cancel.
So the AI control problem is not “always offer 14 days cancel”. It is: **classify the product**, surface the **correct** pre-contract facts, and **never invent a cooling-off right** the Regulations do not give — or hide the absence of one until after payment.
What Schedule 2 actually demands before the consumer is bound
Schedule 2 is the information list for distance and off-premises contracts under regulations 10 and 13. For an AI-mediated travel sale, the high-risk fields are not academic. They include, among others: the **main characteristics** of what is being sold; the trader’s **identity and contact details**; the **total price inclusive of taxes** (or how price will be calculated); **additional delivery or other charges**; **payment, performance and timing** arrangements; the trader’s **complaints** policy; and — critically — either the **cancellation conditions** where a right exists, or clear information that the consumer **will not benefit from a right to cancel** (or the circumstances in which that right is lost).
Regulation 13 also requires a **cancellation form** (Schedule 3 Part B) where a right to cancel exists. If your AI is selling a product that **does** attract the 14-day right (for example certain open-dated or non-date-specific services — classify with counsel), the form is not optional chrome. If your AI is selling a Friday-night hotel stay or a Saturday zip-wire slot, the correct control is usually **Schedule 2(o) honesty**, not a fake cancel button that creates a chargeback later.
The electronic-means pay gate (regulation 14)
When a distance contract is concluded by electronic means and places the consumer under an obligation to pay, regulation 14 requires the trader to make the consumer aware, in a clear and prominent manner and **directly before the consumer places the order**, of Schedule 2 paragraphs (a), (f), (g), (h), (s) and (t) — characteristics, total price, additional charges, subscription-style cost information where relevant, duration, and minimum obligations. The consumer must **explicitly acknowledge** that the order implies an obligation to pay. If the order is placed by activating a button or similar function, that control must be labelled only with **“order with obligation to pay”** or a corresponding unambiguous formulation. If paragraphs (3) and (4) are missed, **the consumer is not bound** by the contract or order.
For AI product teams this is a UI and state-machine rule, not a prompt suggestion. A chat turn that says “Shall I book it?” and then charges a card when the guest types “yes” is still an electronic order. The pay acknowledgement and the labelled confirm control must be first-class artefacts in the booking state — the same discipline we argue for total-price honesty under DMCC drip-pricing controls and for unfair-term clarity under the Consumer Rights Act article.
The six gates before AI may complete a UK distance travel sale
Gate 1 — Product classification: CCR, PTR package, or passenger transport
Before any generative turn can reach “confirm”, classify the basket: flight-inclusive package / linked travel arrangement (PTR + ATOL path), passenger transport ticket, date-specific accommodation or leisure, vehicle rental, or another distance service that may still attract CCR cancellation. Gate 1 fails if the assistant uses one generic “your statutory cancel rights” blurb for ATOL packages, scheduled flights and Friday hotel nights alike.
Gate 2 — Schedule 2 payload is assembled from system-of-record fields, not model prose
Build a structured pre-contract object from PMS/CRS/pricing/tax services: main characteristics, trader identity, total price with taxes, additional charges, performance dates, complaints route, cancel-status flag. The LLM may render that object into plain language; it must not invent missing fields. Gate 2 fails if price, dates or trader identity can be hallucinated when a backend field is null.
Gate 3 — Channel-appropriate disclosure before the consumer is bound
On web checkout, show the Schedule 2 surface before the labelled pay control. On chat or voice with limited space, surface the regulation 13(4) core set on-channel and link or deliver the remainder on a durable medium **before** bind. Gate 3 fails if Schedule 2 appears only in a post-purchase email the guest sees after the card is charged.
Gate 4 — Cancellation status is truthful for travel exceptions
If Part 3 cancellation does not apply (passenger transport under regulation 27(2)(c); date-specific accommodation, vehicle rental, catering or leisure under regulation 28(1)(h); packages excluded under regulation 6), the assistant must state that clearly under Schedule 2(o) rather than offering a fictional 14-day cooling-off. If a right **does** exist, supply conditions, time limit, procedures and the Schedule 3 form. Gate 4 fails on either false hope or silent omission.
Gate 5 — Regulation 14 pay acknowledgement is a hard stop in the state machine
No card capture, virtual card, wallet charge or “book on account” confirmation until the consumer has seen the required pre-order facts and activated an unambiguously labelled pay control (or equivalent explicit acknowledgement on that channel). Gate 5 fails if a model tool can call `confirmBooking()` from a bare affirmative utterance without that acknowledgement artefact.
Gate 6 — Durable confirmation and adjacent consumer-law gates still fire
After conclusion, distance contracts still need confirmation on a durable medium under the Regulations’ confirmation rules — and CCR compliance does not waive CMA agent duties, DMCC total price, ATOL AST-14 where packages apply, or accessibility controls under Equality Act / WCAG. Gate 6 fails if teams treat CCR as the only checklist.
What this is not
- Not a rewrite of DMCC drip-pricing — that article is about total-price presentation under the DMCC regime; this one is the CCR Schedule 2 / Reg 14 bind gate.
- Not a substitute for PTR insolvency naming or UK package travel 2026 journey changes.
- Not ATOL certificate / choice disclosure — see AST-14 and AST-13 ads.
- Not CRA unfair-terms drafting — see CRA unfair terms.
- Not permission to skip PECR rules on follow-up — see PECR soft opt-in.
Operator checklist before go-live
- Product taxonomy maps every AI-sellable SKU to CCR / PTR / passenger-transport / Reg 28(1)(h) buckets with counsel sign-off.
- Schedule 2 structured payload sourced from booking systems; null fields block confirm.
- Channel templates for web, app, WhatsApp and voice implement Reg 13 (and 13(4) limited-space rules).
- Cancel-status copy is binary-tested: right exists → form + procedures; right excluded → Schedule 2(o) statement; never a generic cooling-off myth.
- Reg 14 labelled pay control / explicit pay acknowledgement enforced in code before payment tools run.
- Durable confirmation path tested; CMA, DMCC, ATOL/PTR and accessibility gates remain hard stops.
- Change control: no new AI sales channel without repeating Gates 1–6.
How Kaize frames the build
Kaize designs travel and hospitality AI so **control planes sit in front of models**. CCR 2013 pre-contract information is one of those gates: the distance channel does not call confirm-and-charge until the Schedule 2 artefact and regulation 14 acknowledgement are present on the session — just as we refuse package confirmation until insolvency cover is named or guest chat until EU Article 50 AI disclosure is live. If you want that control stack designed around your PMS, CRS, CRM and messaging stack, discuss a project or see what we build and how travel companies should control AI agents.
Sources for operators to read next: CCR 2013 (SI 2013/3134); regulation 13; regulation 14; regulation 28; Schedule 2; GOV.UK — online and distance selling. Always verify against the consolidated text and your counsel — this page is an operator control framing, not advice.