The usual setup at a mid-market hotel goes like this: reservations handles WhatsApp inquiries on one number. The front desk manages arrival coordination on another. Housekeeping works through a shared group chat. F&B takes room service requests through a fourth number entirely, saved in the personal phone of whoever is on shift.
Hotel guest messaging is the practice of connecting those conversations into a coherent program, one that follows the guest from booking confirmation through to post-checkout without requiring them to find the right department number at every stage of their stay.
The problem with the fragmented version is not just that messages get lost, though they do. The problem is structural. Hotels are organized by department because that is how hospitality operations work. Housekeeping owns rooms. Reservations owns the booking. Concierge owns requests. Each team has its own tools, its own workflows, and often its own channel. Guests, however, are not organized by department. They have one phone, one conversation history, and one expectation: that the hotel responds.
This guide covers how to build a guest messaging program that works across the whole stay, the specific failure points at each stage of the guest journey, how to choose the right channels for your guest profile, and how existing systems fit into the picture without requiring a full platform replacement.
The instinct when guest communication feels fragmented is to add a tool. A hotel that already has departmental WhatsApp numbers sets up a new shared number for guest services. Then a Viber account for overseas guests. Then an SMS gateway for bulk confirmations. A year later, a guest who messages about a missing towel, a noise complaint, and a checkout time extension may do so on three different channels, and the staff on each of those channels has no visibility into what the guest already sent through the others.
Fragmentation is the disease, not the symptom. Adding messaging channels without solving the routing and visibility problem does not improve the guest experience. It expands the surface area of the problem.
What resolves this is not a single channel or a single app. It is deciding, deliberately, how messages will flow from each channel to the team responsible for handling them, and what the guest will see when they send one. That decision does not have to involve replacing your property management system or buying an enterprise guest engagement platform. For most independent and mid-market properties, the program can be built around the channels you are already using, with structure added rather than tools replaced.
Pre-arrival is where the guest relationship actually begins, and it is the stage where a small amount of structured messaging creates the most disproportionate value. A booking confirmation, a reminder sent 48 hours before arrival with check-in instructions, and a practical day-of note covering parking, access, and check-in time all happen without front-desk involvement once the workflow is in place.
The operational payoff is underappreciated. Pre-arrival messaging surfaces guest questions early, before the check-in desk is running at capacity. A guest with an accessibility question or an early-arrival request will ask it two days in advance if you give them a channel to reach you. That is significantly easier to handle than the same question arriving at noon on a Friday when the lobby is full.
The channel decision at this stage should be driven by how the guest booked and where they are coming from, not by the hotel's primary market. A reservation made through a travel agent in Manila may have a Viber contact. A direct booking from a guest in Germany will almost certainly be reachable on WhatsApp. When channel preference is unknown, SMS reaches virtually anyone regardless of data access or smartphone model, which makes it the practical fallback for the pre-arrival window when you cannot yet confirm what a guest is using.
For a detailed look at how pre-arrival messaging works in Southeast Asian markets, where OTA-sourced bookings and mixed-channel guest profiles create specific coordination challenges, see Hotel Pre-Arrival Guest Messaging.
In-stay is where the departmental fragmentation becomes most visible to the guest, and where fixing it creates the clearest operational return.
A service request sent to the front desk WhatsApp that needs to be relayed to housekeeping, passed by phone or radio, and confirmed back to the guest involves at minimum three manual handoffs. Each one is a point where the request can stall, be misrouted, or simply not be confirmed back to the guest at all. From the guest's perspective, they sent a message and heard nothing. From the hotel's perspective, the request was handled. The disconnect is in the confirmation loop, not in the execution.
The structure that resolves this is straightforward: incoming messages from guests need to reach the team responsible for handling them, and the guest needs to know the request was received. The channel the guest used does not change that requirement. What changes is whether the team managing inbound communication has sight of all the channels guests are reaching out through, not just the primary one.
In-stay messaging also opens a revenue window most properties leave closed. A guest who is already engaged in a conversation on WhatsApp about a request is a different audience than one who receives a promotional email about spa availability. Upsell messages sent in the context of an active conversation, at a relevant moment in the stay, convert differently than broadcast promotions sent to the whole guest list.
For a detailed look at how independent hotels in Africa and Southeast Asia approach in-stay revenue through messaging, see The In-Stay Revenue Opportunity for Independent Hotels.
Post-checkout is the stage most hotels either automate badly or skip entirely. A review request sent immediately following a difficult checkout is not a review strategy. A feedback message that arrives the following day, gives the guest a way to raise anything that did not go well before directing them to a public review platform, and feels like a genuine follow-up rather than a template is something different.
The timing and framing of the post-stay sequence matters significantly. A guest who reported a room issue during their stay and received a fast response is a better candidate for a review request than one who sent the same message and heard nothing. The post-stay workflow should account for what happened during the stay, not treat every departing guest identically.
Post-checkout is also where the returning guest relationship starts. A property that sends a relevant offer to a guest three months after their stay, one connected to what they actually did during the visit rather than a generic promotional blast, is building something the standard email newsletter is not. The contact data from the messaging program is what makes that possible.
For the full post-stay playbook, including how to sequence feedback requests, review prompts, and re-engagement messaging, see After Checkout: The Post-Stay Messaging Playbook for Boutique and Independent Hotels.
Most channel advice for hotels is framed around the market where the hotel operates. That is not always the right starting point for properties with international or mixed-origin guest profiles.
A hotel in Bangkok serving Japanese package tour groups needs LINE. The same property serving European independent travelers needs WhatsApp. A business hotel in Lagos serving a mix of domestic guests and international conference attendees needs both WhatsApp and SMS, for different segments, sent through different logic. Channel choice is a guest-origin question before it is a market question.
WhatsApp is the practical global default: it is the dominant messaging app in over 100 countries and the reasonable first choice for any property reaching international travelers. But there are meaningful exceptions by guest origin. LINE remains the primary channel for guests from Japan and Thailand. Viber has a strong position among guests from the Philippines and parts of Southeast Asia. SMS works as a universal fallback when channel preference is unknown or when a guest's data access is uncertain.
For properties operating across multiple markets or receiving guests from a wide range of origin countries, the answer is not to pick one channel and expect all guests to use it. It is to match the send channel to the guest profile, and to have a fallback when the preferred channel does not connect. That fallback logic is where the program either holds together or breaks down quietly.
For hotels operating in the Philippines or receiving guests from the Philippines, the Viber, WhatsApp, or SMS guide for Philippine businesses covers the channel decision in full. For broader channel selection principles across markets and use cases, the Telerivet channel guide in the knowledge base covers each channel's operational fit and the conditions under which one outperforms another.
For SMS registration requirements, which vary significantly by country and affect whether sender ID and consent procedures are required before you can send to guests in a given market, the Telerivet SMS compliance series covers the requirements for each major market separately.
The question that comes up at this point is usually whether building a guest messaging program means replacing the property management system, buying a new platform, or undertaking a significant integration project. For most independent and mid-market properties, the answer is that it does not have to.
A messaging layer that covers pre-arrival, in-stay, and post-checkout communication can be built around WhatsApp, Viber, and SMS and sit alongside an existing PMS rather than replacing it. If the PMS supports webhooks or API connections, messages can be triggered automatically from booking events: confirmation on reservation, reminder 48 hours before arrival, welcome on check-in, follow-up on checkout. If it does not, the same sequence can be triggered by a staff action, with minimal additional manual overhead.
For hotels already running Oracle Opera, the specific integration question has a detailed answer. See Can Oracle Opera Integrate with WhatsApp, Viber, and SMS? for a walkthrough of what is available and how it is configured across different versions.
For the broader question of workflow logic across channels, Your Guests Are on Five Channels covers the coordination layer in detail, including how to structure routing when different guest types are using different channels simultaneously.
What makes this kind of program work operationally is communication orchestration: the logic governing which channel carries which message, at which point in the guest journey, and what happens when a guest replies. For most properties, a working program does not require that logic to be complex. Three structured touchpoints across the stay, combined with a clear inbound routing approach for service requests, is enough to close the gap between the experience guests expect and the one a fragmented department-by-department setup produces.
Telerivet is an official Meta Business Partner, which matters when hotels are activating WhatsApp Business API routes for the first time.
What is hotel guest messaging? Hotel guest messaging is the use of SMS, WhatsApp, Viber, or other mobile channels to communicate with guests across the pre-arrival, in-stay, and post-checkout stages of their stay. It covers outbound messages sent by the hotel at key moments, and inbound messages sent by guests to reach the right team.
Which channel should a hotel use for guest messaging? Start with where your guests come from rather than where your hotel is located. WhatsApp is the effective global default for international guests. LINE is the primary choice for guests from Japan and Thailand. Viber is widely used by guests from the Philippines and parts of Eastern Europe. SMS functions as a universal fallback when channel preference is unknown or data access is uncertain.
Does hotel guest messaging require replacing the existing PMS? No. A guest messaging program covering pre-arrival, in-stay, and post-checkout communication can be layered alongside an existing property management system. If the PMS supports API connections, messaging workflows can be automated against booking events. If not, the same workflows can be triggered manually by staff with limited additional overhead.
How does structured messaging improve in-stay operations? The primary operational gain is in routing and confirmation. When guest requests arrive through a channel that connects to the right team, and the guest receives a confirmation that the request was seen, the number of requests that fall through the gap between departments drops. This is most visible for multi-step requests that involve coordination between front desk, housekeeping, or F&B.
What is the right timing for post-checkout messaging? A review request sent immediately after checkout, before the guest has processed the stay, is less effective than a follow-up sent the following day that first gives the guest a way to surface anything unresolved. Properties with in-stay messaging records can further refine the sequence based on whether a guest had any issues during their stay and how those issues were handled.
How do SMS registration requirements affect hotel messaging? Business SMS in many countries requires sender ID registration or regulatory approval before messages can be sent. Requirements vary significantly by market, and the rules for guests roaming internationally differ from local sends. If your property operates across multiple countries or receives international guests who may receive SMS while traveling, review the registration requirements for each relevant market before building your send logic around SMS.
Ready to build a guest messaging program across the channels your guests actually use?