A practical guide / Fonix.AI
Hotel reservations: a practical implementation guide
A worked scenario, illustrated decision review and a practical pilot worksheet.
A hotel receptionist must sell a room that still exists
A hotel AI receptionist can collect dates, guest counts, room preferences and arrival details. The reservation becomes dependable only when those answers are checked against the property's inventory and a reservation reference is returned. Two fluent minutes followed by an overbooking create more work for the reservations desk.
Use this guide to scope a Fonix.AI reservation pilot around one property and one approved room catalogue. The PMS connection, payment process and permitted changes must be agreed for that deployment. This is a booking design, not a claim of a ready-made connector to every hotel system.
Room nights, occupancy and rate plans belong together
Ask for check-in and check-out dates explicitly. A stay from 18 to 20 November uses the nights of the 18th and 19th. Read dates back with the month; “next Friday” can cross a timezone or midnight boundary. Then establish adults, children, accessible-room requirements and whether the caller needs multiple rooms.
A room-type count alone is insufficient. The selected rate may have different meal inclusions, cancellation conditions or occupancy restrictions. Retrieve those terms from the approved source and preserve their version with the quote. Never infer an extra-bed entitlement from a caller's willingness to pay.
Worked example: two rooms and one expiring hold
Consider a fictional property with one family room and two double rooms available. A caller requests two rooms for five adults. The first response should establish the permitted distribution of guests, rather than offer two doubles automatically. If the approved rules permit three adults in the family room, quote that combination and its exact total.
Suppose the system holds both rooms while the guest checks with a colleague. The hold expires before they return. Recheck the inventory and price; an earlier quote does not preserve availability. If only one room remains, explain the changed position and offer a reservations-team callback instead of confirming half a booking as the complete stay.
| State | What the agent may say | Evidence needed |
|---|---|---|
| Search result | These rooms are currently available | Inventory response and retrieval time |
| Active hold | These rooms are temporarily held | Hold reference and expiry |
| Payment pending | Your reservation is awaiting the required payment step | Approved payment/reservation state |
| Confirmed | Your reservation is confirmed | PMS reference and accepted room nights |
Protect the desk from duplicate and ambiguous bookings
Use one enquiry reference across a disconnected call and its callback. When a reservation write times out, look up that reference before sending another write. A second identical booking can consume the final room and make cancellation reconciliation difficult.
Keep special requests separate from guaranteed inclusions. Airport transfers, early check-in and adjoining rooms may require a different owner. Record the requested service, receiving desk and acknowledgement. Avoid collecting card details in a general transcript; follow the property's approved payment channel.
The reservations desk's pilot worksheet
Start with one property, a sanitised room-type catalogue and a reservation-system test account. Have the reservations manager define occupancy limits, hold expiry and who can approve exceptions. Keep payment capture in the property's approved channel.
| Pilot case | Required behaviour |
|---|---|
| Hold expires while the guest decides | Refresh both room nights and rate; retain the old quote as superseded evidence. |
| One room books while the second fails | Report the partial state and involve reservations; do not describe the whole stay as confirmed. |
| Guest changes the number of adults | Re-run occupancy and room allocation before retaining the original price or reference. |
Calculate confirmed-stay accuracy from reservations whose spoken room nights, occupancy and rate match the final PMS record, divided by all calls claiming confirmation. Report requests without confirmation separately so a conservative agent cannot hide missed bookings.
Can we start without a live PMS write?
Yes, as an enquiry-intake pilot. Collect the requested stay and assign a reservations owner, but call the result a request. Move to automatic confirmation only after availability, hold handling and reservation writes are tested together.
Evaluate confirmed stays, not just answered enquiries
Test a sold-out night, a corrected guest count, an expired quote and a timeout after the PMS accepted a booking. For every test, compare the spoken result with the actual room allocation. Measure confirmed reservations per eligible enquiry alongside overbookings, duplicate writes and reservations-team rework. Keep cancellations and payment failures visible rather than removing them from the denominator.
Bring a room catalogue, rate rules and a sandbox reservation flow to review a hotel reservation workflow. For the later attendance step, see appointment reminders; for interrupted human assistance, see warm transfers.
If a guest needs to change their journey as well as their stay, use the separate travel-change intake guide to preserve passenger and segment scope before the travel desk acts.