Hotel booking enquiries on WhatsApp: what to ask before quoting

Begin with arrival and departure dates. “This weekend” can mean different nights, particularly when someone is travelling across time zones. Repeat the dates clearly rather than inferring them from the day of the message.

Illustrative reply: “Which dates would you like to check in and check out? How many guests will be staying?”

Read the message before asking. If the guest already supplied dates and a guest count, acknowledge them and ask only for the missing detail. A conversation that starts by ignoring the answer feels broken even when the questions are sensible.

Ask about the number of rooms when the guest count could mean different arrangements. Two colleagues may want separate rooms. A family may need an arrangement that depends on the hotel’s occupancy rules.

Keep the intake tied to real decisions. A room category may change the rate. A child’s age may matter to an occupancy or meal policy. An arrival time may need a separate operational check. Explain why a detail matters rather than presenting every field as mandatory.

Use this reservations checklist:

• Arrival and departure dates, written unambiguously.
• Number of adults, children where relevant, and rooms.
• Room or bed preference, with an undecided option.
• Meal or package preference when it changes the offer.
• Any request that needs staff to check suitability or availability.
• The teammate responsible for checking and replying.

Do not ask for sensitive identity documents just to answer an initial availability question. Leave later booking requirements to the hotel’s appropriate process.

Fictional example: A guest requests a twin room for two adults from 18 to 20 November and asks about early check-in.

A useful summary is: “I have your request for a twin room, 18 to 20 November, for two adults. Reservations will check the room and rate. Early check-in also needs confirmation.”

That sentence separates the requested stay from an approved booking. “Your twin room is ready” would assert an outcome nobody has checked.

When reservations returns a quote, include what the rate covers and the applicable cancellation or payment conditions. If availability changes while the guest considers the offer, explain that before taking the next step. A copied price from an earlier chat is not a fresh availability check.

Send unusual arrangements to a person with the context already collected. Examples include a group needing adjacent rooms, an accessibility question that the published description cannot answer, or a request for a rate exception.

Do not make the guest restart the enquiry because the request does not fit a menu. The human handoff guide explains how to preserve context and make the next owner clear.

If the hotel’s availability system cannot be reached, say that staff need to check. An empty lookup response does not establish that the hotel is sold out. It also does not justify offering the last room mentioned in a previous conversation.

Record whether the guest asked for a follow-up and what they expect to receive. A booking enquiry is not blanket permission for later promotions. Follow WhatsApp’s messaging policy and the opt-in guide.

Write a follow-up around the open decision: whether the guest needs clarification on the quote or wants staff to check an alternative. Do not invent urgency such as “last room” without a current, authorised basis. Close the task when the guest declines or asks you to stop.

Review a few fictional enquiries with reservations before building automation: a complete request, missing dates, an unusual room arrangement and unavailable inventory. For each, identify the next question and the person who can make the decision.

The hotel workflow page connects enquiry intake to team ownership. Use the glossary if terms such as template or Logic flows are unfamiliar. Start with an intake your staff can follow consistently. Add connected availability checks only when the actual system and its failure behaviour have been verified.

Download the blank checklist to adapt the fields for your team. Use fictional records when testing it.

Use the chatbot for enquiry intake and approved facts such as directions or normal check-in hours. Room availability, rates and exceptions need a current system result or reservations. A calendar appointment is not a room reservation.

Let guests correct dates without restarting. Offer staff help when a request does not fit the menu. During closed hours, give the actual staffed hours and the hotel's appropriate urgent contact route.

Before enabling the flow, test missing dates, changed dates, an unavailable room system and an explicit request for a person. Confirm that automated replies yield when staff own the conversation. Keep a named owner for unanswered enquiries. Use the Logic Flow setup guide for configuration and the guest shift-handover checklist for requests that continue after check-in.