The Pre-Arrival Message Sequence: What to Send, When, and Why Most Templates Don't Work Here

A pre-arrival message sequence is five messages sent between the moment a guest books and the moment they walk through your door. For a small UK property its job is not to sell them a bottle of prosecco. Its job is to stop the booking falling over during the five or six weeks of silence that follow it, and to answer — once, in writing, before they ask — the three questions you otherwise answer several hundred times a year.

Almost every guide to this is written for a hotel with a marketing database, and it opens with "send a pre-arrival email." That advice fails at the first step for most independents, because you do not have most of your guests' email addresses and you are not allowed to have them.

Start there.

You cannot email most of your guests

Independent properties take 63.4% of their bookings through OTAs. What you actually receive with those bookings is not what the templates assume.

On the five-room B&B this journal has been modelling all month — 1,043 room nights a year, two-night average stay, 522 bookings — that splits roughly 331 OTA and 191 direct. A real, usable email address exists for 36.6% of your bookings.

So the first design decision in a pre-arrival sequence is not what to write. It is: the same five messages have to go out over three different pipes, and two of those pipes are somebody else's.

That is annoying, and it is also the reason this is worth setting up properly rather than improvising. A sequence that lives in your booking system and fires down whichever channel the booking arrived on is a system. A sequence that lives in your email client is a system that covers a third of your guests.

The silence problem

Average lead time for an independent's booking is 40 days, and 47 days in EMEA. Call it six weeks between "booked" and "arrived."

Six weeks is a long time to say nothing to someone who has an OTA cancellation button in their pocket. Cancellation rates for independents run 21.8% on OTA bookings and 10.6% on direct. Blended across the model's channel mix, that is about 92 of 522 bookings a year — 17.7% — that book and then don't come.

You will not talk all of those out of it. Plenty are genuine changes of plan. But a booking that has heard from you twice, by name, with a note about the parking and a line about what time breakfast runs, is a different kind of booking from one that has heard nothing since the confirmation screen.

Here is the number that should decide how much effort you put into this. At the model B&B's ladder-year ADR of £100.15 and a two-night average stay, one booking is worth £200.30. Save one a month and that is £2,404 a year.

Hold that against what the sequence is usually sold on, below.

What the sequence is actually worth

The industry benchmarks for this all come from hotel CRM data — large properties, restaurants, spas, car parks, priced in dollars. They are worth knowing and worth discounting.

Those benchmarks put confirmation emails at a 67.3% open rate and pre-arrival campaigns at 57.7% open and 2.5% conversion, generating around $82 per converted booking (£60.89 at 0.7426). Upsell adoption is highest in EMEA at 49%. The categories that convert are food and beverage (34%), check-in and check-out timing (24%), and activities (16%).

Run that across the model property honestly:

The upsell number is the smallest one on the page. A five-room B&B does not have a spa to sell. What it has is early check-in, late checkout, parking, a taxi booked, a packed lunch, a bottle in the room — a basket worth about £25, and at the benchmark conversion rate that is thirteen sales a year.

Note which upsell category is second on the list, though: check-in and check-out timing, 24%. That one costs you nothing to supply on most dates and is the only one a five-room property can sell at scale. If you sell anything in this sequence, sell time.

The time it gives you back

Three message exchanges per booking, three minutes each, is nine minutes of back-and-forth per booking. At 522 bookings that is 78 hours a year — an hour and a half every week — worth about £994 at the April 2026 National Living Wage of £12.71.

A sequence that reliably answers two of those three exchanges before they are asked takes it to 26 hours, saving 52 hours a year (£663). On the twelve-room hotel: 238 hours down to 79, saving 159 hours a year (£2,016), which is three hours a week of somebody's actual time.

The third exchange survives. It is the genuinely bespoke one — the dog, the anniversary, the 4am flight — and you should not want to automate it.

The five messages

Timings are counted from arrival day, except the first.

1. Confirmation-plus — immediately on booking

The OTA sends a confirmation. It is a receipt. It does not sound like you, it does not say where to park, and it is the last thing many guests read for six weeks.

Send your own within the hour. It is the highest-opened message you will ever send (67.3%), so it carries the load:

• Their name, dates, room, number of guests, total, and what is included — breakfast, parking, anything they've already paid for

• Your cancellation terms restated in one plain sentence, and the date the free window closes

• The balance due date, if there is one

• One line of human welcome that a receipt cannot do

• How to reach you, and how you will reach them

What it prevents: "did that go through?", "is breakfast included?", "can I still cancel?" It also, quietly, is the message that makes the cancellation terms theirs rather than a surprise.

2. The week-before — seven days out

This is the one most properties skip and the one that does the work. Seven days is when a guest starts actually planning the trip: trains, dinner, whether to bring the dog.

• Arrival window, and what to do if they will miss it

• Parking, in specifics — where, whether it's free, what to do if it's full

• Breakfast times, and whether they need to tell you anything

• Two or three genuinely local recommendations, not a directory

• A gentle prompt for anything you need to know: dietary requirements, arrival time, celebrating anything

The recommendations are worth a moment. Guests want them — 40.7% ask for local recommendations — but they want three good ones from someone who lives there, not forty from a widget. Name the pub. Say what to order.

What it prevents: the parking question, the arrival-time question, and about half the "we're going to be late" calls.

3. Arrival day — the morning of, or the evening before

Short. Practical. Read on a phone, probably at a station.

• The address, again, with a map link and the thing that stops people driving past

• The check-in time and what happens if they're early

• Door code or key arrangement if and only if it is a self-access property — and if so, on the day, not a week early

• Your phone number as a tappable link

Check-in instructions are the single most-wanted piece of pre-arrival information at 88.7%. This is the message that has to land.

