WhatsApp, SMS and email: which channel each hotel message deserves

A hotel sends confirmations, arrival instructions, offers and reminders, and almost always pushes them all through the same pipe. But channels are not interchangeable pipes: each one has a nature of its own, and each type of message has a channel it deserves. Choosing wrong breaks nothing right away; it simply guarantees that the right message lands in the place where nobody will read it.

Three channels, three natures

Email is an archive. Receipts, unopened newsletters and promotions for everything the guest ever bought all live there. It is an excellent channel for storing and a poor one for notifying: whatever arrives gets filed, postponed and, with luck, searched for later. An email is not read when it arrives; it is found when it is needed.

SMS was born as an interruption. It is short, it arrives with little identity and it does not invite a reply. Today it shares the screen with verification codes and system alerts, and that neighborhood defines how it gets read: the guest glances at it, extracts the fact and forgets it. It works for immediately useful notices; as a relationship channel it is a dead end, because the conversation back barely exists.

WhatsApp is a conversation. It is the inbox where family and friends write, where every message gets looked at, even in passing, and where replying is the natural gesture. When the hotel writes there, it inherits that full expectation: it is expected to sound like a person, to arrive at a good moment and to answer when the guest replies.

The confirmation: a document and a piece of news

A booking confirmation lives a double life. On one hand it is a document: reference number, dates, rate, cancellation policy. That document belongs in email, because the guest will look for it weeks later, perhaps from another device, and archiving is exactly what email does well. On the other hand it is news: the certainty that everything is in order. And news lives best where the guest actually looks.

The healthy practice is to use both, with different roles: email as the record, WhatsApp as the handshake. The short WhatsApp message, with the guest’s name and arrival date, does something the attached document cannot: it opens a conversation. The guest who receives the confirmation there already knows where to ask about parking, check-in time or the extra crib.

The operational message: where conversation decides

Operational messages are the ones that expire: check-in time, directions to the property, the notice that the room is ready. They all share two traits: they have an expiry date and they generate questions. Email fails on both fronts, because it gets read late and because replying to an operational email feels like opening a support ticket.

On WhatsApp the operational message arrives at the moment it is useful and carries the reply built in. The guest answers with whatever worries them first, and on the hotel’s side the AI receptionist handles that reply on the spot, at whatever hour it lands. The question that would have been lost in email becomes a better prepared arrival.

• The estimated arrival time, which organizes that day’s front desk operation.
• Access directions, which prevent the call from a lost guest ten minutes from the hotel.
• The room-ready notice, which turns a lobby wait into a smooth check-in.
• The late checkout offer, decided in the moment and through the same channel.

Marketing: permission rules

Marketing is the message the guest did not ask for, which is why it demands the most from the channel. In email, the culture of volume made it invisible: hotels send a lot because almost nobody sees it. In SMS it is a paid interruption that cannot hold a conversation. On WhatsApp it can be the best or the worst thing your hotel does, and one single thing makes the difference: real permission.

Real permission means the guest already wrote to the hotel’s WhatsApp at some point: they started the conversation, they know the number and they expect that channel to be useful. Guest Sender builds its audiences only from those guests, filtered by the hotel’s CRM tags, and even then treats every send with restraint. Safe Pace sends 44 messages a day, one every 15 minutes with random variation, only between 8 in the morning and 7 in the evening local time, under a prudent monthly quota.

Market context explains the rest. The pay-per-message API charges around 3 US cents for each marketing message in Mexico; a campaign to 10,000 guests runs about 300 dollars, every single time. Guest Sender does not use that route and does not charge per message, but it keeps the discipline that price imposes: thoughtful audiences, messages worth sending and an automatic opt-out that respects the guest who writes “stop”.

Every hotel message has a channel it deserves; sending it through the wrong one is not a saving, it is a silent way of going unread.Guest Sender operating principle

A practical rule for deciding

• If the guest might need it six months from now, it is a document: it goes to email.
• If it expires in hours or needs an answer, it is a conversation: it goes to WhatsApp.
• If it is a code or an automatic system alert, SMS still does the job.
• If it is marketing, it goes only to the channel where real permission exists, at a measured pace and with an easy way out.

The proof arrives on its own with the metrics. When a message travels through the channel it deserves, the campaign numbers, sent, delivered, read, replied and opt-outs, tell a coherent story: high reading, replies the front desk can sustain and few opt-outs. When the channel is wrong, the same table gives it away before any complaint does. Choosing the channel is not a logistics detail: it is the hotel’s first editorial decision.