Hotel Push Notifications: When to Send, What to Say, and What to Avoid

A push notification from a hotel can do something almost no other channel can: arrive on a guest's lock screen, in the middle of their stay, with a message that is relevant to exactly where they are and what they are doing. Done well, it feels like the hotel reading their mind. Done poorly, it feels like a marketing department that does not know — or care — what the guest is actually experiencing.

The gap between those two outcomes is not primarily a technology gap. It is a strategy gap. The mechanics of push notifications are the same regardless of platform. What separates hotels that see 25% open rates and measurable revenue impact from those that see mass opt-outs in the first 48 hours is the decision framework for what to send, when, and to whom.

Why push notifications matter more for hotels than any other industry

Most industries send push notifications to drive repeat engagement with a product the user accesses at home, at work, or on the commute. Hotels have a different window: a short, intense relationship with a guest who is physically present, emotionally engaged, and — crucially — making real-time decisions about how to spend their time and money.

A guest standing in their room at 11am on a Wednesday is deciding right now whether to order room service or go to the restaurant, whether to book a massage or go explore the city, whether to extend their stay or check out on time. A well-timed, relevant notification can influence all three of those decisions in real time, in a way that a post-stay email never could.

This is the unique leverage of hotel push notifications: the guest is physically present and contextually engaged. No e-commerce brand, media platform, or travel OTA has this moment. Hotels do — and most use it for the equivalent of a generic newsletter.

The 5 types of hotel push notifications that actually get opened

Type 1: Pre-arrival preparation

Pre-arrival notifications are the highest-open-rate category in hotel push messaging. Sent 24–48 hours before check-in, they reach a guest who is actively thinking about their upcoming stay and has high receptiveness to anything that reduces friction or adds anticipation.

High-performing pre-arrival notifications provide practical value: online check-in availability, directions and parking, early check-in availability, and what to expect at arrival. They are not promotional — they are genuinely useful to a guest preparing for their trip. The implicit message is: this hotel is organised and thinking about my arrival.

• "Your room will be ready from 3pm. Online check-in is now available — skip the queue."
• "Parking is available on-site at £15/night. Reserve your spot in the app."
• "Early check-in from 11am is available for your dates — upgrade your arrival for £20."

Type 2: In-stay service updates

In-stay service notifications are the most operationally useful type: confirming that a request was received, updating the guest on timing, or notifying them that a service is ready. These are not marketing messages — they are service messages that happen to be delivered through a notification channel.

Examples: "Your room service order will arrive in 20 minutes," "Your spa appointment is confirmed for 4pm — arrive 10 minutes early for a welcome drink," "The extra towels have been delivered to your room." These notifications close the loop on service requests and dramatically increase guest satisfaction scores because they eliminate the uncertainty that follows a request with no acknowledgement.

Type 3: Contextual upsells

Contextual upsell notifications are the highest-revenue category — but only when they are genuinely contextual. A notification about the spa sent to a guest who has already been to the spa twice is a repeat opportunity. The same notification sent to a guest who checked in six hours ago and has not opened the app yet is a cold sell.

High-converting contextual upsell patterns include: sending a restaurant booking prompt at 4pm on the day of arrival (when guests are thinking about dinner), sending a late-checkout offer at 8am on the last day (when the guest is weighing their options), and sending a spa notification to guests who have searched spa content in the app without booking.

Type 4: Checkout preparation

Checkout preparation notifications reduce front-desk congestion, improve late-checkout revenue, and create a structured farewell moment that influences post-stay sentiment. Sent at 8am on the final day, they can include: express checkout availability, late-checkout options and pricing, luggage storage info, and transport booking links.

Properties that automate this notification report meaningful reductions in checkout queue length and a consistent uptick in late-checkout revenue — not because guests did not want a late checkout before, but because the prompt arrived at exactly the moment they were deciding how to structure their morning.

Type 5: Post-stay follow-up

