Stop hotel AI from quoting outdated policies by assigning one approved source to each policy, recording its effective dates, and defining what happens when sources disagree. Updating a prompt is not enough if old PDFs, website pages, and staff notes remain available. A conflict should produce clarification or human review, not a guessed compromise.
Why more documents can make the answer worse
A resort may have a current breakfast schedule, an old wedding brochure, and a seasonal package PDF. All can contain plausible answers to the same guest question. If the assistant retrieves the wrong document, fluent language makes the mistake harder to spot.
The NIST framework provides general risk-management context. For hotel operations, the practical response is a policy register with explicit ownership and an answer test for every meaningful change.
Create a policy register
| Field | Example of what to record | Why it matters |
|---|---|---|
| Property | The hotel to which the policy applies | Prevents another property's rule being reused |
| Policy type | Breakfast, pets, parking, cancellation, arrival | Creates one clear owner per fact |
| Effective period | Start and end dates where relevant | Separates current and seasonal rules |
| Scope | Rate plan, booking channel or guest eligibility | Prevents a package exception becoming a general promise |
| Approver | Named operational owner | Creates accountability for updates |
| Fallback | Clarification or escalation route | Keeps missing facts from becoming invented facts |
Distinguish policy from a reservation's contract
A hotel's current cancellation policy does not automatically replace the conditions attached to an existing reservation. The assistant must identify whether the guest is asking about a new booking or their confirmed stay. For amendments and refunds, retrieve the booked terms and obtain the required authority.
Likewise, a general “breakfast available” statement does not establish that breakfast is included in every rate. The package-quote guide explains how to keep inclusions attached to the selected offer.
Make a change through one controlled process
When breakfast hours change, update the approved record, identify affected website and brochure content, and retire superseded material from the active knowledge set. Keep an archive for audit purposes without allowing it to compete with current instructions.
Test a new enquiry, an existing conversation, and a future-dated stay. A conversation that began yesterday should not indefinitely retain yesterday's operational facts. Conversely, a policy becoming effective next month should not be applied to this morning's service.
What the assistant should do with a conflict
Suppose a package says dinner is included while a general page lists dinner as an extra. The assistant should resolve the selected package and stay dates before answering. If the booking data does not settle the conflict, it should identify the uncertainty and send it to the reservations team.
Do not instruct the model to always choose whichever source appears most recent. A newly uploaded general document can still be less authoritative than a valid booked contract. Precedence must account for scope as well as date.
Measure the maintenance burden
Track outdated answers, unresolved conflicts, and how long policy changes take to reach guest-facing replies. Review recurring questions that lack a source. An assistant should help reveal gaps in the hotel's information, but the hotel must approve the replacement fact.
Mews' Smart Tips announcement describes bringing guest context together for staff. It illustrates the value of organized information, not proof that any AI system can reconcile contradictory policies unaided.
Use the reservations training guide for initial preparation and Hotelary's WhatsApp AI overview for product context. Maintain the register alongside your acceptance tests, so a policy edit results in verified answers rather than an untested upload.
Sources and further reading
Sources reviewed on September 14, 2026. Check current vendor terms and policies before implementation. Examples and checklists are editorial guidance unless explicitly identified as reported research.
- NIST framework — nist.gov
- Mews' Smart Tips announcement — mews.com
