A WhatsApp playbook for hotel guest communication

Ask any front-desk team in India where their guests actually want to talk to them, and the answer is almost never email and rarely a phone call — it’s WhatsApp. Guests message to ask about early check-in, to send a photo of their ID before arrival, to ask if the pool is open, and to complain the moment something goes wrong, all in the same thread they already use for everything else in their life. A hotel that treats WhatsApp as an afterthought is ignoring the channel its guests are already using. This is a practical playbook for doing it well.

Why WhatsApp is the guest channel in India

WhatsApp’s near-universal adoption in India means it’s not a “nice extra” channel alongside email and SMS — for most guests, it’s the primary one. It’s asynchronous, so a guest doesn’t need to be free at the same moment as your staff. It supports images and documents, so a guest can send an ID photo or you can send a folio PDF without a separate portal. And because guests already use it for everything else, a message from your hotel doesn’t feel like it’s coming from a system — it feels like a conversation. That familiarity is the whole advantage, and it’s also exactly what you can accidentally destroy by getting the tone or the frequency wrong.

The five messages every hotel should send

There’s a small set of moments in a guest’s stay where a WhatsApp message earns its place rather than feeling like noise:

1. Booking confirmation — the moment a reservation is made, confirming dates, room type and rate so the guest has something to refer back to.
2. Pre-arrival — a message a day or two before check-in with practical details: address, parking, check-in time, anything they need to know before they arrive.
3. In-stay check-in — a brief message once they’ve settled in, giving them an easy way to ask for anything without hunting for a phone number.
4. Checkout / folio — sending the final bill or a thank-you at departure, on the same thread they’ve already been using.
5. Win-back — reaching out to a past guest, respectfully and infrequently, when it might genuinely be relevant for them to book again.

Each of these is a moment where a message adds value to the guest’s actual experience of staying with you — not just a moment where it’s technically possible to send one.

Keeping it human

The single fastest way to burn out a WhatsApp channel is to treat it like a broadcast list. A guest who messaged to ask about parking and gets three unrelated promotional blasts that week will mute your number, and rightly so. The discipline that keeps WhatsApp working as a channel is simple: it’s one inbox with a real conversation history, not a one-way blast tool, and every automated message respects the fact that a real person can reply and expects that reply to go somewhere a human will actually see it. Consent and an easy opt-out matter too — a guest should always be able to say “stop messaging me promotions” and have that respected immediately, not buried in a settings page nobody finds.

Where AI helps (and where the channel stands today)

WhatsApp is live today as the channel this whole playbook assumes — official Meta API or a QR-linked connection, both landing in one inbox. SMS and email are on the roadmap as additional channels, but they’re not what any of the above depends on right now; this is a WhatsApp-first playbook because that’s the channel that’s actually shipped and working.

This is where an AI-first inbox earns its keep, if it’s built the right way. The value isn’t “the AI replies instead of a human” — it’s that a chatbot can handle the repetitive first pass of a conversation (confirming a booking detail, answering an FAQ about check-in time) while proposing anything consequential — a new reservation, a change, a cancellation — and waiting for explicit confirmation before it acts. Anything sensitive, like verifying identity or authorizing a change to a paid booking, should be OTP-guarded rather than taken on the AI’s word alone. And critically, the AI should know when to step back and hand the conversation to a human — a frustrated guest, an unusual request, anything outside its confidence — rather than looping them through a script. Cnykra’s inbox is built around exactly that shape: propose, confirm, guard the sensitive stuff, and hand off when it should.

Automation without spam

The guardrails that keep automated WhatsApp messaging from turning into spam are unglamorous but essential: quiet hours so nobody gets a promotional message at 11pm, deduplication so the same trigger doesn’t fire the same message to the same guest twice, and an honest opt-in model where a guest chose to be reachable rather than being messaged because their number existed in a database. None of this is exciting to build, but it’s the difference between a WhatsApp channel guests appreciate and one they block.

If you’re setting this up for the first time, the practical starting point is a unified inbox that keeps every conversation — human and automated — in one place, with an AI that proposes and confirms rather than acting alone, and hands off the moment it should.