WhatsApp vs Email vs SMS for Hotels: Channel Comparison

Most hotels in 2026 still run three guest messaging channels in parallel. Email for the booking confirmation and the newsletter. SMS for the panic-button reminders that nothing else can be trusted to deliver. WhatsApp for everything that actually feels like a conversation. None of these is going away, and pretending one of them is a silver bullet usually ends with an ops team patching the gaps manually.

What guests expect has shifted faster than what most PMS vendors expect. A 32-year-old booking a city break wants to ask one quick question about late check-in and get a reply in minutes, on the channel she already uses with friends. A 65-year-old booking a long stay still scans her inbox twice a day and prefers the formal tone of an email. A walk-in who handed you a mobile number with a typo in it will only ever hear from you again if SMS happens to land.

This post is a head-to-head, not a WhatsApp pitch. We organise messaging for hotels for a living, and we genuinely think SMS and email still earn their seats, for specific jobs. Here's the honest comparison, with the cost ranges, the open-rate ranges, and the workloads each channel handles best.

Open rates and response times

Numbers vary by region, segment, and how clean your list is, so treat any single figure with suspicion. The pattern, though, holds across most European hotel data we see:

• WhatsApp: roughly 90-98% open rate, with the bulk of opens happening inside 60 minutes. Reply rates on conversational messages sit between 35% and 60% for well-timed pre-arrival messages.
• SMS: roughly 85-95% open rate, with most opens inside 90 minutes. Reply rates are much lower (often under 5%) because guests treat SMS as one-way.
• Email: 18-30% open rate spread across 24+ hours. Reply rates on transactional email are tiny, under 2% in most data sets.

The gap between WhatsApp and email isn't really about open rates. It's about where guests answer. Email's not dead; it's just not where guests answer. Send a short question on email and you'll wait. Send the same question on WhatsApp and you'll have an answer before the kettle boils.

Regional variation matters. WhatsApp open rates in Germany, Spain, Italy, and the Netherlands are consistently strong. In pockets of the Nordics, SMS still rivals it because Telegram and iMessage have eaten into WhatsApp share. North American guests skew towards SMS or iMessage. If you sell heavily into the US, don't assume WhatsApp will carry the conversation.

Cost per message

This is where channel choice gets uncomfortable, because the cheapest channel is rarely the most effective.

• WhatsApp Business API: roughly €0.005 to €0.04 per 24-hour conversation depending on category (utility, marketing, authentication, service) and country. Service messages inside the 24-hour window from a guest reply are free in most regions. Spain, Italy, and Germany have specific rate cards worth checking.
• SMS in the EU: roughly €0.04 to €0.10 per outbound message, often more for premium routes. A two-way conversation across 5 messages can run you 25 cents before anyone has booked anything.
• Email: near zero per message at any sensible volume. The cost lives in the platform: ESP licences, deliverability tooling, list hygiene, design work. Easily €200-1500/month for a mid-size group.

Worth running the numbers properly before you cut a channel. We put a full breakdown in our pillar on WhatsApp costs for hotels. The short version: WhatsApp usually wins on cost per resolved conversation, but loses on cost per blast. Email wins on cost per blast and loses on speed. SMS loses on cost almost everywhere, except where reach is non-negotiable.

Rich content support

What you can put inside a message changes which jobs the channel can do.

• WhatsApp: images, PDFs (think check-in forms, restaurant menus, invoice receipts), location pins, quick-reply buttons, list selectors, voice notes. Approved templates for outbound, free-form replies inside the 24-hour window.
• SMS: 160 characters of plain text. Concatenated to about 480 if you accept the higher cost. No formatting, no buttons, no attachments. MMS exists but is unreliable across EU carriers.
• Email: the richest of the three. Full HTML, large attachments, hero images, trackable links, calendar invites. Also the most likely to land in promotions or get filtered by Apple Mail Privacy Protection.

This shapes what a channel can do. You can't run a smooth pre-arrival flow on SMS; there's no room. You can't send a one-tap restaurant booking on email; the link round-trip kills it. WhatsApp sits in the middle and that's why it eats so much of the in-stay workload. If you want a deeper look at the message types we run, our WhatsApp templates post walks through them.

Conversational vs transactional fit

The cleanest mental split: is this a message that wants a reply, or a message that just needs to land?

Conversational messages (pre-arrival questions, in-stay requests, problem-solving) belong on WhatsApp. The interaction loop is fast, the medium is informal, and guests tolerate a 5-minute back-and-forth they would never tolerate over email. Transactional messages (confirmations, invoices, receipts, terms) belong on email. Guests expect a record, want to forward it to their boss or partner, and need to find it again two months later. Urgent one-way messages — your room is ready, your taxi has arrived, the front door code is 4271 — belong on SMS, because nothing else delivers reliably to a phone with weak data signal.

