WhatsApp for hotels: guest communication on autopilot

Ask a guest whether they read your confirmation email and you'll get a shrug. Ask them about the WhatsApp message with the door code – they've seen it, opened it, and saved it. The difference in attention is enormous, and for a hotel that depends on smooth arrivals, that's not a detail.

Why WhatsApp beats email

Email to guests has three problems: it lands in spam, it reads badly on a phone, and it often isn't opened at all. Open rates for travel newsletters sit at 20–30%. WhatsApp messages, by contrast, are almost always read – and usually within minutes.

On top of that there's the channel itself: in German-speaking markets, WhatsApp is the de-facto standard for private communication. The guest doesn't have to install anything, remember a portal login, or download the hotel's app. They reply as they would to a friend. For short, time-critical information – arriving today, parking, door code, "Wi-Fi password?" – it's the natural channel.

And it's bidirectional. An email confirmation is a one-way street; with WhatsApp the guest simply replies. "We won't arrive until around 10pm" lands directly in the right thread instead of disappearing into the general info@ mailbox.

Business API vs. the normal app

This is where it gets technical, but the difference is decisive. The WhatsApp app on the hotel phone is built for individuals. For a hotel it's unsuitable for several reasons:

• Not automatable. There's no official interface. Trying it anyway via hacks risks getting the number banned.
• One number, one phone. Several staff, one device – that doesn't scale.
• No templates, no clean opt-in. Bulk messages from a private number quickly get flagged as spam.

The WhatsApp Business Platform (Cloud API) is the official, Meta-approved route for companies. It runs through a Business Solution Provider (e.g. 360dialog), offers an API for automated sending and receiving, allows multiple agents in the same inbox and – importantly – works with approved templates and clear rules. It's precisely those rules that make the whole thing work without being treated as spam.

Opt-in, templates and the 24-hour window

Three concepts to understand, and the rest follows.

Opt-in. Before a hotel may message a guest over WhatsApp, it needs their consent. In practice you collect it during booking or in the confirmation ("Would you like to receive your arrival info via WhatsApp?"). No opt-in, no sending – that's both a Meta rule and clean from a data-protection standpoint.

Templates. A message initiated by the hotel must be a template pre-approved by Meta. Example: "Hi {{1}}, your booking for {{2}} is confirmed. Check-in from 3pm." The template is submitted once, reviewed, and then sent filled with the concrete values. The hotel may only send free text as a reply within the service window.

The 24-hour window. As soon as a guest messages the hotel, a 24-hour window opens during which the hotel may reply freely (without a template). If the guest goes quiet, the window closes and the hotel can only reach them again via a template. This logic prevents companies from spamming users unprompted.

The three workflows that pay off immediately

When you automate WhatsApp for a hotel, three messages above all justify the effort:

1. Booking confirmation. Right after booking: name, dates, arrival time, a short route description. Sent as a template, triggered from the PMS. The guest has the key details on their phone instead of buried in an email.
2. Check-in reminder. On arrival day, e.g. a few hours before: "We're looking forward to seeing you today. Check-in from 3pm, parking right by the building." Noticeably cuts the number of phone calls.
3. Door code / self-check-in. For properties with self-check-in or a smart lock, the most valuable use case: the access code, automatically at the right time, to the right person. No key at reception, no missed handover.

At zimrly these triggers run straight out of the PMS: a new booking creates the confirmation, the arrival day triggers the reminder, the self-check-in status the door code. The hotelier sets it up once and afterwards only looks at the inbox when a guest actually replies.

Automation with guardrails

The biggest mistake in guest automation is taking it too far. Confirmations and reminders are uncritical – they're factual and uniform. It gets delicate the moment a guest wants something real: a complaint, a special request, a last-minute change.

An auto-reply to a complaint is the worst thing that can happen. "Thank you for your message, your booking is confirmed" in response to "The room wasn't clean" turns an unhappy guest into a furious one. That's why every automation needs a clear guardrail:

• Automatic only for the factual: confirmation, reminder, code, standard FAQ ("When is breakfast?").
• Escalation to a human for anything that sounds like a complaint, dissatisfaction or an individual request. The system should recognise it has to step aside – and then do exactly that: notify a staff member instead of sending a platitude.

This separation is the difference between a helpful assistant and an embarrassing bot. At zimrly, complaint detection is therefore a hard veto: if the system detects a complaint or uncertainty, it sends nothing automatically and instead puts the message in front of the team.

A quick word on GDPR

WhatsApp belongs to Meta, a US corporation – which rightly raises data-protection questions. The clean setup includes: a documented opt-in from the guest, a data processing agreement with the Business Solution Provider, a mention in the hotel's privacy policy, and the principle of data minimisation – only the data the message needs is transmitted (name, booking details), nothing more. Using the Cloud API through an EU-based provider and collecting the opt-in cleanly puts you on defensible ground. What matters is that it's set up deliberately and not as an ad-hoc hack on the private hotel phone.

Bottom line

WhatsApp isn't a marketing gimmick for hotels, it's the channel guests are actually reachable on. Via the Business API, confirmation, check-in reminder and door code can be fully automated straight from the PMS – with clear guardrails so real concerns reach a human and not the bot. Set up right, it saves phone calls every day and makes arrivals smoother. Set up wrong, it drives guests away with platitudes. The difference lies not in the technology but in the discipline to draw the line between routine and a real conversation cleanly.