Pre-Arrival Communication for Hotels: Five Messages, Timed Right

A pre-arrival sequence that cuts day-one questions is five messages timed to the booking window, each one answering a specific group of questions the guest would otherwise ask at the desk, sent by email for the long content and by message for the logistics, with one offer in the whole sequence, not five. That is the design. Build it from your own arrival-day question log rather than from a template library, and it will keep paying for itself every time the booking engine sends another bare confirmation. The channel and tooling questions sit in our hotel guest communication software guide; this post is the sequence itself.

A note before we start: messaging consent rules vary by country and by channel, so the consent points below are general information, not legal advice.

Why do guests arrive knowing nothing?

Because the confirmation email from the booking engine was the last thing they heard from you, and it was mostly a cancellation policy. Three months later they land with a tired family, a rental car and a dozen questions that all have the same answer: "it was in the confirmation." It was. Nobody reads a confirmation in August for a trip in November.

OTA guests get even less. In Mews' Data Snap 2024, drawn from thousands of properties, about one in three direct bookers used online check-in versus about one in ten OTA bookers ^[2], which says a lot about how little pre-arrival contact an OTA booking carries. That guest has your name, a date and nothing else. They need the sequence most and are least likely to be in your segments unless you go looking.

The design input is your desk, not a template library. For one week, write down every question that arrives on arrival day. That list, sorted into groups, is the sequence.

Which arrival-day questions can you answer before the guest gets here?

Most of them. The exceptions are questions about the guest's own situation on the day ("is our room ready yet") and anything that goes wrong. Everything else is knowable in advance, and the table sorts the common groups by the message that should handle each.

Arrival-day questions and the message that pre-empts them

Operator mapping, 2026. Groups come from a typical resort's arrival-day tally; your own log will reorder them.

"How to reach us" is the group most properties forget and the one that pays off most, because a guest who knows how to message you asks the next question in chat instead of in the lobby. And "kids and activities" belongs only in messages to bookings with children, which is why the sequence needs segments rather than a blast.

What are the five messages, and when do they go out?

Timed to the booking window, not to your calendar. The first goes out when the booking lands, the last at check-in, and the three in between follow the guest's own planning rhythm: thinking about the trip a week out, packing two days out, traveling on the morning of.

The five messages (sample copy, placeholders in brackets)

Sample copy for illustration, 2026. Placeholders in brackets; adjust timing to your booking window and quiet hours.

Illustrative: a 120 room beach resort builds this for its family segment. Message two gains a kids' club paragraph and a pool rules line about swim diapers. Message three adds "the stroller-friendly entrance is on the beach side." Nothing else changes, and the family arriving on Saturday afternoon has nothing left to ask except where to put the towels.

Bookings made under a week out collapse to three: confirmation, 48 hours and arrival morning. There is no point in a plan-your-stay email two days before the plan-your-stay message.

Which channel should each message use?

Email for the planning content, messaging for the logistics. Email is read more than most GMs believe: Revinate's 2026 benchmark, drawn from its customers' email programs, found confirmation emails open at 67% and pre-arrival emails at 58% ^[1]. The guest a week out is planning, sitting down and willing to read a few paragraphs with links. That is the moment for message two.

Two days out and on the morning of, the guest is traveling and wants one screen with three facts, where they are already looking. eviivo's 2025 survey of 430 travelers found 58% preferred SMS, WhatsApp or email links for quick exchanges with a property, and only 4% wanted a property app or QR code to communicate ^[3]. The broader argument for messaging over a download is in why messaging beats an app for most guests, and it applies with particular force to a guest in an airport.

On consent: SMS to a number the guest gave for the stay is generally treated as service messaging, but capture the number for that purpose and say so. WhatsApp is stricter: Meta requires documented opt-in before a business sends the first message, and the opt-in must name the business and state what the person is agreeing to receive ^[4]. Collect it at booking or in message one, or send messages three and four by SMS instead.

Should the sequence include upsell offers?

One, placed where the guest is already thinking about it, and never in the logistics messages. The data supports both halves of that sentence. Revinate's 2026 benchmark found pre-arrival email campaigns convert at 2.5%, with upsell revenue per booking of $86 on confirmation emails and $82 on pre-arrival emails ^[1], so the planning email is a real revenue moment. Only 36% of hotels globally run email upsells at all ^[1], which means most are leaving the moment empty.

But the sequence exists to answer questions. A 48 hour message that leads with a spa offer has stopped being logistics and started being marketing, and the guest will treat the rest of your messages accordingly. Put the one offer in message two, make it relevant (breakfast, early check-in, the kids' club package for families), and let it be declined in one tap. Which offers guests actually buy, and when they resent being asked, is the subject of the upsell moments guests say yes to.

How many messages are too many?

Five is the ceiling, and if you cannot name the questions a message prevents, cut it. I have a very low threshold for this as a guest. The property that sent me six emails before a four night stay taught me to stop opening them, which meant I missed the one that mattered. Frequency is a trust budget, and you spend it every time a message arrives that did not need to.

Three guardrails. Never send two messages within 24 hours unless one is a reply. Hold everything outside the guest's local waking hours; a 6am "we are ready for you" lands badly in another time zone. And make every message answerable, with a real reply path to a person, because a number that cannot hear back is the fastest way to make a guest resent a message. A sequence that answers questions and then waits is service. One that keeps talking is noise. The rules for the whole in-stay cadence, not just pre-arrival, are in what to send guests, when, and how to not become spam.

How do you build it with the team you have?

Three pieces: segments (arriving in 48 hours, arriving today, families, OTA bookers), templates (the five messages with placeholders) and one knowledge base, the single source both the messages and the desk answer from, so the shuttle time in message three matches the one the agent gives at the counter.

The general practice is a scheduled message to a segment on the channel the guest can receive it. ResortConcierge AI does this through scheduled notifications by segment and channel, sending each message by email, SMS or WhatsApp to the guests it applies to, such as families with the kids' club package rather than every arrival.

The timing piece is a segment, not a spreadsheet. Targeting a message to guests arriving in 48 hours is how message three goes out on time without someone remembering to send it, and every message can end with the concierge link so a guest who still has a question asks it in chat and gets a knowledge base answer instead of calling the desk.

One scope note: connectors to property management systems (PMS) that would trigger messages from reservation events automatically are planned. Today, segments are built from guest and stay data entered in the platform or imported, which is enough to run the sequence and not yet enough to forget about it.

How do you know it worked?

Count day-one questions per arrival for one week before launch, by hand, at the desk and in the inbox. That is your baseline, and without it you will have a feeling instead of a result. Then run the sequence for 60 days and count again at 30 and 60.

Add three more numbers. Desk wait on arrival days during the peak check-in hour. Reply rate to each message, which tells you which ones guests actually read. And opt-out rate, which is the guest telling you the count is wrong. ResortConcierge's analytics shows which questions still arrive on day one, and those questions are the next version of message two.

Start with the tally sheet, not the templates. Seven days of arrival-day questions will tell you exactly what messages one through five need to say, and when you build them from that list rather than from a vendor's library, the guest who steps up to your desk on Saturday will already know where to park.