WhatsApp Chatbot for Hospitality (2026)

Because a traveling guest is often on a flight, in a different time zone, or paying for roaming - a phone call is the worst way to reach them, and an email gets buried under booking confirmations from three other sites. WhatsApp is usually already open on their phone, and it works over hotel or airport wifi without a call connecting.

The practical scenario: a guest lands late, their flight delayed by two hours, and messages at 23:10 asking if the front desk is still staffed and whether check-in can happen after midnight. A phone line with no answer leaves them standing in a lobby unsure what to do. A WhatsApp thread that already sent pre-arrival check-in instructions can confirm late check-in policy immediately and, if the question goes beyond policy, hand off to whoever is on the overnight desk.

The same channel carries the reverse case well too - a guest replying to a pre-arrival message with "can we get a crib in the room" is a request the bot can log and confirm, rather than something that only gets noticed when the guest mentions it at check-in.

It also fits how guests already book. Most arrive through an OTA or a booking engine that hands off to email confirmations nobody reads carefully. A WhatsApp thread opened right after booking becomes the one place a guest reliably checks, which is why pre-arrival information sent there gets read at a much higher rate than the same content buried in a confirmation email.

Keep the automated scope to logistics and information that does not require overriding a policy:

• Pre-arrival information. Check-in time, directions, parking, what to expect, sent ahead of arrival with a reply path for questions.
• Booking modifications within policy. Date changes, room type changes, and cancellations that fall inside the stated rate rules.
• Concierge-style Q&A. Amenity hours, restaurant recommendations, wifi details, spa or gym hours - grounded on your property's actual information.
• Checkout logistics. Late checkout requests within policy, folio and invoice delivery, luggage storage.
• In-stay requests. Extra towels, a crib, housekeeping timing - captured and routed to the relevant department.
• Post-stay follow-up. Review requests and return-guest offers, sent after checkout.

Notice what is missing: overriding a cancellation policy, negotiating a rate, and resolving a service complaint. Those need someone with authority to make an exception, which a bot should never have.

A useful test: does the request end in something the bot can confirm directly - a date change within policy, a fact about the property - or does it require someone to physically do something or approve an exception? The first automates cleanly; the second is a job for a department, with the bot's role limited to capturing the request accurately and routing it fast.

This is the rule that decides whether your pre-arrival sequence actually reaches the guest, and hotels running multi-message pre-arrival flows are the ones most likely to trip over it.

When a guest messages you - or opts in at booking - a 24-hour customer-service window opens, during which you can reply freely. Once it closes, only an approved message template can send.

• A check-in reminder or arrival-day instructions tied to a confirmed booking is utility, since it relates to a transaction the guest already made.
• A post-stay review request or a "come back and save 15%" offer is marketing, business-initiated and promotional, and needs explicit opt-in plus stricter review.
• The moment the guest replies to any message in the sequence, the window reopens, and questions about the room, amenities, or a request can be answered freely until it closes again.

Sequence the messages so the guest has a reason to reply early - a simple "reply YES to confirm your arrival time" reopens the window well before check-in day, giving the bot room to answer questions freely instead of being limited to template text right when the guest needs the most help.

Volume matters for properties running frequent turnover. A property sending a pre-arrival sequence to every booking, plus a post-stay offer to every departure, is running two separate template categories at meaningful scale, each billed by Meta per message by category and destination country. Plan template approval and the messaging budget into the season, not around it.

The line here is safety and financial exposure, not the difficulty of the question.

• No safety or emergency handling. A message about a fire alarm, a medical issue, or feeling unsafe must escalate to staff instantly - not be answered with a scripted reply.
• No policy overrides. Refunding a non-refundable booking, waiving a cancellation fee, or comping a night are compensation decisions a bot should never make unilaterally.
• No payment card data in the thread. Share a secure payment link for any balance due; never ask a guest to type a card number into WhatsApp.
• No service recovery promises. A guest complaining about a noisy room or a maintenance issue needs a person who can actually move them or send someone up - a bot apology does not fix the room.

Build an explicit escalation path for anything that sounds urgent or dissatisfied: the bot should acknowledge it plainly and route it immediately rather than trying to resolve a complaint it has no authority to fix.

Local regulation adds another layer for properties handling payment on the channel. PCI rules govern how card data can be collected and stored, and a WhatsApp thread is not a compliant place to hold that data even briefly - always redirect the guest to a secured payment page rather than accepting card details as plain text.

