AI booking chatbots for hotels, gyms and clinics: disclosure, confirmations and the pay button
What applies to a booking bot
| Step in the chat | Rule | What to do |
|---|---|---|
| Bot greets the visitor | AI Act Article 50(1) and (5) | Say it is an AI, at the latest at the first message |
| Bot quotes price, dates, what is included | Consumer Rights Directive Article 6(1) | Give the main characteristics, total price and cancellation terms before booking |
| Visitor confirms a paid booking | Consumer Rights Directive Article 8(2) | A button or step clearly labelled as an order with an obligation to pay |
| After the booking | Consumer Rights Directive Article 8(7) | Confirmation on a durable medium (an email, not only the chat) |
| Health or treatment bookings | GDPR Article 9 | Ask only what the booking needs |
The AI disclosure
A booking assistant interacts directly with customers, so Article 50(1) applies. Booking bots often speak in the voice of the front desk ("Hi, it's Anna at reception"), which is the set-up the Article is aimed at. A named assistant is fine if the first message says it is an AI:
"Hi, I'm Lakeside Hotel's AI booking assistant. I can check availability and book a room, or put you through to reception."
The disclosure wording guide has more options. For phone booking lines, see the AI receptionist guide.
When the bot takes a paid booking
Most chat bookings for hotels, classes or treatments are distance contracts concluded by electronic means. Article 8(2) of the Consumer Rights Directive then sets two requirements.
Right before the order, the trader must show "in a clear and prominent manner" the main characteristics of the service, the total price, and the duration and minimum duration of the contract where relevant (points (a), (e), (o) and (p) of Article 6(1)).
At the order, the consumer must "explicitly acknowledge" that the order implies an obligation to pay. Where a button or similar function places the order, it must be labelled "only with the words 'order with obligation to pay' or a corresponding unambiguous formulation". The sanction is in the same paragraph: if the trader has not complied, "the consumer shall not be bound by the contract or order".
In a chat, typing "yes" in reply to "Shall I book it?" is a weak way to meet this. The safer pattern is to hand over to a summary screen or card with the price and a button such as "Book and pay EUR 180" or "Confirm booking, payment due", not a free-text "yes". Many booking engines already provide that step; the risk is a custom bot that skips it.
Free bookings (a free table reservation, a free consultation) do not place the consumer under an obligation to pay, so the button rule does not bite. A no-show fee does change that, so check whether one applies.
No 14-day withdrawal for most dated bookings
Article 16(l) excludes the right of withdrawal for "the provision of accommodation other than for residential purpose, transport of goods, car rental services, catering or services related to leisure activities if the contract provides for a specific date or period of performance". A hotel stay, a restaurant table or a fitness class on a set date is covered by that exception.
Two points for the bot:
- The trader still has to tell the consumer before the booking that there is no withdrawal right (Article 6(1)(k)). The bot's summary should say so, together with the business's own cancellation policy.
- The exception does not reach everything a gym or clinic sells. A gym membership or a course of treatments without a specific date is a different contract. Check each product.
What the bot confirms binds the business
When a bot tells a customer "your room includes breakfast" or "you can cancel free until 24 hours before", that is the business speaking. A Canadian tribunal held Air Canada responsible for a refund policy its website chatbot had described wrongly (Moffatt v. Air Canada, 2024 BCCRT 149, reported; not EU law). Under EU consumer law, the pre-contract information the trader must give under Article 6(1), such as the total price and the cancellation terms, forms an integral part of the contract (Article 6(5)), and a misleading answer can be an unfair commercial practice.
Practical limits:
- Prices, inclusions and cancellation terms come from the booking system, not from the model's memory.
- The bot does not promise upgrades, discounts or exceptions that staff have not approved.
- The confirmation email repeats the terms, so the customer and the business have the same record.
- Staff can see the chat transcript when a customer disputes what the bot said.
Clinics and treatments
Booking a medical or therapy appointment can reveal health data. Ask only for what the booking needs (name, contact, appointment type) and leave symptoms to the clinician. The AI receptionist guide covers the health-data and triage points in more detail.
Checklist for a booking bot
- [ ] First message says it is an AI assistant.
- [ ] Price, inclusions and cancellation terms come from the booking system.
- [ ] Paid bookings end with a summary and a clearly labelled pay button, not a typed "yes".
- [ ] Summary says when there is no withdrawal right, plus the cancellation policy.
- [ ] Confirmation sent by email (a durable medium).
- [ ] Bot cannot offer discounts or exceptions on its own.
- [ ] Clinic bookings ask for no more health detail than needed.
- [ ] Transcripts kept for disputes, with a retention period in the privacy policy.
Sources
- Regulation (EU) 2024/1689 (AI Act) on EUR-Lex: Article 50(1) and (5).
- Article 50 text at artificialintelligenceact.eu.
- Directive 2011/83/EU (Consumer Rights Directive) on EUR-Lex, as amended: Articles 6(1), 6(5), 8(2), 8(7) and 16(l).
- Consumer Rights Directive, Article 8 and Article 16 at legislation.gov.uk (EU text as retained in the UK), used for quoting.
- Regulation (EU) 2016/679 (GDPR) on EUR-Lex: Article 9.
- Moffatt v. Air Canada, 2024 BCCRT 149, Civil Resolution Tribunal of British Columbia, reported.