Webchat or a WhatsApp button? Put both on the site, and one inbox behind them

Hotels ask us which one to put on their website, webchat or a WhatsApp button. The answer is both, feeding one inbox, and the reasoning is not a dodge. The two channels are good at different halves of the same job, and the half each one is bad at is the half the other one covers.

What webchat does better

The guest stays on your site. No app switch, no lost visitor. The chat sits next to your booking engine, at the moment the guest is deciding, which is the only moment on a room page that changes anything.

Rich answers. Room cards with photos, the price, and a direct "book this room" link. A guest who can see two options side by side and tap one is a guest who books. That is hard to reproduce inside a messaging app.

Context. A visitor arriving from a campaign page can start the conversation with that offer already loaded, so they never have to explain which deal they mean.

Your look. Results can be shown in the style of the rest of your site rather than as generic grey bubbles.

No phone number needed. That suits people who are browsing and not ready to identify themselves. Ask for a number too early and a proportion of them simply leave.

What WhatsApp does better

The conversation continues after the guest leaves your site. They close the tab, think about it for three days, and come back in the same thread with all the context intact. Webchat cannot do that, because the tab is gone.

You can follow up, within rules. When a guest messages your business, a 24-hour customer service window opens. Meta's documentation puts it plainly: when a WhatsApp user messages you or calls you, a 24-hour timer starts, and once the window closes you can only send pre-approved template messages (Meta, *Send messages*, read 28 September 2026). Templates must be submitted to Meta and approved before they can be sent, and they are the only kind of message that can reach a user outside a customer service window (Meta, *Templates*, read 28 September 2026).

In practice an enquiry from Tuesday is still reachable on Friday, as long as you planned for it and had the template approved in advance.

It is where guests already are, particularly in Israel, much of Europe and Latin America. No install, no account, no password reset.

The same thread lasts the whole stay. Pre-arrival questions, in-stay requests and the post-checkout invoice all sit in one conversation that both sides can scroll back through.

The trade-offs, honestly

Webchat visitors are often anonymous and gone. If they leave no name or email, the conversation ends when the tab closes and you have no way to reopen it.

WhatsApp costs money and needs planning. Meta charges per delivered message for marketing templates, and for utility and authentication templates sent outside an open customer service window (Meta, *WhatsApp Business Platform pricing*, read 1 October 2026). Rates vary by template category and by the guest's country code, so check your own markets rather than an average.

Since 1 October 2026 the ordinary replies are charged too. Meta now charges per message for service messages, the free-form replies sent inside the 24-hour window, which had been free since November 2024. Each business phone number gets 1,000 delivered service messages free per month, resetting with no roll-over, and charging starts after that. Without a payment method on file, Meta delivers inside the free tier and then stops (Meta, pricing, read 1 October 2026). If your replies went quiet in the first week of October, that is the first thing to check. The full pricing picture for hotels works through the sums, and the WhatsApp pricing calculator does the arithmetic by guest country.

WhatsApp also asks for a phone number, which some browsers will not give you, and it does not render a booking-engine-style room card as well as your own site does.

What we recommend

1. Put webchat on booking and room pages, where visitors are comparing options and are one tap from paying. If it is only on the homepage, it is missing almost every decision.

2. Put a WhatsApp button on contact pages, in confirmation emails, and in your phone menu. These are the moments when the guest has already chosen you and wants a durable line to you, not a sales conversation. The phone menu is the most underused of the three: "press 2 to message us on WhatsApp" moves a real share of calls off the queue at reception, and there is more to that connection than one menu option.

3. Send both into one inbox with the same knowledge. This is the part that actually matters. If webchat and WhatsApp have separate knowledge and separate queues, a guest who asks the same question in both places gets two different answers, and your team maintains everything twice.

4. Add guided buttons such as "family trips", "spa" and "groups", so first-time visitors know what they are allowed to ask. Most people do not open a hotel chat with a fully formed question. They open it to see whether it is worth asking.

What to do on Monday

Check which pages your webchat is on. If it is only on the homepage, move it to the room and booking pages. Then add the WhatsApp link to your confirmation email, and decide which two or three follow-ups you would ever want to send outside the 24-hour window. Those are the templates worth getting approved before you need them.

Before any of that, settle which number the WhatsApp button points at: the app on the front-desk phone or the official platform is not a detail, and it decides what the button can do.

Takeaway

Webchat wins the visit. WhatsApp keeps the relationship. You need both, and you need them answering out of the same brain. For the wider picture of what a messaging setup should cover across the stay, see what a hotel guest messaging platform should actually do.