1. Any safety or emergency signal. Escalate instantly, day or night, with no waiting on a queue.
2. Complaints or dissatisfaction. Detected by keyword and by sentiment - a guest should not have to ask twice to be heard.
3. Requests outside policy. Rate exceptions, comped nights, or anything requiring management sign-off.
4. Explicit request. "I want to speak to the front desk" must work at every step.

The handover needs to carry the reservation details and what the bot already tried, so staff are not asking a jetlagged guest to repeat their room number and booking reference. On Conferbot the conversation moves into a shared agent inbox with the full thread attached, and the bot stops replying once a person joins.

Because hotels operate around the clock, state clearly in the thread whether the message is going to an overnight desk or will wait until morning - a guest arriving at 2am needs to know which, rather than wondering whether the bot even registered the request or simply went silent.

1. Get a WhatsApp Business API number. A dedicated guest services line, staffed in shifts, not a single employee's phone.
2. Submit templates early. Pre-arrival instructions, check-in reminder, and post-stay review request (marketing, opt-in) - approval takes time, so do this before your next peak season, not during it.
3. Build the flow once using Conferbot's template library for pre-arrival, concierge Q&A and checkout as a starting structure.
4. Push booking, room and rate data in from your property management system over webhook so it's real, not stale copy in a script - there's no native PMS integration to enable.
5. Write the emergency and complaint escalation copy deliberately - this is the safety-critical text, and it should be tested as carefully as the booking flow.
6. Pilot on one property or one guest segment for a season before rolling out across the portfolio.

Because the same flow deploys to every channel on Conferbot, a guest who books through your website can continue the same conversation on WhatsApp once they arrive in-country - see cross-channel context for how that continuity is designed, so front desk staff see one thread instead of two disconnected conversations for the same reservation.

Track the numbers that reflect guest experience and front desk load, not just messages sent:

• Front desk call volume for logistics questions the bot now answers directly.
• Pre-arrival reply rate - guests who confirm arrival details in advance are easier to plan for at check-in.
• Escalation rate by reason, especially safety and complaint categories, since a spike there deserves attention on its own.
• Post-stay review request response rate, compared against email-based requests for the same period.

Watch complaint-escalation response time specifically - a guest still on property whose issue is not resolved quickly is a very different risk than one who complains after checkout, since the first can still be turned around before they leave a review that the second cannot undo.

Can a hotel send pre-arrival messages automatically on WhatsApp?

Yes, as an approved utility message template if it is sent before the guest has replied, since it relates to a booking they already made. Once the guest replies to that message, the 24-hour window reopens and the rest of the conversation - directions, room requests, arrival timing - can be free-form until it closes again.

What is the 24-hour window for hotel guest messaging?

It is the period after a guest messages you, or opts in, during which you can reply with anything. Once it closes, only pre-approved message templates can send. Booking-related messages like check-in reminders are utility templates; post-stay offers and review requests are marketing templates that require opt-in and stricter review.

Can a WhatsApp bot handle a guest complaint?

It can acknowledge the complaint and escalate it immediately, but it should never attempt to resolve one on its own - a noisy room or a maintenance issue needs a person who can actually act, such as moving the guest or sending housekeeping up. The bot's job is to route the complaint fast, not to apologize and stop there.

Should a hotel chatbot waive cancellation fees?

No. Fee waivers, rate exceptions, and comped nights are financial decisions that should route to a manager or reservations staff, not be decided automatically. The bot can confirm what the stated cancellation policy allows and process any change that falls within it, but exceptions need a person with the authority to approve them.

How should a hotel handle a safety issue reported on WhatsApp?

Escalate instantly, with no scripted reply in between - a message about a fire alarm, a medical issue, or feeling unsafe should trigger immediate handover to staff, day or night. Build this as a dedicated detection path rather than relying on the same escalation rules used for general complaints, since response time matters far more here.

How much does a WhatsApp chatbot cost for a hotel?

There are two costs: the chatbot platform and WhatsApp's own conversation fees, billed by Meta per category and destination country. Plans are $19, $39 and $59 a month, and the free tier covers 600 conversations on the website widget. WhatsApp needs the Business plan - the pricing page lists what each tier includes. WhatsApp API messaging fees are billed by Meta directly.