For guests in Europe and Asia-Pacific, WhatsApp isn't a channel choice — it's where they already live, and a villa that answers there feels local in a way an OTA inbox never will. The decision is which tier to use: the personal app (fine for one property, fragile beyond it), the free WhatsApp Business app (profiles, quick replies, up to a handful of devices), or the WhatsApp Business Platform API (automation, AI, shared numbers — with Meta's 24-hour service window and approved template messages as the rules of the road). This guide explains the three tiers, translates Meta's rules into host language, and is honest about when WhatsApp is the wrong channel.
The pattern every EU/APAC operator knows: the booking arrives on Airbnb or Booking.com, and the guest's second or third message is some version of "do you have WhatsApp?" They're not being difficult — they're switching to the app where their boarding passes, family chats and taxi drivers already are. Meeting them there measurably speeds everything up. Ignoring it means your check-in instructions compete with OTA notification digests for attention.
Personal app, Business app, or Business Platform (API)?
WhatsApp is three different products wearing one logo, and picking the wrong tier is the most common setup mistake. The honest decision table:
Meta's rules in plain host language
The Business Platform comes with two rules that sound technical but map neatly onto hosting reality. First, the 24-hour service window: once a guest messages you, you can reply freely for 24 hours; after the window closes, you can only reach out using a pre-approved template message (which reopens the conversation). In practice, guests mid-stay message you constantly, so the window is almost always open when it matters. Second, templates and opt-in: messages you initiate — a check-in reminder three days out, a door code on arrival morning — should use approved templates, and the guest should have agreed to hear from you on WhatsApp (a line in your booking confirmation covers this). Meta polices spam hard, which is precisely why guests still open WhatsApp messages: the channel stays clean because the rules have teeth.
Wiring WhatsApp into actual operations
One number per villa or one number for the operation? The pattern that scales is a shared operation-level number — guests save one contact, staff share one inbox, nothing lives on anyone's personal phone — with per-villa overrides where a property has its own brand. That's the model Hostella runs: WhatsApp as a live two-way channel where the AI answers in the guest's language, turns requests into assigned staff tasks, and escalates anything sensitive — with the OTA threads flowing into the same unified inbox alongside it. The guest experiences one conversation; the operation sees one timeline.
When NOT to use WhatsApp
Honesty section. North American guests often don't have WhatsApp installed — for a largely US/Canadian guest mix, SMS/iMessage and the OTA thread remain primary, and pushing WhatsApp adds friction rather than removing it. Before the booking is confirmed, keep conversations on the OTA: platforms require pre-booking communication to stay on-platform, and moving it off can violate their terms — after confirmation, exchanging contact details for stay logistics is normal. And never make WhatsApp the only channel: some guests won't use it, so the booking platform thread has to remain a first-class fallback. A useful floor: every guest gets an answer on the channel they wrote on.
WhatsApp + Telegram + OTA threads, one inbox
Hostella runs WhatsApp as a live two-way AI channel — org-level number, per-villa overrides, guest requests becoming staff tasks — from €29/month.
See pricing