How Should a Hotel Text Message Guests? Tone, Timing and Rules

Good hotel texting is short, warm, timed to the guest's day, and limited to things the guest asked for or needs to know. That is the whole standard; the rest of this post is how to get eight people on two shifts to sound like one calm person. A text is the most intimate channel a property has. It arrives next to messages from the guest's family, which is why it is the easiest channel to get wrong and the one guests remember. The channel mechanics, especially for WhatsApp, are in our guide to WhatsApp automation for hotels; this is about the words.

A quick note before the rules: texting consent and timing rules differ by country and state, and WhatsApp has its own policies, so this is general information, not legal advice.

How should a hotel sound in a text?

Warm, plain and brief, with one ask per message. Name the property the first time you write, and sign with a first name after that. Use the words a person would use at the desk, not the brand book's. The test is whether the message sounds like it came from someone who was also, at that moment, helping a family find the elevator.

The stakes for getting tone wrong are not small. In Zendesk's 2025 CX Trends research, drawn from about 5,100 consumers in 22 countries in mid-2024, 63% said they were willing to switch to a competitor after one bad experience ^[4]. A text that reads as careless is a bad experience that fits on one screen.

Three rewrites:

Stiff: "Dear Valued Guest, we are pleased to inform you that your accommodation is now prepared for occupancy. Kindly proceed to the Front Desk at your convenience." Rewritten: "Hi Daniel, your room is ready. Come to the desk whenever suits you. Maria, Front Office."

Too casual: "Hey!! Room's ready 🎉🎉 come grab ur keys!!" Rewritten: the same as above. The casual version is not friendlier, just louder.

Vague: "We are looking into your request." Rewritten: "Got it. Housekeeping is bringing two extra towels to 214 now, should be there by 4:15. Reply here if not."

The rewrites share a name, a time, a next step and nothing else. For the pre-arrival versions, a pre-arrival sequence that cuts day-one questions has sample copy for each message.

What time of day can a hotel text guests?

Default to the guest's local 8 a.m. to 9 p.m., and treat that as a floor. In the United States, TCPA regulations bar telephone solicitations before 8 a.m. or after 9 p.m. at the called party's location (47 CFR 64.1200(c)(1)); whether that reaches consented marketing texts is contested, and a petition for a declaratory ruling was filed in March 2025 ^[1]. The law is unsettled. Your house rule does not have to be.

My rule: nothing non-urgent after 9 p.m. or before 8 a.m. in the guest's time zone, which is not always yours. A traveler who landed from Europe at 4pm is asleep by 9. Hold the checkout reminder until morning. Hold the spa offer forever. The only message that crosses the line is urgent and about safety: a weather warning, a water shutoff.

The schedule from booking to post-stay is in which notifications to send and when. The etiquette rule sits on top: when in doubt, it can wait until 8.

Should you use the guest's name, emojis and exclamation points?

Name, yes, once. Emojis, rarely, and never in bad news. Exclamation points, one at most, and most messages are better with none. The table is the whole standard in twelve rows.

Hotel texting: do and do not

Recommended practice, 2026. Not drawn from a survey.

I notice this as a guest more than I would like to admit. A message that opens with my name and closes with a person's name feels like a note. One with two party poppers and my name three times feels like a system that knows my name, which is a slightly worse feeling. It is the difference between being addressed and being processed.

How fast should a hotel reply to a guest text?

Acknowledge within minutes, resolve by a stated time, and never leave a thread without a last word from the property. The acknowledgment does not need the answer. "Got it, checking with housekeeping, back to you by 2:30" is a complete first reply, and it buys the time the real answer needs.

In eviivo's 2025 survey, 58% of travelers preferred SMS, WhatsApp or email links for quick exchanges, and 25% preferred a person "as long as follow-up is prompt" ^[3]. Prompt is doing all the work in that sentence. I will not give you a minute benchmark, because the figures that circulate are vendor claims or a decade old. Set your own: acknowledge in five minutes during the day, state a time, and hit it.

The last word matters. A thread that ends with the guest's "thanks" feels finished to the staff member and unfinished to the guest, who does not know if it was read. "You are welcome, enjoy the pool" costs four seconds. Silence is the one reply a guest always notices.

What should a hotel never send by text?

Six things. Bad news alone: a cancelled reservation, a room change, a failed card. Text to say you are calling, then call. Disputed charges, because a text is a permanent record of the argument and the guest will screenshot the worst line. Arguments of any kind; if a thread turns, move it to a call or a face. Personal numbers; staff never text from their own phones. Anything unverified: "I think the pool opens at 7" is worse than "let me check." And marketing without opt-in.

That last one has rules behind it. The CTIA Messaging Principles and Best Practices (2023 update) expect consent that discloses the program, the message frequency and how to opt out, backed by terms and a privacy policy ^[2]. WhatsApp requires documented opt-in before a hotel writes first, naming the business ^[5]. Service texts tied to the stay are treated differently from marketing in most frameworks, but still capture the number for that purpose and say what you will send. The channel-specific mechanics are in running WhatsApp without losing control.

How do you keep the tone consistent across a whole team?

Templates with editable fields, a shared inbox so context carries, and a monthly read-through of 20 random threads. Templates handle the messages you send fifty times a week: room ready, request received, request completed, checkout reminder. They should sound like a person and be editable by one, so an agent can add "and the pool is open late tonight" without rewriting. ResortConcierge AI keeps those as editable message templates, so whoever is on shift starts from the same warm, brief draft.

The second person to pick up a thread is where tone breaks. They do not know the guest was already told the towels were coming, so they ask again, and the guest is now being processed. One inbox with the history, for every channel, is the fix, and ResortConcierge keeps every channel there with the history attached, which is less a feature than a courtesy.

Then language. Etiquette does not survive the moment a guest texts in Arabic or Hebrew and the reply comes back in English. ResortConcierge answers in any of 11 supported languages, including right to left scripts, which is the practical meaning of replying in the guest's language: the warmth has to arrive in a language the guest can feel it in.

The read-through is the part teams skip. Once a month, pull 20 threads at random and read them aloud. You will hear the stiff ones and the loud ones within a sentence.

What changes when an AI drafts the first reply?

Nothing about the standard, one thing about disclosure. The same rules apply: short, warm, one ask, a time, a name. If a guest asks whether they are talking to a person, say so plainly, and better still, say it first: "This is our automated concierge; a person is one message away." Zendesk's 2025 research found 64% of consumers were more likely to trust AI agents that show friendliness and empathy ^[4], which is a long way of saying guests want the same thing from a machine that they want from the desk.

The line is emotional weight. Pool hours can be answered by anything that knows the pool hours. A message with a feeling in it, "we have been waiting an hour," belongs to a named person immediately, and the automation's only job is to notice and hand it over.

The one page standard, to copy

1. Tone: warm, plain, brief. One ask per message. Property name first time, staff first name after.
2. Timing: guest's local 8 a.m. to 9 p.m. Nothing non-urgent outside it.
3. Speed: acknowledge in minutes, give a time, hit it, and always send the last word.
4. Names and emoji: name once, emoji rarely and never in bad news, one exclamation point at most.
5. Never by text: bad news alone, disputed charges, arguments, personal numbers, anything unverified, marketing without opt-in.
6. Consent: capture the number for the stay and say what you will send; marketing gets its own opt-in.
7. Consistency: editable templates, one inbox with history, 20 threads read aloud monthly.
8. Automation: same standard, disclosed, with anything emotional handed to a person.

Print it, tape it by the desk, and read the first five threads of the week against it. The property that sounds like one calm person is not the one with the best writers. It is the one that wrote the standard down.