The WhatsApp Business API works for hotels when each message is matched to the right Meta category: booking confirmations, check-in instructions and checkout reminders are utility templates, review requests and upgrade offers are marketing, and everything a guest asks during the stay is a service reply inside the 24-hour window. Get that mapping right and the channel is cheap, compliant and welcome. Get it wrong and a hotel pays marketing rates for operational messages, or sends promotions to guests who only agreed to hear about their booking. Most English-language guides on this topic are written by guest-messaging vendors and lead with open rates. The category comes first, because it decides cost, consent and whether the message is delivered at all.
This guide covers which hotel messages are utility, which are marketing, how the stay itself fits the service window, what consent an Italian hotel needs and where to collect it, how the API connects to a PMS or channel manager, and when a property is better off without the API. It is general information, not legal advice.
Mapping the guest journey to Meta's categories
Before arrival: utility, as long as it serves the booking. Meta defines utility as non-promotional messages that follow a transaction or account event the customer started. A booking confirmation with dates, room type and amount qualifies. So does a pre-arrival message with the address, parking instructions, check-in time or a link to complete online check-in. Each should carry booking-specific data, such as the reservation number or dates, so it reads as tied to that stay.
The upgrade offer is marketing. "Upgrade to a sea-view room for 30 euros a night" serves the hotel's revenue, not the existing booking. Meta classifies mixed-intent templates as marketing, so an upsell bundled into the pre-arrival message turns the whole template into marketing. Send offers as separate marketing templates, only to guests who opted in to promotions.
During the stay: mostly service messages. When a guest writes to ask for towels, a late checkout or a restaurant tip, a 24-hour customer service window opens and the hotel can reply freely. Since 1 October 2026 Meta bills these free-form replies as service messages: the first 1,000 delivered each month are free for each business phone number, and charges start from the 1,001st. Whether a property stays inside that allowance depends on its guest volume and how many replies each request takes, so a large resort with busy concierge traffic should count its monthly replies before assuming they are free.
Utility inside the window is no longer free. A "your room is ready" template sent while the guest's window is open used to cost nothing. Since 1 October 2026 utility templates are charged inside the window too, at the utility rate for the guest's country code. The cheaper option, where the flow allows it, is a free-form service reply in the open thread rather than a template.
After checkout: careful with reviews. A checkout confirmation or the folio summary is utility. A request to review the stay on a booking platform talks about the stay but serves the brand, which is why it is a grey zone. Treat it as marketing unless Meta has approved your template as utility, and never bundle it into the checkout confirmation. The same logic, applied to online retail, is in WhatsApp order and shipping notifications.
Consent for an Italian hotel
Two layers, both mandatory. Meta's business messaging policy requires an opt-in to receive WhatsApp messages from the business. The GDPR adds its own requirements. Operational messages about a booking generally rest on the performance of the contract the guest entered into. Promotional messages, including return-stay offers sent months later, need prior consent that is specific, informed and freely given, and the hotel must be able to prove it. The full Italian framework is in WhatsApp opt-in and GDPR in Italy.
Collect it at your own touchpoints. Guests who book through an online travel agency often reach the hotel without a direct phone number or marketing consent the hotel can rely on. The practical collection points are the hotel's own booking engine, the online check-in form, and the front desk, with separate checkboxes for stay updates and for offers. Pre-ticked boxes do not count.
Identity documents are not a chat attachment. Italian accommodation providers must communicate guest details to the police under article 109 of the TULPS, usually through the Alloggiati Web service. WhatsApp can remind guests to complete online check-in, but asking them to send passport photos in the chat creates copies of sensitive data in a messaging thread. A secure check-in form linked from the message is the safer design.
Connecting the API to the PMS
Events, not campaigns. The useful hotel flows are triggered by events in the property management system: booking created, booking modified, arrival in two days, room status changed to clean, folio closed. Each event maps to one approved template, filled with variables from the reservation.
The channel manager is upstream. OTA bookings arrive through the channel manager into the PMS, so the PMS is the right trigger point for every booking regardless of source. What differs by source is whether you hold a usable phone number and a valid opt-in.
One template, several languages. International guests should receive the confirmation in their language. A WhatsApp template can carry translations for several languages under the same name, each reviewed by Meta, and the PMS language field decides which one is sent.
Replies need an owner. Every template invites an answer. Whoever handles the inbox, a front-desk team, an AI concierge, or both with handover, must see the reservation context, otherwise the guest repeats their booking number three times. Messages from users are never charged, so good conversations cost the hotel only its own replies.
When the API is the wrong choice
A small property with one phone. A five-room B&B where the owner answers personally gains little from the API. The free WhatsApp Business app covers manual messaging, and the API adds a provider, template approval and per-message costs. The API earns its keep when several staff share one number, when messages must be triggered by the PMS, or when volume makes manual replies impossible.
Guests who never opted in. Without a WhatsApp opt-in there is no one to message. Email remains the channel for those guests, and for invoices and documents they may need to keep.
Pure promotion. If the plan is mostly seasonal offers to past guests, the cost is marketing templates at marketing rates, with no volume discount. A newsletter may do the same job for less.
In short
On the WhatsApp Business API a hotel pays and complies by category: utility for the booking, service for the stay, marketing for offers and, in most cases, reviews. Since October 2026 both utility templates inside the window and service replies beyond 1,000 a month per number are charged, so design flows that answer in the open thread and send templates only when an event demands one. TikJoy runs on the official API, with an AI concierge that can answer guests inside the window. See how the WhatsApp AI Concierge works.