Hotel voice AI reservations with PMS integration: dates, totals and policy aloud

What it is

A reservations agent answers the hotel's booking line, works out whether the caller wants a new stay or a change to an existing one, resolves the dates aloud, checks live availability and rates in the property-management system, quotes the total for the chosen rate plan including taxes and fees as the PMS computes it, reads back and attaches the loyalty number, records requests, speaks the cancellation policy, and writes the reservation. For an existing booking it matches the confirmation number and the name before it discloses anything, then changes the same record. The guarantee goes by secure link; the agent never hears a card number.

The call runs three to five minutes when it goes well. The risk sits in four turns. Dates: "next weekend" has to become two calendar dates in the agent's mouth before anything is checked. Money: the total must be the PMS's total, in words, including the fee the guest will otherwise meet at check-out. Identity: a confirmation number is not a password. Policy: the cancellation terms for the chosen rate must be spoken before "confirmed", because that is the moment the dispute would start.

Independents call this an AI reservations agent or AI phone agent for the hotel. Groups call it voice reservations automation and judge it on rate integrity and loyalty attachment.

Who buys it

• Independent hotels and small groups where the front desk is the reservations department and the phone loses to the guest at the counter.
• Management companies and brands replacing or supplementing a central reservations office, who need rate and policy consistency across properties and a loyalty number on every booking.
• PMS and guest-messaging customers choosing between a bundled agent and a standalone product, who should run both on the same demo script.

Budget owner: the general manager at an independent; the head of revenue or distribution in a group, with the PMS administrator signing off on the integration and the loyalty team on the member flow.

KPIs

Sample fifty phone quotes against the PMS and count date corrections for one month before you deploy. Then track booking containment, rate and total accuracy, date accuracy, identity-gate compliance on modifications, policy spoken before confirmation, and voice-to-voice latency on the turns that read the PMS or write the reservation.

Two traps. Containment that rises because the agent books whatever it hears will show up as date corrections and rate disputes a week later; read them together. And a total that is right because the demo property has no fees is not a test; put a resort or service fee on the sandbox.

Demo script

Run the full script from the demo guide. The condensed version, with the traps that separate a product from a demo:

1. Greeting. Pass: hotel name, AI disclosure, recording notice, and "new stay or changing one?"
2. Ambiguous dates. Ask for "two nights next weekend, a king room, arriving late". Pass: it names both calendar dates and the check-out day and confirms two nights before checking. Fail: it checks availability without saying the dates.
3. Interruption during rates. While it reads the two rate plans, cut in with "the flexible one". Pass: it stops mid-sentence and proceeds with the flexible rate.
4. Loyalty read-back. Give a member number. Pass: digit by digit, matched to the profile, name confirmed, then the member rate applied.
5. Party change. Switch to a family: "two adults, two kids, same weekend, connecting rooms and a cot". Pass: connecting availability checked in the PMS, the cot recorded, children's ages asked if the rate depends on them.
6. Total with taxes and fees. Ask "what's the total with everything?" Pass: the PMS total including taxes and the service or resort fee, in words, per room and overall. Fail: a room rate only, or an agent-computed sum.
7. Eight seconds of silence after the total. Pass: one short prompt, then an offer to hold the rooms or text the quote. Fail: a countdown or a hang-up.
8. Modification without identity. Switch to an existing guest and read a confirmation number with pauses. Pass: read back, name asked, nothing disclosed until both match, then the existing booking is changed. Fail: stay details on the number alone, or a second booking created.
9. Out-of-scope wanderer. Mid-booking ask about visas, the best restaurant in town, a friends-and-family rate and whether you are quieter than the hotel across the road. Pass: visa declined with a pointer to official sources, restaurant answered from your concierge data only, no such rate, no comparison, back to the booking.
10. Policy and write. Say "book the flexible rate". Pass: the cancellation policy for that rate spoken, dates, room, rate, requests and loyalty number restated, a plain yes, the reservation in the PMS, the guarantee link in the message log. Then "can I give you my card?" Pass: declined per your rule.

Score each trap pass or fail. A booking confirmed without the policy, details disclosed before the name matched, an invented discount, or a card number requested is a hard stop.

Compliance notes

The booking call is inbound and outside the TCPA consent rule in the United States; confirmation texts and callbacks are outbound contacts that need prior express consent captured on the call, and anything that counts as a solicitation sits inside the 8 a.m. to 9 p.m. window in the guest's local time. Recording is all-party consent in roughly a dozen states, so announce it. Quoting a total without the resort fee is a consumer-protection problem before it is a voice problem; the PMS total is the fix. In the United Kingdom, recording is personal-data processing under UK GDPR and the agent should say so; a later marketing call needs specific prior consent under PECR Regulation 19. In the European Union, recording needs a GDPR lawful basis and notice, and the AI Act's Article 50 duty to tell callers they are talking to an AI applies from 2 August 2026; many brands require EU hosting as a procurement condition. In Japan, recordings are personal information under the APPI, the purpose of use must be stated, and cross-border transfer requires informing the guest about the destination country; polite register is expected throughout. In Singapore, recording is personal-data collection under the PDPA and the purpose must be notified; in the Philippines, recording without all-party consent is a crime, so announce it. In Australia, state surveillance-devices laws differ, so announce recording; any promotional callback sits inside telemarketing hours of Monday to Friday 9 a.m. to 8 p.m. and Saturday 9 a.m. to 5 p.m. Informational, not legal advice; the compliance rows on this page carry the sources.

Build or buy

Buy if you run a mainstream cloud PMS; the bundled and integrated products have done the availability, rate-plan and modification plumbing, and your job is to break them on the script. Consider a platform or a build if you run a central reservations office with custom rate logic, group blocks and a loyalty programme whose rules change what the agent may offer. In both cases the acceptance test is the same: dates said aloud before availability, the PMS total with fees, nothing disclosed before the name matches, and the cancellation policy spoken before the word "confirmed".