4. In-stay — the morning after arrival

One line, no questions that create work: "Everything all right with the room?" Sent once.

The point is not service recovery theatre. It is that a guest who tells you about the radiator on Tuesday morning tells you instead of telling TripAdvisor on Friday.

5. Post-stay — the day after checkout

Thank them. Ask for the review. And — read the next section before you do anything else here — this is the message where you may want to invite them back directly.

The line where a service message becomes marketing

This is the part the American templates cannot help you with, and it is the part that matters if you are sending from a UK property.

Messages 1 to 4 above are service messages. They exist because the guest has a booking and you are performing it. You need no consent to send them and no unsubscribe link, in the same way a restaurant's booking confirmation text is not marketing.

The moment you add "and here's 10% off your next stay," or "join our newsletter," or "we've got dinner offers in November," that message is direct marketing, and UK rules apply.

You can usually still send it, under what the ICO calls the soft opt-in. All five of these must be true:

1. You obtained the contact details yourself

2. You obtained them "while selling or negotiating to sell a product or service"

3. You are marketing only "your similar products and services"

4. You gave them the chance to refuse or opt out when you collected the details

5. You give them the chance to opt out in every subsequent message

Three practical consequences for a small property:

The OTA guest is not covered. You did not obtain those details — the OTA did, and gave you an alias. The soft opt-in runs on details you collected while selling. It does not travel through someone else's platform. Marketing an OTA guest through the OTA's own inbox is also, separately, against the platform's rules.

Condition 4 is the one properties fail. The opt-out has to exist at the point of collection — a checkbox on your booking form — not just at the bottom of the email later. If your booking engine does not have one, you are not covered by the soft opt-in for anybody, and adding one is a ten-minute fix worth doing before you send message 5.

"Similar products and services" is not infinitely elastic. Inviting a past guest back for another stay is similar. Emailing them about a friend's yoga retreat is not.

And in every message: don't hide who you are, and give a working way to opt out.

None of this is a reason to avoid the post-stay message. It is a reason to make message 5 the one place in the sequence where the marketing lives, with an unsubscribe link, sent only to guests whose details you collected yourself — and to keep messages 1 to 4 clean, so they never need one.

This is a description of the rules as published, not legal advice. If you are running a larger list or doing anything more elaborate, check it with someone who does this for a living.

What to automate, and what not to

Automate messages 1, 2 and 3. They are the same every time, they are the ones that save the 52 hours, and a guest cannot tell the difference between a good template and a typed message — because a good template is a typed message, typed once.

Send message 4 by hand, or at least read the replies by hand. It is one line a day.

Message 5 can be automated, but check the arrivals list first. Sending a cheerful review request to the guest whose boiler failed is worse than sending nothing.

The test for any of it: if a reply arrives, does it reach a human quickly? An automated sequence with a no-reply address on it is a broadcast, and guests can tell.

Three things to leave out

Door codes more than a day early. A code sent three weeks out lives in a stranger's message history forever, gets forwarded, and is still valid when they get home. Send it on the day.

Anything behind a login. If your pre-arrival information requires the guest to create an account and remember a password, they will not read it. The thing that works is a link that opens.

The long one. There is a temptation to put everything in message 2 because you finally have their attention. Guests want check-in instructions (88.7%), WiFi and appliances (51.0%), house rules (43.1%) and recommendations (40.7%) — in that order. Emergency contacts came in at 8.3%. Write to the order, and keep each message to one screen.

The pre-arrival message sequence on one page

Delivery preference, from the guest side: 44.1% want text or WhatsApp, 23.0% email, 19.1% platform messaging. That is why message 3 is phone-first and message 5 is not. Push the urgent one to where they already are; put the one they might want to keep in an inbox.

FAQ

How far in advance should I send a pre-arrival message? Two of them: one within an hour of the booking, and one seven days before arrival. With average lead times of 40 days globally and 47 in EMEA, a single message on arrival day leaves about six weeks of silence in between, which is when cancellations happen.

Can I email a guest who booked through Booking.com? Not at their real address. Booking.com states plainly that it does not share private email addresses and that both sides see only an anonymous alias, and asks partners to keep communication on the extranet or the Pulse app. You do get a phone number on the reservation page. For Airbnb there is no email at all, and the phone number only appears once the reservation is confirmed.

Do I need consent to send pre-arrival messages? Not for service messages about a booking the guest has made — a confirmation, arrival instructions, a balance reminder. The moment you include an offer, a newsletter sign-up or a discount for a future stay, it becomes direct marketing and you need consent or the soft opt-in, which requires among other things that you collected the details yourself and offered an opt-out at that point.

What should I actually put in the message the day before arrival? Address with a map link, check-in time, what to do if they arrive early, and your phone number as a tappable link. Access codes only if it's a self-access property, and only on the day. Check-in instructions are what 88.7% of guests say they want most.

Will a pre-arrival sequence make me money? Some, but probably not where you expect. On a five-room property the upsell revenue is worth a few hundred pounds a year, the time it saves is worth around £663, and one cancellation prevented per month is worth £2,404. Treat it as a retention and time tool that happens to sell the occasional late checkout.

Should I use email or WhatsApp? Both, for different messages. Guests asked to receive pre-arrival information by text or WhatsApp 44.1% of the time and email 23.0% of the time — so the urgent, day-before message belongs on the phone, and the longer confirmation belongs in an inbox where they can find it again. For OTA bookings, the platform's own messaging is usually where you have to start.

Whichever channel a booking arrives on, the sequence only works if one system knows who is arriving, when, what they've paid and what channel they came from — which is the same thing your arrivals list and your folios already need. Stayvieo keeps bookings, folios and card payments for every channel in one place, with the message centre and review manager on every plan from £29 a month.

See how it works.