Post-stay notifications are the most time-sensitive type: they must arrive within 2–4 hours of checkout to catch the guest while the stay is fresh and before they have moved on mentally to their next destination. They should include a review link, a brief thank-you, and optionally a loyalty incentive for direct rebooking.

Properties that automate post-stay notifications with a direct review link see review submission rates 3–5x higher than those that rely on email alone. The mobile context matters: the guest is already on their phone, typically still in transit, and more likely to take a 45-second action than to revisit an email later in the day.

Timing rules that protect your notification channel

Notification timing is the most important variable after relevance. A well-written notification at the wrong time — 11pm, or the morning of arrival when the guest is in transit — reads as intrusive and triggers opt-out. These are the timing rules that consistently protect open rates and opt-in retention:

1. Never send between 10pm and 7am local time. No exceptions, including automated triggers.
2. Limit to a maximum of 2 push notifications per day during a stay. Even relevant content loses goodwill when it arrives too frequently.
3. Pre-arrival notifications should land 24–48 hours before check-in. Earlier is too forgettable; later creates last-minute stress.
4. Upsell notifications should respect guest activity windows: not during busy arrival periods, not immediately after a complaint or service issue.
5. Post-stay notifications should be sent within 4 hours of checkout. After 24 hours, the review conversion rate drops by more than half.

Copy principles for push notifications guests actually read

Push notification copy operates under strict constraints: approximately 50–70 characters before truncation on most lock screens, zero context from the content that came before, and a reader who is making an instant open/dismiss decision. These constraints shape every effective push notification ever written.

• Lead with value, not brand: "Spa available from 2pm" not "Hotel+ Spa — Book Now."
• Be specific about the thing: "Italian restaurant, 7pm tonight — 2 tables remaining" not "Don't miss our dinner service."
• One action only: every notification should have a clear single action the guest takes immediately or ignores entirely.
• Use the guest's name sparingly: personalisation works, but overuse feels algorithmic rather than personal.
• Avoid urgency manipulation: "Last chance!" and "Only 2 left!" copy damages trust over a multi-night stay faster than in e-commerce, because the guest can verify the claim in person.

Building an opt-in rate worth having

Opt-in rate is the foundational metric for a push notification channel. A 15% opt-in rate means 85% of your guests are unreachable through this channel regardless of message quality. A 60% opt-in rate means the majority of your guests are available for the right message at the right time.

The ask for notification permission should never come at the moment a guest first opens the app. At that moment they have zero trust history with the channel and no reason to grant permissions. Ask for notification permission after the guest has received value: after they have used the local guide, after they have submitted a request that was acknowledged, after they have received a useful service update. The relationship earns the permission.

The permission request itself should be framed around the specific value it unlocks: "Enable notifications to get real-time updates on your requests and tailored suggestions during your stay" outperforms the system default "Allow [App] to send you notifications" because it answers the guest's implicit question: what am I getting for this?

Mistakes that kill your push notification channel

The fastest way to destroy a notification channel is to send messages that feel irrelevant, interruptive, or opportunistic. Opt-out is a one-tap action and it is permanent. These are the most common ways hotels damage their push channels:

• Sending more than two notifications per day: guests tolerate high-frequency notifications from messaging apps where they are in an active conversation. A hotel is not an active conversation.
• Sending the same message to all guests regardless of context: the couple celebrating an anniversary and the solo business traveller on a one-night stay are not the same audience.
• Using push to recover from a service failure: "Sorry for the inconvenience — here's 10% off your next stay" via push notification after an unresolved complaint escalates, not resolves, the situation.
• Generic promotional messages: "This weekend only — spa offer!" has the same open rate as email subject lines and does not belong in a channel guests have chosen to allow close access to.
• Ignoring the opt-out signal: when a segment's opt-out rate spikes, it means the messages to that segment are wrong — not that push notifications are wrong. Investigate before scaling.