WhatsApp for Hotels: The Operator's Guide to Staying in Control

Yes, hotels should use WhatsApp with guests, in the markets where guests already use it, and they should do it through the WhatsApp Business Platform in a shared inbox, with a documented opt-in and a small set of approved templates. The free app on a staff member's phone is how messages get lost, how a request disappears on someone's day off, and how a GM ends up asking "is this even allowed?" This post is the operator's version of our guide to hotel WhatsApp automation: less about what the channel can do and more about staying in control of it.

If the category is new to you, what hotel guest communication software actually does is the broader map. One line of housekeeping before we start: consent and marketing rules vary by country, including GDPR in Europe, the TCPA in the United States and local law everywhere else, so what follows is general information, not legal advice.

Should hotels use WhatsApp with guests at all?

Where your guests live on it, yes, and the data on where that is comes from your own arrivals. Travelers prefer messaging: in eviivo's 2025 survey of 430 travelers, 58% chose SMS, WhatsApp or email links for quick exchanges with a property, against 25% who wanted to speak to a person ^[3]. eviivo did not split WhatsApp from SMS and email, so read that as a preference for messaging channels, not for WhatsApp specifically.

The scale of business messaging is not in doubt. Meta reported more than 600 million business-to-consumer conversations a day across its apps in 2023, with WhatsApp Business past 200 million monthly active users ^[2]. For a hotel the relevant question is narrower: which of my source markets treat WhatsApp as the default? Spain drew 93.8 million international tourists in 2024, led by the United Kingdom (18.4 million), France (13.0 million) and Germany (11.9 million) ^[5]. The Caribbean's 34.2 million arrivals included 5.3 million from Europe ^[4]. Mexico's air arrivals in the first eleven months of 2024 were led by the United States (12.7 million) and Canada (2.3 million) ^[6]. In my experience as a guest, Europeans and Latin Americans reach for WhatsApp and North Americans reach for SMS, but that is an impression, not a statistic. Look at your own booking countries and you will know whether WhatsApp is a primary channel or a courtesy.

I will admit a bias. I travel with my family to places where WhatsApp is simply how you talk to a business, and the resorts that answered me there felt reachable in a way a phone number and a voicemail never did.

WhatsApp Business app or WhatsApp Business Platform: which one does a hotel need?

The Platform, unless exactly one person will ever touch a guest message. The free WhatsApp Business app is designed for a small shop: one number, one phone, one person. The Business Platform, often called the API, runs through a provider into a shared inbox, which is what turns WhatsApp from a personal phone habit into a channel the property owns.

WhatsApp Business app versus Business Platform, for hotels

Operator comparison as of October 2026. Confirm current Meta terms before launch.

The trade-off is cost and setup. The app is free and takes ten minutes. The Platform costs money per conversation and needs a provider, a verified profile and template approvals. That cost buys history that survives a staff change, an owner on every conversation, and routine answers nobody has to type.

Do guests have to opt in before a hotel messages them?

Yes, before the hotel writes first. Meta's policy, as published on its developer documentation in 2026, requires a business to obtain opt-in before sending messages, and the opt-in must clearly state that the person is agreeing to receive communication from the named business, collected in a way that complies with applicable law ^[1]. Acceptable methods include a website form, SMS, a phone system, in person or on paper ^[1]. Re-check that page before you launch, because it changes.

In hotel terms, there are three natural moments to collect it: the booking form, the pre-arrival email ("tap here to receive your arrival details on WhatsApp"), and check-in. The guest who messages you first is a different case: you can reply within Meta's customer service window without a separate opt-in, because they opened the conversation. The practical opt-in checklist:

1. The consent names the property and says what you will send (arrival details, request updates, stay information).
2. It is collected somewhere you can prove later: a form, a checkbox, a signed card.
3. The number and the consent record are stored together, with the date.
4. Opt-out is honored immediately, and "STOP" or its equivalent is tested before launch.
5. Marketing messages get their own consent, separate from service messages, because local law in many countries treats them differently.

