Hotel AI can assist with booking changes and cancellations when it verifies the requester, retrieves the booked terms, checks current availability and charges, and applies the required approval. It should explain the proposed change before saving it. A cancellation request, a cancelled reservation, and an issued refund are separate states.

Start from the existing reservation

A guest may refer to a booking made through an OTA, a travel agent, a corporate agreement, or directly with the hotel. Identify the correct record and channel before describing what the hotel can change. Do not replace the booked conditions with a general policy copied from today's website.

Oracle's interface documentation shows that integrations can exchange reservation information and supported updates. The exact amendment actions remain connector-specific; a vendor should demonstrate them for your configuration.

Use a two-stage conversation

First, prepare the proposal: current stay, requested stay, available room or package, new total, difference payable or review required, and applicable conditions. Second, obtain explicit acceptance and perform the authorized change. If the proposal expires or availability changes, prepare it again.

Do not treat “Can I move to Saturday?” as unconditional permission to charge a new amount. The guest is asking a question. Show the consequence before committing.

The change-control table

Evidence needed for common booking changes
Request	Check first	Confirm after saving
New dates	Availability, rate difference and booked conditions	Arrival, departure, amount and reservation status
Extra guest	Occupancy rules and approved package pricing	Guest count and accepted total
Room upgrade	Available category and approval requirements	Selected category and any accepted charge
Cancellation	Requester authority, channel and cancellation terms	Cancellation record and any separate financial review
Refund enquiry	Verified payments and authorized decision	Actual refund status, not an assumed promise

Protect against an interrupted update

A change may save even if the response is lost. When the guest repeats the request, inspect the current booking before applying it again. Do not create another reservation simply because the conversation does not contain a confirmation message.

Retain the before-and-after record, the accepted proposal, and who or what authorized it. An operator should be able to understand the decision without reconstructing it from scattered messages.

Do not let cancellation silently settle the books

Cancelling inventory is not the same as deciding what happens to completed payments. Deposits, penalties, credits, and refunds require the hotel's financial process. Keep the guest informed about the actual status and send unresolved financial questions to the authorized team.

The folio review guide addresses why AI should identify discrepancies without inventing balancing entries. The payment reconciliation guide explains how to distinguish payment and reservation evidence.

Design for clear confirmation and correction

W3C's forms guidance recommends understandable feedback and opportunities to confirm or correct input. In conversation, the equivalent is a concise change summary followed by explicit acceptance and a verifiable result.

Test a date correction, an unavailable upgrade, a repeated cancellation, a wrong-property booking reference, and an unauthorized caller. Each should produce a useful response without bypassing permissions.

Start with Hotelary's reservation overview and the WhatsApp booking article. Ask which amendments are supported and which remain staff-assisted. A safe assistant can say a change needs review; it should never convert uncertainty into an irreversible commitment.

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.