Guest Notification System for Hotels: What to Send, and When

A guest notification system is the part of a hotel's messaging setup that sends planned, triggered messages to guests, such as the booking confirmation, pre-arrival logistics, in-stay updates and the checkout reminder, on the channel the guest chose. It is the outbound half of guest communication; the inbox is the inbound half. The difference between a notification system that helps and one that reads as spam is not the tool. It is the rules: one trigger per message, service before promotion, a frequency ceiling, quiet hours and consent captured per channel. The tooling side lives in our guide to hotel guest communication software. This post is the rules.

One line of housekeeping first: messaging rules vary by country and state, and WhatsApp has its own policies, so this is general information, not legal advice.

What is a guest notification system?

A guest notification system is the set of scheduled and triggered messages a property sends to guests, with the channel, timing and consent for each decided in advance. What makes it a system rather than a habit is the matrix, one table of triggers the team maintains, and the three message types that decide how each is handled.

Transactional messages respond to something the guest did: booking confirmed, request received, request completed. Service messages inform the guest about their stay: arrival logistics, a pool closure, a checkout reminder. Promotional messages sell something: an upgrade, a spa offer. The distinction matters because it decides consent and channel. WhatsApp makes it explicit: Meta's platform categorizes templates as authentication, utility or marketing, Meta makes the final call, and a message that did not result from an explicit guest request is likely to be categorized as marketing ^[3]. In plain terms, if you cannot point to what the guest did to deserve the message, it is a promotion, and promotions have stricter rules everywhere.

For where notifications sit in the broader category, and what the software costs, see what guest communication software does and costs.

What notifications should a hotel actually send?

Eight, and I would resist the ninth for a season. Each one is tied to a trigger, and each one either answers a question the guest would otherwise ask or tells them something changed.

The core eight, with sample copy

Sample copy for illustration, 2026. Placeholders in brackets; adapt to your property's voice.

The in-stay service update and the request completed message are the two most properties skip, and they are the two that matter most when something goes wrong. J.D. Power's 2025 North America study of 39,219 branded hotel guests found about 12% of stays involved a problem, and satisfaction dropped 217 points on a 1,000 point scale when one did ^[2]. A guest whose request was fixed and who was told it was fixed has a different stay from one who has to check.

When should each notification go out?

In the window the guest would want it, which is rarely the moment it is convenient to send. The timeline below is illustrative, and the quiet hours band is the part to copy exactly.

Pre-arrival messages follow the booking window: at booking, around seven days out, at 48 hours. The arrival day message goes when the room is actually ready, because "your room is ready" at 9am for a 3pm check-in is a lie with a timestamp. In-stay updates go as soon as the change is known, inside waking hours. The checkout reminder goes the evening before. The thank you goes the day after departure, not the hour.

Quiet hours are the floor. US regulations under the TCPA bar telephone solicitations before 8 a.m. or after 9 p.m. local time at the recipient's location (47 CFR 64.1200(c)(1)); whether that reaches marketing texts a consumer consented to is contested, and a petition for a declaratory ruling was filed in March 2025 ^[5]. My rule is simpler than the law: nothing non-urgent outside 8 a.m. to 9 p.m. in the guest's time zone, and never two messages within an hour of each other unless one is transactional. The pre-arrival timing in detail is in the five-message pre-arrival sequence.

Which channel should each notification use?

The channel the guest used to reach you, and if they have not reached you yet, the one they gave you a number for. In eviivo's 2025 survey of 430 travelers, 58% preferred SMS, WhatsApp or email links for quick exchanges with a property, 25% preferred speaking to a person if follow-up was prompt, 13% preferred an OTA or chain app and 4% wanted a property app or QR code ^[1]. The property app ranks last, and the J.D. Power gap for brand app users (699 versus 631, a 68 point lift) describes loyalty members who were already engaged before they opened the app ^[2].

