Pre-arrival communication is a sequence of service decisions—not one promotional blast.
A booking confirmation proves what was reserved. A stay planner explains what the guest needs to know. A final reminder protects the travel day. An arrival message handles a real same-day instruction. A request reply confirms whether the hotel can deliver an exception. These are five different jobs, even when one system sends them.
Repeating the same upgrade banner in every message teaches the guest to ignore the sequence. Start with the next uncertainty: dates, total price, cancellation terms, directions, parking, check-in time, accessibility arrangements, dietary information or a late-arrival handover. Promotion is optional; practical clarity is the reason the service message exists.
Give each message a trigger, purpose and stopping rule.
Send from verified reservation events, not a loose calendar assumption. A modified or cancelled booking should update or stop the sequence. Same-day reservations may skip the seven-day planner. A guest already speaking with the hotel should not receive an automated message that contradicts the human conversation.
Timing depends on the property. A resort may need earlier dining and transfer planning; an airport hotel may need a concise arrival instruction close to travel. Test the sequence against short and long booking windows, OTA reservations, group stays, changed dates and bookings without a usable direct contact channel.
| Message | Trigger | Primary job | Stop or change when |
|---|---|---|---|
| Booking confirmation | Reservation accepted | Record dates, room, price, payment and terms | Booking is modified or cancelled |
| Stay planner | About seven days before arrival | Directions, facilities, preparation and useful requests | The booking window is shorter or details are unresolved |
| Final reminder | About two days before arrival | Protect the travel day and surface changed arrival details | A person is already handling the exception |
| Arrival-day note | Confirmed useful same-day event | Provide one timely instruction or owned contact route | No new information would be added |
| Request acknowledgement | Guest asks for an exception | State owner, status and promised update time | The request is confirmed, declined or replaced |
Customise five copy-ready hotel pre-arrival email templates.
Use the workshop below to add a hotel name, guest first name and arrival date. The remaining brackets are prompts for verified property facts. Remove any line the hotel cannot maintain reliably, and never present a request as confirmed until the owning team has accepted it.
Tone matters less than usefulness. A warm sentence is welcome; a vague promise is not. “We will do our best” leaves status unclear. “Guest services is checking this and will update you by 16:00 tomorrow” gives the guest an owner and time.
Turn a template into a useful guest message.
Enter three details, choose the correct stay moment and copy the result. The fields remain in your browser and are never submitted.
SubjectYour reservation at [Hotel name] is confirmed
Hello [Guest name],
Your reservation at [Hotel name] is confirmed for [Arrival date]. Keep this message because it contains the information you may need before travelling.
Please review the room, dates, party size, total price, payment status and cancellation terms in your confirmation. Reply to this message if anything is not correct.
We look forward to welcoming you.
SubjectUseful information for your stay at [Hotel name]
Hello [Guest name],
Your stay at [Hotel name] begins on [Arrival date]. Here are the practical details for a smooth arrival: check-in time, address, parking or transfer information and the best way to contact the hotel on the day.
If you have an accessibility need, dietary requirement or arrival question that the hotel should prepare for, please reply and tell us what would be useful.
We will confirm any request rather than assume it is available.
SubjectTwo days until your stay at [Hotel name]
Hello [Guest name],
We are preparing for your arrival at [Hotel name] on [Arrival date]. Check-in begins at [time]. The hotel address is [address], and [parking or transport instruction] is the simplest way to reach us.
If your expected arrival time has changed, reply here so the front desk can update the handover.
For urgent travel-day questions, contact [hotel telephone or approved messaging channel].
SubjectArrival information for [Hotel name] today
Hello [Guest name],
We look forward to welcoming you to [Hotel name] today. Your confirmed arrival arrangement is [short factual instruction].
If you are delayed or need help finding the hotel, contact [owned telephone or messaging channel]. A member of the hotel team will handle exceptions.
Safe travels.
SubjectWe have received your request for [Hotel name]
Hello [Guest name],
Thank you for telling us about [request]. We have recorded it for your arrival on [Arrival date] and assigned it to [hotel role or team].
The request is [confirmed / still being checked]. We will update you by [time] rather than leave the outcome unclear.
If anything changes, reply to this message and the hotel team will review it.
Decide whether the message is service communication or direct marketing.
The UK ICO explains that a message sent purely for administrative or customer-service purposes is not direct marketing. Add advertising or promotional material and the message becomes direct marketing. That distinction affects the rules that apply; putting an offer inside a booking update does not make the offer administrative.
Classify each message and content block before launch, document the decision and verify current PECR and UK GDPR requirements for the audience and channel. This guide is an operating framework, not legal advice. Where the position is uncertain, obtain qualified advice rather than stretching a service-message label around promotional content.
| Content | Likely role in the message | Control to confirm |
|---|---|---|
| Booked dates, room, payment status and cancellation terms | Administrative service information | Accuracy, security and the correct reservation recipient |
| Directions, check-in time and a confirmed access arrangement | Customer-service information | Current property facts and an owned exception path |
| An upgrade, spa package or paid add-on | Promotional content | Applicable electronic-mail marketing rule and suppression |
| Destination tips with paid partner promotion | May be promotional | Commercial relationship, transparency and applicable permission |
| Reply route for a guest’s current booking question | Customer-service channel | Monitoring, response ownership and data access |
Personalise from confirmed stay context—not assumptions about the person.
Useful personalisation begins with facts the reservation legitimately provides: arrival date, party size, booked room or package, requested accessibility arrangement, known transport booking and hotel facilities that apply. Do not infer a celebration, health condition, relationship or spending appetite from weak signals.
Segmentation should reduce noise. A guest arriving after reception closes needs access instructions. A family may need the booked cot status and breakfast times. A business traveller has not automatically consented to receive a workspace offer, and a guest who booked a spa package does not need to be sold the same package again.
| Known context | Useful message change | Avoid |
|---|---|---|
| Short booking window | Collapse planning and reminder information into one concise note | Sending an expired seven-day sequence all at once |
| Confirmed late arrival | Show the verified access or handover instruction prominently | Generic check-in copy that contradicts the arrangement |
| Booked parking or transfer | Confirm time, location, price and contact route | Promoting the service as if it were not already booked |
| Accessibility request | State confirmed arrangements and the responsible hotel contact | Guessing needs or describing an unverified room as suitable |
| No permitted marketing route | Send only the necessary service information | Adding offers because the booking email address exists |
A guest reply must become an owned hotel handover.
“Reply to this email” is only useful when somebody sees the reply, understands the booking and can assign the next action. Route messages by request type and urgency, retain the original context and show whether the hotel has acknowledged, confirmed or declined the request.
Automation should stop where judgement begins. Accessibility, allergies, disputed charges, complaints, unusual arrival conditions and anything the system cannot verify need a person. The handover should carry the guest’s words, booking reference, source message, promised response time and responsible role—without copying unrelated personal data.
Keep permitted stay context, communication history and the next responsible action visible without turning the CRM into a second PMS.
↗Measure whether the sequence made arrival easier.
Open rate cannot tell you whether the message was correct, timely or useful. Combine delivery signals with hotel outcomes: repeated arrival questions, incomplete requests, time to ownership, accepted add-ons where marketing was permitted, arrival exceptions and guest comments about clarity.
Keep operational and promotional measures separate. A service reminder may succeed by preventing calls even when nobody clicks. A permitted upsell needs revenue and margin alongside opt-out and complaint signals. Review the whole journey by booking window and property type before changing timing for every guest.
| Question | Useful evidence | Watch for |
|---|---|---|
| Did the message arrive? | Delivery and bounce by message and contact source | Repeated failures or outdated addresses |
| Did it answer the travel question? | Fewer repeated directions, parking and check-in enquiries | Replies that repeat information the message should contain |
| Did exceptions reach a person? | Time to acknowledgement, owner and final status | Requests left open at arrival |
| Did permitted offers help? | Attach rate, contribution and fulfilment quality | Opt-outs, complaints or selling unavailable inventory |
| Was arrival smoother? | Exception log, front-office observations and guest feedback | Automation that moves work rather than removing it |
The arrival—not the email—is the proof that the sequence worked.
A polished message followed by a confused handover is worse than a plain message the hotel can honour. Test the journey from a real guest’s reply through the owning inbox or workspace to the arrival list and front-desk conversation. Include changed dates, cancelled bookings and requests that cannot be fulfilled.
Start with one property and the message causing the most repeated work. Approve the facts, permission classification, trigger, exceptions and owner. Run it long enough to observe arrival outcomes before adding another message or channel.
Connect fast answers, approved hotel facts and human handover across the guest journey.
↗Approve the pre-arrival sequence before switching it on
Test the facts, permissions, triggers and human handovers with real booking scenarios. An unchecked item is a launch risk, not a formatting task.
checked
Frequently asked questions
Concise answers to the practical questions hotel teams ask when putting this guide into use.
01What should a hotel pre-arrival email include?
Include the booking facts the guest should verify, arrival date, address, check-in time, parking or transport guidance, the best day-of contact route and a clear way to reply about accessibility, dietary or arrival needs. Confirm requests rather than implying availability.
02When should hotels send pre-arrival emails?
Send the reservation confirmation immediately. A useful stay-planning message can follow about seven days before arrival, with a short factual reminder around two days before. Send an arrival-day message only when it adds information the guest genuinely needs.
03What is a good subject line for a hotel pre-arrival email?
Use a factual subject that matches the stay moment, such as “Useful information for your stay at [Hotel]” or “Two days until your stay at [Hotel]”. Avoid manufactured urgency and make promotional content identifiable when it is included.
04Is a hotel pre-arrival email a service message or marketing?
A message limited to necessary booking and arrival information can be a customer-service communication. Promotional upgrades, packages or partner offers introduce direct-marketing content, so the hotel must apply the relevant electronic-mail marketing rules and suppression preferences.
05How should a hotel personalise a pre-arrival message?
Use verified, stay-relevant context such as the guest name, hotel, dates and confirmed arrangements. Do not expose unrelated profile data or infer sensitive preferences. Personalisation should make the next decision easier, not demonstrate how much data the hotel holds.
06Which pre-arrival messages should not be fully automated?
Accessibility needs, allergies, complaints, disputed charges, unusual arrival conditions and any request the system cannot verify should reach an authorised person. The handover should include the guest’s words, booking reference, promised response time and responsible role.
Current guidance behind this article
This guide combines primary guidance with practical hotel workflow analysis. Product capabilities and integrations should still be verified against the property’s systems, operating rules and current supplier documentation.
- Information Commissioner’s OfficeGuidance on direct marketing using electronic mail
Current PECR guidance explaining electronic-mail marketing, consent and soft opt-in rules, and the boundary between purely administrative service messages and promotional content.
- OpenTravel AllianceOpenTravel specifications and code lists
Travel industry message specifications covering availability, rates and reservations.
- Meta for DevelopersSend messages and the customer service window
How the 24-hour WhatsApp customer service window opens, resets and closes, and what may be sent once it has.
- W3C Web Accessibility InitiativeForms tutorial
Practical guidance for form labels, grouping, instructions, validation and notifications that make surveys easier to use with assistive technology.
