Most calls reaching a hotel switchboard reduce to three questions: is a room available on these dates, how much is it, what is included. These are formulaic — therefore the best candidates for automation. On one condition: the answer must be correct at that moment.
Why a document is not enough
A price list placed in a knowledge base can be wrong a day later in hospitality. Occupancy changes, rates move by date, minimum-stay rules kick in.
So in hotel deployments the agent must query availability and price live. It takes the question, asks the reservation system, and speaks the answer it gets back. The knowledge base is for things that do not change: location, facilities, pet policy, parking, breakfast hours.
Asking the right question
An availability query is impossible without three facts: check-in date, check-out date and number of guests. Customers rarely provide all three at once.
How the agent collects them defines the quality of the call. Asking one by one ("check-in date? check-out date? how many people?") feels like a survey. The natural approach is to infer what was said and collect the rest in a single question: "I am looking at 15 to 18 August — how many of you will there be?"
Date traps
Date expressions in hospitality are free-form and the agent must translate them correctly:
- "Next weekend" — depends on what day it is today.
- "Three nights from 15 August" — check-out is the 18th, not the 17th. Confusing nights with days produces the wrong query.
- "Over the holiday" — requires knowing public holiday dates.
Defining these three patterns explicitly in the instructions markedly reduces wrong queries.
When quoting a price
A price answer should carry three things together: the amount, what it covers and its validity. "It is 4,200 TL per night, breakfast included, and this rate is valid today" prevents most later disputes.
What the agent must never do is guess a price that did not come back from the query. If the system does not respond, the correct behaviour is "let me check and come straight back to you" and dropping the record to the team.
Who completes the booking
There are two approaches, and the choice depends on the business's appetite for risk:
- The agent informs, a human completes the booking. Safer, especially where payment and cancellation terms are involved.
- The agent creates the booking directly. Faster, but a booking with wrong dates is expensive.
A reasonable middle ground for most hotels: the agent creates an optional hold, a confirmation message goes out, and the booking firms up when the guest confirms.
International guests
The share of international calls is higher in hospitality than in other sectors. A second language is not a luxury here but a baseline requirement. Likewise, time zone differences must be respected in outbound reminder calls.
After the stay
The most neglected use of a voice agent in hospitality is post-checkout: asking about satisfaction, requesting a review, inviting a return booking. These calls are short, single-question and cheap — and their response rates beat first-contact calls.
Tomorrow we move to a neighbouring sector: finding the right tour in a catalogue.