Top agentic AI use cases for travel and hospitality in H2 2026

Rates, content and points ready for booking inside Google AI Mode

On 27 August 2026 Google began rolling out hotel booking inside AI Mode in the US, in English, with ten launch partners including Booking.com, Expedia, Marriott and Hilton; the hotel or booking platform stays merchant of record. NIA checks what AI Mode shows for your properties and keeps the rates, policies and room content it reads accurate.

the workflow, in one room

1. ai teammatespeople
2. TriggerEach week, run the trip questions guests ask through Google AI Mode for each property’s market.
3. Record which properties appear, which booking options are offered and what price and policy are shown.
4. Compare rates, taxes, fees, room descriptions and cancellation terms in Google Hotel Center with the booking engine.
5. Draft fixes to the feed and room content, and check that member and points prices display correctly where the brand runs a loyalty programme.
6. Approved by Distribution managerThe distribution manager approves every change to rates, policies and content before it is pushed.
7. Push the approved changes and re-run the questions to confirm what AI Mode now shows.

Guardrail. Google says the hotel or booking platform remains merchant of record and handles customer service, so every price, cancellation term and promise in the feed is yours to honour.

Recommended in ChatGPT, Gemini and AI Mode trip plans

Booking.com’s 2026 Travel Trends survey of 32,800 travellers found 69% of Gen Z and 64% of millennials use generative AI for travel planning. DRIS runs the trip-planning questions your guests ask across ChatGPT, Gemini, Perplexity and Google AI Mode, records which properties and sources are named, and drafts fixes to the pages and profiles the engines draw on.

the workflow, in one room

1. ai teammatespeople
2. TriggerEach week, run the agreed trip-planning questions by source market and traveller type across ChatGPT, Gemini, Perplexity and Google AI Mode.
3. Record which properties or operators are named, in what order, and which pages, profiles and review sites are cited.
4. Compare with last week and with named competitors to find the questions you are losing.
5. Draft fixes: plain answers on room types, accessibility, parking, family facilities and cancellation, plus profile updates on Google and the OTAs.
6. Approved by Content or SEO leadThe content or SEO lead approves each change and its facts before publishing.
7. Publish, then re-run the affected questions and log whether mentions and citations moved.

Guardrail. Fix the facts on the page rather than writing for a machine, and never publish a claim about rooms, accessibility, prices or awards the property cannot back up.

One all-in price across site, metasearch, ads and messages

Price rules tightened in 2025: the FTC’s fees rule took effect in the US on 12 May 2025 and covers short-term lodging, and the UK’s DMCC Act regime came into force in April 2025, banning drip pricing with fines of up to 10% of global turnover. India’s amended E-Commerce Rules follow from 1 January 2027. The agent audits every place a price appears and drafts fixes for approval.

the workflow, in one room

1. ai teammatespeople
2. TriggerBefore each campaign, crawl the booking engine, landing pages, metasearch feeds, ad copy and email and WhatsApp templates for every displayed price.
3. Flag prices shown without mandatory fees, fees added late in checkout, and paid extras selected by default.
4. Check every sale or was-and-now claim against the price actually charged before the offer.
5. Draft corrected copy, feed values and templates for each market’s rule.
6. Approved by Director of e-commerceThe director of e-commerce approves each fix and the campaign’s price claims before launch.
7. Apply the fixes, re-crawl and keep the audit record as evidence.

Guardrail. From 1 January 2027 India’s amended E-Commerce Rules require e-commerce entities to run a yearly dark patterns self-audit and treat the prior price as the lowest of the previous thirty days.

Direct offers in the EEA now that Booking.com parity is gone

Under the EU Digital Markets Act, hotels on Booking.com in the EEA can set their prices and conditions freely on other channels, including their own site, and a Commission factsheet of 28 September 2026 says outside prices no longer decide Booking Sponsored Benefit eligibility. MIRA plans member rates and direct offers by market, and the revenue manager approves where the direct price sits.

the workflow, in one room

1. ai teammatespeople
2. TriggerEach month, pull rates and availability by channel from the channel manager and the rate shopper.
3. Compare direct, OTA and metasearch prices by market, date and length of stay for EEA properties.
4. Propose member rates, direct-only packages and closed-group offers, each with its expected cost of acquisition.
5. Draft the metasearch, search and email activity that carries each offer.
6. Approved by Revenue managerThe revenue manager approves rate positions and offers before they are loaded.
7. Load the approved rates, launch the activity and report direct share by market.

