Hotel booking chatbot: turning enquiries into bookings

Why hotel enquiries don't become bookings

Most written enquiries to a hotel start with the same sentence: «15–20 October, two people, how much?». When the reply takes a few hours, the guest has already booked another hotel or an OTA. Even when a reply comes, it is often incomplete: there is a price, but no room type, no breakfast, no cancellation terms, and the conversation drags on with the next question.

A hotel chatbot can close that gap — on one condition: what it can and cannot confirm must be clear in advance. This article covers the flow from enquiry to booking, the information to collect, the bot's boundary on availability and price, package and group requests, night-time enquiries, a sample conversation and measurement.

The enquiry flow: four questions are enough

Guests don't want to fill in a form. A booking needs four pieces of information, and the bot extracts them from what the guest has already said, asking only for what's missing.

1. 1DatesArrival and departure. If the answer is vague, like «the weekend», the bot suggests specific dates.
2. 2GuestsAdults and children; children's ages if any — price and extra beds depend on it.
3. 3Room type and needsStandard, family, with a view; breakfast; transfer. The bot shows two or three fitting options briefly.
4. 4ContactOn WhatsApp the number is already known; on Instagram and the website, a number or email is asked for to confirm.

Availability and price: the bot's boundary

The biggest risk in a hotel chatbot is saying a room is free when it isn't, or quoting an old price. There are two models, and which one applies depends on the hotel's system.

1. 1With live dataIf the hotel's reservation system is connected by API, the bot can read availability and the price for those dates. Even then, the final confirmation comes from the system, not from the bot's sentence.
2. 2Without live dataThe bot gives the seasonal price range and room types from the knowledge base and passes the request, complete, to reception: «We'll check availability for your dates and send an exact offer within 30 minutes.»
3. 3NeverThe bot does not call an unconfirmed booking «confirmed», does not take a deposit or payment, and does not promise exceptions to the cancellation policy.

Package, group and event requests

• Package (spa, dinner, transfer): the bot gives the contents and price range and records the choice
• Group (5+ rooms): the bot collects dates, room count and purpose and passes it to sales — group pricing is individual
• Wedding, conference, corporate event: initial details and a meeting only; sales prepares the proposal
• Long stay: terms are individual; the bot records the request and hands it over

Night-time and other languages

A large share of hotel enquiries arrive in the guest's time zone, which is the hotel's night, and often in another language. Vexvon detects the language of every message and replies in it; the company can limit the list of supported languages.

• At night: the bot collects the full request and tells the guest when the reply will come
• In the morning: reception sees night requests complete, in priority order
• Language: the reply is in the guest's language, but room names and terms come from approved translations
• Voice notes: transcribed and answered in the same flow

A sample conversation

1. 1Guest, 23:10, WhatsApp«Hi, do you have a room for 17–19 October for two adults and a 6-year-old? Is breakfast included?»
2. 2Bot«Hello! For these dates a family room or a standard room with an extra bed would suit you; breakfast is included in both. This season the family room is 180–220 AZN per night. Shall I check availability and send an exact offer by 10:00 tomorrow?»
3. 3Guest«Yes, the family room. We also need an airport transfer.»
4. 4Bot«Noted: 17–19 October, 2 adults + 1 child (6), family room, breakfast, airport transfer. The offer will reach this number by 10:00.»
5. 5Morning, receptionSees the complete request, checks availability in the system and sends the offer at 09:20.

After the booking

• Before arrival: address, check-in time, parking — from the knowledge base
• Early check-in, late check-out: the bot records the request, reception confirms
• Cancellation and changes: the policy is stated, the action stays with a person
• A follow-up call for unconfirmed requests is a separate process — hotel booking follow-up

Division of work with reception

When the bot goes live, reception's work does not shrink — it changes: the bot takes repeated questions, decisions and confirmations stay with staff. The split should be written down in advance so no request falls between the two.

1. 1The botAddress, check-in time, parking, breakfast, pet policy, price range, collecting the four details of a request — day and night.
2. 2ReceptionChecking availability, the exact offer, booking confirmation, payment, changes and cancellations.
3. 3Sales managerGroups, events, corporate contracts and long-stay requests.
4. 4Duty managerComplaints, problems arising while the guest is in the hotel, emergencies — the bot hands over at once.

At every handover the staff member sees the full request: dates, guests, room, special wishes and the time the bot promised the guest.

What to measure

1. 1Time from enquiry to offerEspecially for night enquiries — the share of promised times actually met.
2. 2Complete-request shareThe share of requests reaching reception with all four details.
3. 3Offer-to-booking conversionBy channel and language — which markets' enquiries turn into bookings most.
4. 4Wrong answersOld prices or rooms that weren't free — each one investigated.

Common mistakes

• Saying «we have a room» without checking the system
• Not updating the price range when the season changes
• Quoting the standard room price for a group request
• Collecting a night request but missing the morning reply time
• Asking for a payment link or card details in chat

Limits

A hotel chatbot does not replace the reservation system. Without a live integration, the bot does not know availability and only collects the request well. Payment, deposits, cancellation exceptions, group pricing and complaints always stay with staff. These limits should be stated openly to the guest — a hidden limit causes more dissatisfaction than a broken promise.

Conclusion: a complete request, an offer on time

The value of a hotel chatbot is not in booking by itself but in getting the enquiry to reception day and night, in the guest's language, complete. An exact offer arriving at the promised time is what turns an enquiry into a booking.

The different flow for travel agencies is in the tourism chatbot, and other industries are in this category. To build your hotel's enquiry flow together, get in touch.

Frequently asked questions

1. 1Can a hotel chatbot confirm a booking itself?Only when integrated with the hotel's reservation system and the confirmation comes from that system. Otherwise the bot collects the request and staff confirm.
2. 2Which channels does it work on?WhatsApp, Instagram, Facebook, Telegram and website chat — all with one knowledge base.
3. 3What is needed to set it up?Room types, seasonal price ranges, included services, the cancellation policy and a reply time for night enquiries.