Pre-arrival guest messaging is the automated process of sending timed communications to hotel guests between their booking confirmation and check-in date. A standard sequence includes a booking confirmation, a reminder with upsell options sent ten to fourteen days before arrival, and a logistics message the day before check-in.The most commonly used channels are WhatsApp, Viber, and SMS.
The window between a booking confirmation and a guest's check-in is one of the most valuable communication opportunities a hotel has. It is also, at most properties across the Philippines, Indonesia, Thailand, Vietnam, and Malaysia, managed almost entirely manually. The same pattern holds at independent and mid-size hotels in Kenya, Tanzania, South Africa, and across much of East and Southern Africa..
A typical Reservations team in this region is running three or four communication tools simultaneously: WhatsApp Business on a phone, a Viber account on another device, Facebook Messenger open in a browser tab, and SMS going out through a separate dashboard. Each channel operates independently. When a guest sends a WhatsApp inquiry and then follows up on Messenger, a different staff member picks up the thread with no context from the previous exchange. Nothing is connected. Nothing is automated. And the guest list for next week is sitting in the property management system waiting for someone to export it, open a spreadsheet, and start writing individual messages.
At scale, this breaks down fast.
Properties running between 1,000 and 1,500 arrivals per month, which is a reasonable midsize operation in Manila or Cebu, typically want to send three to five pre-arrival touches per guest. A booking confirmation goes out immediately. A reminder with an upsell offer - room upgrade, early check-in, spa package goes out roughly two weeks before arrival. A logistics message covering directions, parking, and check-in timing goes out the day before. At 1,200 guests a month and three touchpoints each, that is 3,600 messages that someone on the Reservations team is currently composing or scheduling manually.
The pain is not the messaging itself. It is the absence of any trigger logic, timing automation, or delivery visibility. Staff members are doing calendar math by hand to determine when reminders should go out. They are checking sent folders across multiple apps to see what a given guest received. When a booking is cancelled or a check-in date changes, there is no automated update to the message queue, someone has to catch it and manually suppress the sequence.
This is not a technology gap. The tools to solve it exist. It is a workflow that was never properly built.
A structured pre-arrival sequence is not complicated. It is a triggered drip: a set of messages, timed relative to booking date or check-in date, sent on the guest's preferred channel with a fallback to SMS if the primary channel fails to deliver.
The booking confirmation fires immediately on reservation. It should carry the guest's name, their room type, the check-in date, and a contact channel for questions, not a generic template, but one that reflects what the guest actually booked. The mid-sequence message, sent ten to fourteen days out, is where upsells belong. Guests are still in planning mode at that point; a well-timed offer for a room upgrade or an activity package lands differently than the same offer at check-in. The day-before message handles logistics: arrival time, parking, any property-specific instructions.
Each of these touches is personalized from data the hotel already has. The guest's name, booking details, and arrival date are sitting in the property management system. What is missing is the connective layer that reads that data and fires the right message on the right channel at the right time.
The first objection that comes up in almost every hospitality technology evaluation in this region is PMS integration. Oracle Opera is the most common system at mid-to-large properties in the Philippines. Hotelogix, Cendyn, and SiteMinder appear across the broader APAC market. The assumption is that automating guest communication requires a live API connection to the PMS, and that building that connection is a long, expensive project.
It is not required to get started.
A CSV export from Opera or any PMS contains everything a pre-arrival sequence needs: guest name, phone number, booking date, check-in date, room type. Scheduled against those date fields, a properly configured messaging platform can run the full pre-arrival drip with personalization and channel fallback without any API integration. The integration project can be scoped and built in parallel. The automated workflow can go live on real guest data this month.
This matters because it decouples two problems that are often bundled together. Whether or not your PMS will eventually connect via API is a separate question from whether your Reservations team should still be writing individual WhatsApp messages tomorrow morning.
Channel preferences differ significantly by market, and any pre-arrival messaging strategy has to account for them. In the Philippines, WhatsApp and Viber are both heavily used - Viber in particular has a strong footprint that properties further north in the region often overlook. Facebook Messenger has high penetration across the region, especially among leisure travelers. SMS remains the universal fallback: every phone number can receive it, no app installation required, and delivery rates are consistent in a way that chat apps cannot always match.
A channel-aware pre-arrival sequence does not pick one channel and commit to it. It attempts delivery on the guest's preferred channel and falls back to SMS if that attempt fails or goes undelivered within a defined window. This is not a sophisticated concept, but most properties are not running it, they are running a single channel per staff member, per shift, per device, and losing messages to app-specific delivery failures they cannot see. If you are sending pre-arrival messages to guests, treating channel fallback as a strategy rather than an afterthought is one of the lowest-effort improvements available.
In East African markets, particularly Kenya, Tanzania, and South Africa, WhatsApp holds a similarly dominant position, though without the Viber layer that matters in parts of Southeast Asia. SMS carries even greater weight as a fallback in these markets, where feature phone usage remains significant and data connectivity is less consistent outside major cities.
For properties in the Philippines specifically, messaging regulations apply to commercial outbound SMS. The Philippines business messaging compliance post covers what organizations need to know before scaling automated outbound volumes.
Pre-arrival automation is the priority, but it is worth noting what becomes possible once the workflow exists. A property with 2,000 to 3,000 guests on site during a peak weekend has a contact list and a set of channel preferences already on file from the pre-arrival sequence. Pushing a restaurant promotion at noon, an activity offer on a slow afternoon, or a late checkout upsell the night before departure requires no new data collection. The channel is already open.
Most properties in this region do not have a mechanism to reach guests once they have checked in without physically approaching them. Building that capacity starts with the pre-arrival workflow -- not as an add-on, but as the same sequence extended a few steps further.
The manual approach to pre-arrival communication is not a permanent state. It is a workflow that has not been replaced yet. The guest data exists. The channels exist. The sequence logic is not complicated. Three of the most common guest communication journeys are the same ones every Reservations Manager, whether in Southeast Asia, East Africa, or anywhere independent hospitality operates at volume is already running by hand.
Frequently Asked Questions
Do hotels need a PMS integration to automate pre-arrival messaging? No. A scheduled CSV export from a property management system like Opera contains all the fields a pre-arrival sequence requires: guest name, phone number, check-in date, and room type. Automated sequences can run on that data without any API integration in place. However, integration does make things a lot smoother.
Which messaging channels should Southeast Asian hotels use for pre-arrival communication? WhatsApp and Viber are the primary channels for guests in the Philippines, Indonesia, and Malaysia. SMS is the recommended fallback for guests who do not have either app installed or have unreliable data connectivity.
How many pre-arrival messages should a hotel send? Three touchpoints cover most guest journeys: a booking confirmation on reservation, a reminder with an upsell offer ten to fourteen days before arrival, and a logistics message the day before check-in.
Telerivet supports multi-channel hotel guest communication across WhatsApp, Viber, and SMS from a single workflow layer, including Viber Business API connectivity for properties with existing Viber accounts.