On 1 October 2026, WhatsApp messages that hotels have been sending for free start costing money.
Meta's pricing documentation, updated 5 August, confirms two changes on that date. Service messages, free since November 2024, become chargeable. Utility templates sent inside an open 24-hour customer service window, free since July 2025, become chargeable. Every business phone number gets 1,000 free service messages a month, resetting monthly with no rollover, and pays from the 1,001st.
For a hotel answering a few hundred messages a month, that is close to nothing. For a busy coastal property in August, it is a line item that did not exist in July. Either way it means the same thing: the era of treating WhatsApp as a free channel you can spray messages into is over, and the hotels that set it up properly are the ones it will not hurt.
This is the practical guide to doing that. What WhatsApp actually does for a hotel, the rules that shape what you can send and when, the six moments worth automating, the ones that need a person, and what it takes to run it alongside email rather than instead of it.
Why WhatsApp, without the inflated statistics
WhatsApp passed three billion monthly active users, on Meta's own reporting, making it the most used messaging app in the world. In most of Europe, Latin America and Asia, it is not one channel among several. It is the channel, already installed, already open, already carrying the traveller's conversations with everyone else in their life.
Now the part most articles get wrong.
You will see it claimed everywhere that WhatsApp has a 98% open rate against 20% for email. We are not going to use that figure, because it has no verifiable primary source. It traces back to an industry estimate that has been copied between blogs for years without anyone producing the underlying data.
The real comparison is more interesting anyway. Revinate's 2026 Hospitality Benchmark Report, built on 2.8 billion emails, found hotel newsletters average a 33.6% open rate globally. Targeted sends to lists under 5,000 contacts hit 42.78%. Cart abandonment campaigns reach 69% open rates and convert at 6.8%.
Hotel email is not unread. Badly targeted hotel email is unread, which is a different problem and not one WhatsApp fixes.
What WhatsApp gives you that email does not is the shape of the conversation. Email is a broadcast the traveller might reply to. WhatsApp is a thread they already have open, where a reply takes four seconds and no one has to find an attachment. A guest standing in your lobby at 23:40 with a question about the door code will not open their email. That is the actual argument, and it is strong enough without a fake statistic underneath it.
The rules that decide what you can send
Most WhatsApp guides for hotels skip this and then recommend message sequences that Meta's platform will not let you send. Three mechanics govern everything.
The 24-hour customer service window. When a guest messages you, a 24-hour window opens. Inside it you can send free-form messages of any type. Each new message from them resets it. When it closes, you can no longer send free-form messages at all.
Templates. Outside that window, template messages are the only thing you can send. Templates are pre-written, submitted to Meta, and approved before use. They come in three categories: Marketing, Utility and Authentication. Category matters because it determines both what is allowed and what you pay.
Per-message pricing. Since 1 July 2025, Meta charges per delivered template message rather than per conversation, at rates that vary by the recipient's country calling code. Belgium currently sits in the Rest of Western Europe band. Marketing rates rose in Spain, the UK and Italy on 1 July 2026.
Put together, these decide the design of every sequence below. A pre-arrival upsell offer is a Marketing template, it needs approval, and you pay for it. A reply to a guest who just asked about parking is free-form inside an open window. After 1 October, service replies are free only up to 1,000 a month per number.
One more mechanic worth knowing: a Click-to-WhatsApp ad or a Facebook Page call-to-action opens a free entry point window of 72 hours during which everything you send is free. If you run paid social at all, that is the cheapest door into a conversation you have.
The six moments worth automating
1. Booking confirmation
The confirmation is a Utility template and it is the moment the thread gets created. Send it and the guest now has a WhatsApp conversation with your hotel that sits in their app for the whole trip.
Put something in it worth keeping: the address in a form their maps app will open, the check-in window, and a direct line to change anything. This is also where a direct booking link belongs for guests who arrived through an OTA, because it is the last moment they are thinking about the reservation rather than the holiday.
2. Pre-arrival
Travellers book around 40 days ahead globally, 47 in EMEA. That window is where the revenue is, and where most hotels send nothing.
The rule that makes it work is relevance. A generic "would you like breakfast" to everyone performs badly and, as a Marketing template, costs you per send. An offer that knows the guest booked the standard double, arrives on a Friday, and has not yet added breakfast is a different message entirely.
At C-Hotels Silt, a 73-room seafront property in Middelkerke, fewer than 6% of arriving bookings received any message across an eight-month window before launch. After launch, more than 65% of arrivals were reached, and the property took over €24,000 in upsell revenue across three months: €15,000+ breakfast, €8,000+ parking, 450+ orders written straight into the PMS. That is €12 or more per arrival.
3. Check-in day
Arrival instructions, door codes and digital keys are Utility messages and they are the highest-value automation in the set, because they replace the phone call that happens when someone is standing outside your building with luggage.
Send it timed to arrival rather than at 09:00 to everyone. A guest landing at 22:00 needs the late-arrival instructions at 18:00, not twelve hours earlier alongside a breakfast offer.
4. During the stay
This is where the thread earns its keep, and it is mostly reactive rather than scheduled.
At C-Hotels Andromeda in Ostend, more than 90% of guest messages have been answered without a person over eleven months, 6,500+ of 7,500+, at a median under ten seconds. Over 500 parking reservations were placed by guests themselves with no staff involvement. Conversations split near-evenly across Dutch, English, French and German, plus 20+ other languages.
Resist the scheduled "is everything okay?" ping. It is a Marketing or Utility template depending on how it is written, it costs money, and it mostly generates polite non-answers. Guests with a problem will tell you if the thread is open and someone answers fast.
5. Check-out
Departure instructions, the folio, late check-out. Utility messages, low volume, high goodwill. The one worth automating properly is late check-out, because it is the only upsell that is still available on the morning of departure and the front desk almost never offers it.
6. Post-stay
Ask while it still matters. At Yalo Ghent, 92 design rooms with a 24/7 brand promise, more than 85% of rated stays score 9 or 10, from 650+ of 750+ responses since May. Roughly one in ten score 6 to 8, and barely one in a hundred score 5 or below. Happy guests get prompted to say so publicly. Unhappy ones get found before the review site does.
The rebooking offer is a Marketing template and needs opt-in. Send it seasonally to people who actually rated you well, not monthly to the whole list.
What to automate and what a person has to handle
Being straight about this matters more than the automation rate.
Automate: the repeat questions, which are always the same six at any given property. Parking, WiFi, breakfast times, check-in and check-out, pets, the nearest station. Confirmations, arrival instructions, door codes. Structured upsell offers. Feedback requests. Anything where the correct answer is a fact rather than a judgement.
Keep human: complaints, anything involving money that has already been charged, accessibility and medical needs, group and event coordination, and any message where the guest is upset. Also any question the system has not seen before. A wrong confident answer costs more than a slow one.
The measure of a good setup is not the deflection rate. It is whether escalation is fast when it happens. At Andromeda, escalated messages take a median of over an hour for a staff reply against under ten seconds for automated ones. At Yalo it is over 30 minutes. That gap is the real cost of a badly drawn line, and it is the number to watch.
We go deeper on the split in what to automate and what to keep human.
Why the WhatsApp answer and the website answer have to come from the same place
Here is the failure that undoes everything above.
Your website says breakfast is €18. The chatbot was trained in March and says €15. The WhatsApp assistant reads from a third document that says breakfast is served until 10:00 when it now runs to 10:30. A guest asks the same question in two places and gets two answers, and now they do not trust either.
This is not a hypothetical. It is the default state of any hotel running a website from one vendor, a chat widget from another, and WhatsApp from a third. Each holds its own copy of the same facts, each was updated on a different day, and nobody owns the discrepancy.
The fix is structural. One knowledge base holding the facts about your property, and every channel reading from it rather than holding a copy. Change the breakfast price once and the website, the WhatsApp assistant and the pre-arrival message are all correct at the same moment. This is also what makes the pre-arrival offer possible in the first place, because a message that knows what the guest booked needs the reservation and the product catalogue in the same place.
Integrations do not solve this. An integration moves a fact between two systems that both still store it, and one of them is always stale.
GDPR and WhatsApp Business in Europe
This is a summary, not legal advice, and a hotel operating in the EU should have its own counsel confirm the specifics.
Meta's platform requires opt-in before you send template messages, and that requirement is independent of GDPR. Under GDPR you also need a lawful basis for the processing itself. Transactional messages tied to a reservation (confirmations, arrival instructions, folios) generally rest on contract performance. Marketing messages, including rebooking offers and promotional upsells, need consent, collected clearly and separately, with a record of when and how it was given.
The practical requirements:
- Collect WhatsApp consent at the point of booking, worded so it is obvious what the guest is agreeing to, and separated from your general terms
- Give a working opt-out in the thread and honour it immediately across every channel, not just WhatsApp
- Have a data processing agreement in place with whichever provider runs the messaging on your behalf, since they are your processor
- Set a retention period for message history and actually enforce it
- Be able to produce a guest's message history on request, and delete it on request
The one that catches hotels out is the opt-out. If a guest opts out of WhatsApp marketing and your email tool keeps sending, you have a problem, and it is the same problem the knowledge base section describes: two systems, two copies, one of them wrong.
What you need to get started
Four things.
A WhatsApp Business Platform account. Not the free WhatsApp Business app, which runs on one phone and does not automate. The platform account is what allows templates, automation and multiple people in the same inbox.
A verified business phone number. It cannot be a number already registered to a personal WhatsApp account, and it should be the hotel's number rather than a duty manager's mobile.
A PMS connection. This is the one that determines whether any of the above works. Without it, your messages have a name and a date. With it, they have the reservation, the room type, the arrival time and what has already been paid for. Every useful automation in the six moments depends on it.
A platform to run it. Template management, approval, the shared inbox, escalation routing, the knowledge base and the reporting. The AskWhisper Suite covers this at €99 a month with the first 10 rooms included, then €7 per extra room, plus a one-time €399 setup fee, including the branded WhatsApp number, the PMS connection and the central knowledge base that the website reads from too.
Order matters. Connect the PMS first, load the knowledge base second, automate the six repeat questions third, and only then build the pre-arrival sequences. Hotels that start with the upsell campaign end up sending well-designed messages to people the system does not know anything about.
What results actually look like
From three properties running this, with their own numbers:
| Measure | Silt (73 rooms) | Andromeda (114 rooms) | Yalo (92 rooms) |
|---|---|---|---|
| Messages handled without staff | 4,000+ in 90 days, under 25 by staff | 90%+ of 7,500+ over 11 months | 95%+ of 2,500+ over 90 days |
| Median time to an answer | Under 10s | Under 10s | Under 10s |
| Arrivals reached | 65%+, from under 6% | 60%+ | 750+ in conversation monthly, from ~30 |
| Revenue | €24,000+ upsells in 3 months, €12+ per arrival | 500+ self-service parking reservations | — |
| Guest feedback | — | — | 85%+ of rated stays score 9 or 10 |
Read the pattern rather than the individual figures. Response time collapses from hours to seconds. Contact volume goes up several times over with the same headcount. Revenue appears in the pre-arrival window where there was none before. None of the three hired anyone to get there.
What none of them show is a hotel replacing its team. Yalo runs 750+ conversations a month with the staff it already had, and the reason the 9-and-10 scores hold is that the people are still there for the parts that need them.
Your website, your WhatsApp thread and your pre-arrival emails should all be saying the same thing, because they should all be reading from the same place. Describe your hotel once, and AskWhisper runs the site and everything that follows it from one record.
Turn lookers into bookers. Just Ask Whisper.