That fifth point is where properties get into trouble. A guest who agreed to receive their shuttle time did not agree to a spa promotion.

What can a hotel send, and when?

Two kinds of conversation, with different rules. When the guest writes first, the hotel can reply freely inside Meta's service window, which is where most of the useful traffic lives: questions, requests, complaints. When the hotel writes first, it must use a template Meta has approved in advance, categorized as utility (tied to something the guest did or booked) or marketing (an offer). Meta decides the category, and a message that does not follow from a guest request is likely to be treated as marketing.

Template set for a resort

Sample copy for illustration, 2026. Meta assigns the final template category; confirm each one on approval.

Keep the set small and the tone human. Six templates that sound like a person beat twenty that sound like a bank; texting etiquette for hotels covers the tone rules, quiet hours and the things never to send on any channel.

How do you keep WhatsApp off personal phones and across shifts?

Move the number to the Platform, point it at a shared inbox, and retire the personal phones the same day. Not the same week. Any phone that still receives guest messages will keep being used, because it is easier, and the whole point is to make the inbox the easiest place.

Then four rules. Every conversation has an owner. Handoff happens by reassigning inside the inbox, never by forwarding a screenshot. Shift change is a two minute review of the open conversations: who owns this, and what did we promise? And retention is written down: how long history is kept, who can see it, and how it is deleted when a guest asks.

The general practice is one inbox for every channel, and ResortConcierge AI puts WhatsApp in the unified inbox next to SMS, email and web chat, so a guest who starts on WhatsApp and continues at the desk has one history any staff member can pick up.

The reason this is a service question rather than an IT one is laid out in why one inbox for every channel is a service problem, not an IT problem. The short version: the guest experiences the gap between the phones, not the phones.

Routine WhatsApp questions, the shuttle time and the pool hours, can be answered from the property knowledge base in the guest's language. Anything that needs a human, or any message with a negative tone, should land with a person, and ResortConcierge does that by handing a conversation to a person with an owner rather than pinging everyone and hoping. Approved templates go out by segment, arrival details to tomorrow's arrivals and not the whole house, which is the difference between a notification and a blast.

Two scope notes. WhatsApp voice notes and calls are not part of this; treat them as out of scope. And a supervised mode where a person approves every automated reply is planned, not shipped.

What does WhatsApp cost a hotel?

Per conversation, at rates Meta sets by country and by category, plus whatever your provider charges for the inbox and the connection. I am deliberately not quoting numbers, because Meta changes the rate card and a figure that was right when I wrote this will be wrong when you read it. Pull the current pricing page for your markets at draft time, and again at budget time.

What you can plan is the shape. Guest-initiated service conversations are typically the cheapest category, utility templates cost more, and marketing templates cost the most, which is a useful discipline: the pricing nudges you toward answering questions and away from blasting offers. Multiply your expected conversations per stay (two to four is a reasonable planning assumption for a resort) by occupied room nights, and you have a monthly estimate to put beside the provider fee.

How do you measure whether WhatsApp is working?

Five numbers, reviewed weekly for the first quarter. Median first response time on WhatsApp, compared with your other channels. Share of WhatsApp conversations resolved without a person, which is the knowledge base doing its job. Escalations, and how long they waited for an owner. Opt-in rate at each collection point, so you know whether the pre-arrival email or the check-in card is doing the work. And complaints that mention messaging at all, in reviews or in the inbox.

The first number is the one guests feel. A WhatsApp that answers in minutes feels like a concierge in the pocket; one that answers the next morning feels worse than no WhatsApp at all, because the guest saw the two blue ticks. If response time is the problem you are trying to solve, slow response times has the fuller picture.

Start with the number itself. This week, find out which phone your guests are actually messaging, move that number to the Business Platform, and put it in an inbox with an owner. The templates and the measurement can follow, but the day the personal phones go quiet is the day the channel becomes yours.