Hotels that try to flip this (pre-arrival via email, confirmations via WhatsApp) usually find the response data tells them to stop within a quarter.

Compliance and consent profile

Channel choice in Europe is also a consent question, and the rules differ in ways that catch teams out.

• WhatsApp: Meta's policy plus GDPR. You need a lawful basis to message a guest, and Meta enforces a 24-hour service window. Outside that window you can only send approved templates in specific categories (utility, authentication, marketing). Marketing templates need explicit opt-in. Quality rating drops fast if guests block you.
• SMS: the strictest in most EU countries. PECR in the UK and the equivalents in Germany, France, and the Netherlands require explicit prior consent for marketing SMS. Transactional SMS (the booking is confirmed, your code is 4271) is generally fine under legitimate interest, but the line between transactional and marketing is enforced narrowly.
• Email: GDPR plus PECR. Soft opt-in is allowed for past guests on similar products, which is why hotel newsletters still work legally where SMS marketing usually wouldn't.

And here's the part most teams forget: opt-in for one channel doesn't transfer to another. A guest who handed you a mobile number at check-in didn't agree to a WhatsApp marketing template six months later. The booking engine consent text needs to cover each channel separately, or your CRM has to track them separately. We wrote about this in our guide to CRM solutions for hotels.

Channel use case mapping

The honest version, by job:

This isn't gospel. Your guest mix may push pre-arrival to SMS or invoices to WhatsApp. But this is roughly where the data lands for European city and resort hotels we work with.

When to drop a channel

Three honest cases where dropping a channel makes sense.

When SMS isn't worth the cost

If your average guest journey produces 6-10 SMS sends at €0.06 each, you're spending €0.36-0.60 per stay on SMS alone. For a 4-star city hotel with 30,000 stays a year, that's €10-18k a year. If 90% of those guests already engage on WhatsApp and the other 10% can be caught with email, the SMS line item is mostly insurance against edge cases. We've seen hotels keep only the urgent in-stay SMS (room ready, door code) and drop everything else without a measurable drop in guest satisfaction.

When email is dead weight

Email rarely deserves to be dropped, but pre-arrival email flows often do. If your pre-arrival email open rate is under 20% and you're already running the same content on WhatsApp with an 85%+ open rate, the email is duplicating effort and giving you a worse signal. Keep the booking confirmation, kill the "3 days before arrival" email, and watch the team's workload drop.

When WhatsApp doesn't reach your demographic

If you sell heavily into US groups, business travellers in markets where WhatsApp share is low, or older demographics who don't run a smartphone, WhatsApp won't be the right primary channel. Run a 90-day test: send pre-arrival messages on both WhatsApp and email and measure reply rates per segment. If WhatsApp reply rate is under 15%, you have the wrong segment for it.

How a hotel actually runs all three — orchestration patterns

The hotels that get this right don't pick one channel. They orchestrate. The pattern that works for most of our customers:

1. Email for the immutable transactional record (confirmation, invoice, post-stay).
2. WhatsApp as the primary conversational channel for everything between booking and check-out, with a fallback rule: if no WhatsApp reach within 24 hours, fall back to email.
3. SMS reserved for two or three high-stakes one-way moments: door code, room ready, late-arrival critical info.
4. One inbox, not three. The front office should see WhatsApp threads, email replies, and inbound SMS in the same place, threaded by guest reservation.

That last point is where most setups fall apart. Three channels living in three apps, none of them tied to the PMS reservation, is how guests get answered three times by three people. The fix is a layer above the channels: a CRM or an AI operator that owns the conversation thread, keeps state, and routes outbound by channel rules. We did the ROI maths on this and it's usually the operational efficiency, not the marketing uplift, that pays for the platform.

And one rhetorical question worth sitting with: if a guest sends you a WhatsApp message at 22:30 about a missing toothbrush, where does that conversation live tomorrow morning when housekeeping needs to know? If the answer is "in the night auditor's phone", your channel mix is fine but your orchestration isn't.

Conclusion

WhatsApp wins on engagement and cost-per-resolved-conversation for the bulk of guest messaging in Europe. SMS still earns its keep for time-critical one-way messages and segments where WhatsApp reach is weak. Email is the only place transactional records and newsletters belong. None of them is the answer on its own.

If you want to run the three together without bolting on yet another inbox, this is what Viqal's AI Operator does: it sits over your channels, keeps the conversation threaded against the reservation, and decides outbound channel by rule rather than by whoever happens to log in first. For the deeper cost picture, the WhatsApp costs pillar is the next stop.