Check your own phone: when did you last answer an email from a hotel? Now check when you last answered a WhatsApp message. Guests are the same. In most surf destinations, WhatsApp is not a channel, it is the channel, and email is where confirmations go to be unread.
Yet almost all hospitality software is built around email journeys, because email is easy to automate and WhatsApp is not. Here is the setup that works for small houses without a Business API contract, without bulk-sender risks and without spamming anyone.
The principle: the system drafts, a person sends
Fully automated WhatsApp needs the Business API: approval, templates, per-message fees, and a sender that feels like a robot because it is one. The pragmatic alternative for a small house is a message queue: the system watches the bookings and suggests what should go out today, prewritten and in the guest's language. A person taps send. That keeps the personal number, the personal tone and a human glance between the data and the guest.
The glance matters more than it sounds. The system does not know that the guest already paid cash an hour ago, or that their flight was cancelled. The person at the desk does. Suggestion plus human beats automation at this scale.
The five messages that carry the whole relationship
- The welcome, a few days before arrival: how to find the house, when check-in opens, the one thing guests always ask. This message alone removes half of all pre-arrival questions, especially when it carries the link to the guest area.
- The deposit reminder, when a deposit is due and unpaid. Friendly, factual, with the amount and the date. Money conversations are easier in writing.
- The extras offer, once, in the week before arrival: airport pickup, a board, a lesson. Once is the important word.
- The departure note, the evening before checkout: checkout time, open balance if any, how the morning works.
- The review request, a day after departure, exactly once, only to guests who left happy. A second ask annoys; a third burns goodwill. The system should enforce the "exactly once" so nobody has to remember it.
Rules keep it polite
The difference between helpful and spammy is not the content, it is the bookkeeping. Every send gets logged on the booking, so nobody double-sends. Every message type has a switch and a lead time per house, so the queue fits how you work. And individual guests can be muted, because the long-stay regular does not need a welcome message every month.
Group messages, the honest way
Sometimes the whole house needs to know: the barbecue moved to Friday, the swell arrives Tuesday. Without the Business API there is no mass sending, and that is fine. A broadcast that works as a prepared list, one guest, one tap, next guest, takes three minutes for a full house and arrives as a personal message instead of a broadcast label.
What to keep out of WhatsApp
Invoices and legal documents belong in the guest area, linked, not pasted into chat. Long policies belong on a page. WhatsApp is for the short, timely and personal. The moment a message needs a scroll bar, it wants to be a link.
The result, in numbers a small house feels: fewer unanswered questions, deposits that arrive before the guest does, and a steady trickle of reviews from the guests who loved the stay and just needed to be asked, once.