Hotel booking follow up calls: enquiry to booking

Enquiries arrive, bookings do not

A hotel usually receives far more enquiries than bookings. Someone asks the price, gets an answer, says they will think about it, and disappears. The hotel never learns the outcome: if no booking followed, it is unclear whether the reason was price, dates, room type, or simply a slow reply.

A travel decision is usually made within a day or two, and in that window the customer contacts three or four places. So what a hotel competes on is not only price — it is the speed and clarity of the answer. A precise answer two hours later works better than a discount two days later.

This article covers the call flow from enquiry to booking: the six facts an enquiry needs, how to answer the price question, the follow-up window, a four-situation script, the pre-arrival confirmation touch, and why group enquiries are handled separately.

The six facts in a hotel enquiry

Closing a booking takes six things. If they are not collected on first contact, the answer cannot be precise and the customer moves into «thinking about it».

• Dates: arrival and departure, number of nights
• Guests: adults and children, and the children's ages
• Room type and count: one room or several; whether an extra bed is needed
• Rate conditions: breakfast included or not, and the cancellation terms
• Purpose of travel: leisure, business, an event — this changes the offer
• Arrival time and whether a transfer is needed

The fifth line is often skipped, though it affects the chance of closing directly. A business trip and a family holiday ask different questions: the first needs receipts, invoices and an early checkout, the second needs child policies and distances.

Having these six on the enquiry form helps, but in practice some customers fill the form halfway or simply call. So the script's job is to complete the empty fields rather than ask all six from scratch. If the form already carries dates and guest count, the call starts at room type and rate conditions — which takes two minutes out of the conversation.

The price question: one number is not enough

A hotel's price depends on the dates, the room type and the rate conditions. Answering «how much per night?» with a single number is either wrong or an invitation to comparison — and in both cases the booking is lost.

1. 1The price is given with its conditionsWhich dates, which room, breakfast or not, and the cancellation terms. Those four details fit in one sentence and take the customer out of comparison, because they now know what they are comparing.
2. 2Cancellation terms are explained plainlyA freely cancellable rate costs more; a non-refundable rate costs less. Giving the customer that choice removes much of the price objection.
3. 3An alternative is kept readyIf the requested date or room type is unavailable, the conversation does not end: a nearby date, a different room or a different rate is offered.

The third step closes the most loss. A call that ends with «we have nothing on those dates» sends the customer to a competitor; the same sentence followed by one alternative keeps part of the booking.

The follow-up window

Answering an enquiry is not one touch. The model that works has three, and each has its own purpose.

• First 30 minutes: the answer to the enquiry — price, conditions and availability together
• After 24 hours: if there was no reply, one touch — are the dates still current
• After 72 hours: a final touch, with an alternative date or rate
• After that: the enquiry is closed and the customer joins the seasonal campaign list

Continuing past the third touch is unproductive: the travel decision has usually been made. Recording why an enquiry closed is productive, though — at the end of a season the distribution of those reasons explains more than the rate card does.

The script: four situations

A follow-up call is short and works without sales pressure. The goal is not to speed the decision up but to complete the information the decision needs.

1. 1The dates still standAvailability is confirmed, the rate conditions are repeated and the booking is made. Result: a confirmation message and a pre-arrival touch plan.
2. 2The dates changedA fresh check on the new dates. This is the most common case, and closing it as a lost enquiry is a mistake.
3. 3They booked elsewhereAsk why: price, location, conditions. The customer is lost and the information remains — and that information is what seasonal pricing decisions need.
4. 4It is a group or event enquiryThe call goes to a salesperson. Group terms, event space and corporate invoicing are not the subject of an automated script.

After the booking: two touches before arrival

A hotel's loss is not only in bookings that never close — it is also in guests who do not arrive. Part of that is preventable.

• As soon as the booking is made, dates, room type, guest count and rate terms are repeated back
• One or two days before arrival, a confirmation touch: arrival time, transfer, late check-in
• If a late arrival is mentioned, the front desk is told
• A guest who cancels is asked why, and the reason is recorded
• No-shows stay in their own status — they are a different segment in a later campaign

The second line both reduces loss and creates the natural moment for an extra sale: transfer, breakfast, late checkout. Those offers belong on the confirmation touch; on the first enquiry they only make the conversation longer.

Separating the causes of no-shows matters too. Some are cancelled trips and outside the hotel's control; others come from the guest having booked two places and turning up at one. The confirmation touch reduces the second group, because a call asking for confirmation forces the choice — and the hotel learns about it a day early rather than on the day of arrival.

Limits

Parts of this flow are not automated. Group reservations, event organisation and corporate contract terms come first — there the price is set by individual agreement.

The second is a complaint. A problem raised during or after a stay is not run by a sales script; such a call goes straight to the person responsible.

How contact after a complaint is built is covered separately in the negative review recovery call.

How Vexvon supports this flow

Vexvon's AI voice agent answers and places calls from each company's own scenario, approved information and escalation rules. The parts this flow uses:

• Inbound: time policies and routing rules send a call to the front desk, to sales or to the agent
• The scenario defines the fields to extract: dates, guest count, room type, rate conditions, arrival time
• With webhook tools the agent can read availability and pricing from the company's own system
• Follow-up campaigns are built from a CRM filter; reminders are checked every minute and night hours are protected
• Group and event enquiries are handed to an operator by a condition in the scenario

Turning interest in a tour package into a sale is in travel sales calls, and booking a car in car rental booking calls — the three flows need different data.

Measurement and where to start

Four numbers are enough to follow this flow.

• Enquiry-to-booking rate, measured per channel
• First response time — from the enquiry arriving to the answer
• Share of enquiries lost to availability
• No-show rate — separately for bookings with and without a confirmation touch

The simplest first step: for one week, log every enquiry with the six fields and measure first response time. To build this flow against your own system, get in touch or see the call center page.