Guardrail. The DMA freedom applies to Booking.com in the EEA, so check every other OTA contract and market before pricing below an OTA, and show each member rate as an all-in total.

A website booking assistant that says it is AI, for EU guests

From 2 August 2026, Article 50 of the EU AI Act requires AI systems that talk to people to disclose that they are AI, unless that is already obvious. Convexa answers questions on rooms, policies and the area from approved content, says it is AI in its first message and hands over to reservations whenever a guest asks.

the workflow, in one room

1. ai teammatespeople
2. TriggerA visitor opens chat on the website or booking engine.
3. Open with a plain statement that the assistant is AI and that a person is available.
4. Answer from the approved library of room facts, house rules, policies and local information, linking to the room and rate that fit.
5. Hand over to reservations or events, with the conversation attached, when the guest asks for a person or raises a group, wedding or complaint.
6. Approved by Reservations managerThe reservations manager approves the answer library and every change to it before it goes live.
7. Review unanswered questions weekly and add approved answers.

Guardrail. Disclose the AI in the first message for EU guests under Article 50, and never let the assistant invent a price, policy or availability that is not in the approved library.

WhatsApp booking conversations under Meta’s 2025 and 2026 rules

WhatsApp changed twice for travel sellers: per-message pricing from 1 July 2025, with utility messages sent in an open service window charged from 1 October 2026, and terms from 15 January 2026 that bar general-purpose AI assistants while still allowing businesses that use AI to serve their own customers. LIPI runs enquiry and pre-arrival conversations inside those rules, with the CRM lead approving templates.

the workflow, in one room

1. ai teammatespeople
2. TriggerA guest messages on WhatsApp from a click-to-WhatsApp ad, the website or a booking confirmation.
3. Reply within the open customer service window from approved property details, with prices shown as totals.
4. Classify each outgoing template as marketing, utility or authentication, and send marketing only to guests who opted in.
5. Offer a person by chat transfer, phone or email whenever the guest asks or the question falls outside the approved answers.
6. Approved by CRM leadThe CRM lead approves every template, its category and the opt-in wording before use.
7. Log bookings, opt-ins and opt-outs to the CRM and report messaging cost per booking.

Guardrail. WhatsApp’s policy requires opt-in before messaging, honoured opt-outs and a clear path to a person, and Meta’s 2026 terms allow AI that serves your own guests but not a general-purpose assistant.

Consent records for Indian guest data before the DPDP deadlines

India notified the DPDP Rules on 13 November 2025: consent manager registration applies from 13 November 2026 and the core duties, including standalone consent notices, from 13 May 2027. CORA builds a consent record for every guest, enquiry and lead across the booking engine, front desk, WhatsApp and CRM, and the data protection lead approves the notice text.

the workflow, in one room

1. ai teammatespeople
2. TriggerMap every point that collects guest or lead data: booking engine, front desk, WhatsApp, event enquiry forms, loyalty app and OTA imports.
3. Flag forms that bundle marketing consent with booking terms or collect more than the stated purpose needs.
4. Draft standalone notices that list the data, each purpose and how to withdraw consent or complain.
5. Add consent fields with timestamp and purpose to the CRM, and suppress contacts without a valid record.
6. Approved by Data protection leadThe data protection lead approves the notice text and consent fields before they go live.
7. Report weekly on contacts with valid consent by purpose, and process withdrawals.

Guardrail. Rule 3 of the DPDP Rules 2025 requires clear, standalone notices that name the data and its purposes and give a simple way to withdraw consent, from 13 May 2027.

Trip bundles and add-ons checked against the revised EU package rules

The EU’s revised Package Travel Directive, (EU) 2026/1024, entered into force on 28 May 2026: it removes linked travel arrangements, simplifies the package definition and gives member states twenty-eight months to transpose, with full application expected from 2029. FOLIO reviews every bundle and cross-sell flow and drafts the changes for the compliance lead to approve.

the workflow, in one room

1. ai teammatespeople
2. TriggerList every bundle, dynamic package and cross-sell flow on the site, in apps and in post-booking emails.
3. Mark which flows sell more than one travel service for the same trip, and how the traveller is invited to add each one.
4. Compare each flow with the revised package definition and the new complaint-handling duties.
5. Draft changes to information pages, booking flows and emails, with owners and dates set against each national transposition timeline.
6. Approved by Compliance leadThe compliance lead approves the changes and the timeline before build starts.
7. Track each change to release and keep the record for regulators.

Guardrail. The revised directive requires organisers to acknowledge complaints within seven days and answer within sixty, and national laws set the final detail, so confirm each market with counsel.

Frequently asked questions