By message type: SMS and WhatsApp for anything time-sensitive, the 48 hour details, the room ready note, the pool closure. Email for anything with documents or length, the seven day logistics message. Web chat for in-stay replies when the guest is already in a conversation. The one rule that overrides all of these: every notification must be answerable, on the same channel, by a person. A notification sent from a number that cannot hear back is how "the pool is closed" becomes "and nobody answered when I asked where else to swim." That failure has its own page: when replies to notifications go unanswered.

How many messages are too many?

Fewer than you think, and the guest decides. Set a ceiling: no more than one unsolicited message per day during the stay, and a per-stay budget of five or six non-transactional messages from booking to post-stay. Transactional messages, the ones the guest caused, do not count. Promotions never outnumber service messages, and for most stays there is room for one promotion, if that.

I have a high tolerance for a hotel that tells me the pool is closed and a very low one for a hotel that tells me about the spa three times. The second kind trained me to stop reading, which meant I missed the pool message. Frequency is a trust budget, and every message that did not need to be sent spends some of it.

The number to watch is the opt-out rate, weekly. It is the guest telling you the count is wrong, and the CTIA Messaging Principles and Best Practices expect your consent language to have disclosed the message frequency in the first place ^[6], so a guest who opts out after message four has a point. The wider tone and timing rules for texts, including what never to send, are in tone and timing rules for hotel texts.

Do guests have to opt in, and how do you capture it?

For marketing, yes, on every channel. For WhatsApp, yes for anything the hotel sends first. Meta's documentation requires a business to obtain opt-in before messaging, and the opt-in must clearly state that the person is opting in to receive communication and clearly name the business ^[4]. Once a guest writes to you, a 24 hour customer service window opens in which you can reply freely; outside it, only approved templates can be sent ^[3].

For SMS in the United States, the CTIA Messaging Principles (2023 update) expect consent that discloses the program, the message frequency and how to opt out, with terms of service and a privacy policy behind it ^[6]. Service texts tied to the stay are treated differently from marketing in most frameworks, but capture the number for that purpose and say what you will send. Capture it at the booking form and at the moment a guest scans a QR code or taps a stay link. Honor STOP immediately and test it before launch.

Notification matrix: trigger by channel, window, consent and owner

Operator matrix, 2026. Consent notes are general information, not legal advice; confirm channel policies (Meta, CTIA) and local law before launch.

Where ResortConcierge AI helps

The general practice is one matrix, maintained in one place. ResortConcierge sends scheduled and triggered guest notifications on the channel the guest already used, SMS, WhatsApp, email or web chat, so the matrix above lives in one tool rather than three.

Audience targeting is how a property sends a pool closure only to guests in house, or a family activity reminder only to bookings with children, which is the practical meaning of sending a message only to the guests it applies to. And replies to any notification land in the same inbox the team already works, so "the AC is broken" typed in response to a checkout reminder becomes a service request with an owner instead of an unread text.

One scope note: connectors to property management systems (PMS) that would fire the arrival day message from a check-in event are planned. Today, triggers come from stay dates and guest data in the platform.

How do you set this up at one property in two weeks?

Two weeks is enough if you resist the ninth message.

1. Days one and two: pick the eight. Cross off anything on your idea list that does not prevent a question or report a change.
2. Days three to five: write the copy. One ask per message, a reply path in every one, the property's name on first contact. Have someone who did not write them read them aloud.
3. Days six and seven: assign channels and windows from the matrix. Set quiet hours in the guest's time zone, not yours.
4. Days eight and nine: capture consent. Add the checkbox to the booking form and the line to the QR entry page, and test STOP.
5. Days 10 to 12: test on staff phones. Run a fake stay from booking to post-stay and read every message as the guest would, at the time they would get it.
6. Days 13 and 14: go live with the next week's arrivals, and set a weekly 15 minute review of opt-outs, replies and complaints that mention messaging.

The eight messages will not stay eight forever, and that is fine. What should stay fixed is the rule that every new one has to name the question it prevents. Write the matrix this week, hand it to the team, and let the opt-out rate tell you whether you got the count right.