WhatsApp for hotels and guesthouses: fewer calls, better check-ins
Guests message the number they already have saved. Here is how a small hotel can answer well, keep the history, and stop losing requests in one person's phone.
Guests message the number they already have saved. Here is how a small hotel can answer well, keep the history, and stop losing requests in one person's phone. In this deep dive, we explore actionable strategies, real-world engineering blueprints, and future-proof patterns to elevate your digital operations.
A hotel front desk does not have a messaging problem. It has an ownership problem. The guest has one thread with your property, and that thread lives on whoever's handset happened to be at the desk when the message arrived. The guest thinks they are talking to the hotel. In reality they are talking to a person who goes off shift at 6pm.
I build BNex, a WhatsApp Business Platform product, and hospitality is the clearest case I have seen for keeping guest conversations in a place that belongs to the property rather than to an employee. Below is how I would set it up, including the parts that should never be automated.
What guests actually message about
Guest WhatsApp traffic clusters into three phases, and each phase has a different urgency.
Before arrival. Is my booking confirmed? Can I check in early? How do I get from the airport? Do you have parking? Can I add a cot? These are decision questions, and a slow answer costs money in cancellations.
During the stay. Extra towels, the air conditioning, late checkout, a table at the restaurant, a taxi at 7am. These are service requests with a real clock on them.
After checkout. The invoice, something left behind, a booking for next season, a review request. This is where repeat business is quietly won or lost.
On a property running everything through one phone, all three phases compete for the same attention, and the guest in front of you at reception always wins. That is human nature, and it is why messages sit unanswered until midnight.
What the platform allows, in plain terms
WhatsApp has a 24-hour customer service window. If a guest messaged you in the last 24 hours, you can reply with free-form text, exactly like a normal chat. Outside that window, such as a message to someone who booked three weeks ago, you need an approved template.
Templates come in categories, and the category decides how much the message costs. A booking confirmation, a check-in reminder or an invoice is a utility template because it follows something the guest already did. A seasonal offer is marketing and is priced higher. Getting that boundary right matters more in hospitality than almost anywhere else, because hotels send both kinds of message to the same list. The rules are Meta's and apply whatever tool you use; WhatsApp messaging limits explained covers the quotas that go with them.
The messages worth templating
Four templates carry most of the value:
- Booking confirmed. Dates, room, total, cancellation terms, and what happens next. This single message prevents more pre-arrival calls than any other.
- Check-in reminder, sent the day before or the morning of arrival. Add the address, the check-in window and the direct line to reception.
- A short in-stay info message with the useful facts: wifi, breakfast times, how to reach reception. One message, sent once, readable later.
- Post-stay invoice, with the review link kept separate so the invoice stays a utility message rather than turning into marketing.
Everything else, including arrival questions and special requests, belongs in free-form conversation. A guest asking about airport transfer at 9pm wants an answer from a person, not a template.
The front desk problem
Most small properties do not have a tooling gap. They have a phone that leaves the building.
When the only WhatsApp access sits on a personal handset, three things break. The history leaves when the staff member does. Nobody can see whether the 7am taxi request was answered. And when two people reply from two devices, the guest receives two inconsistent answers.
The fix is not more people. It is a shared inbox, so every conversation sits on the property's number with visible ownership. If you are evaluating one, the 7 questions that separate shared inbox tools is the checklist I would apply to my own product first, and our shared inbox guide explains how assignment and history are meant to work.
Clinics solved the same problem earlier with reminders; WhatsApp appointment reminders for clinics shows the mechanics that transfer directly to a check-in reminder.
Where teams get it wrong
- Automating the welcome. A bot that recites policy to a guest who has been travelling for nine hours is worse than no message at all. Automate confirmations and reminders, keep conversation human.
- Blasting past guests with offers. Marketing templates to everyone in the booking history lift unsubscribes and blocks, and blocks affect how much the number can send. Send offers only to guests who opted in.
- Letting the marketing and utility lanes blur. Adding a discount line to a booking confirmation reclassifies it and bills it at the wrong rate. Keep the offer in its own message.
- Running it on a personal number. Your number is the property's asset. If it sits on someone's handset, the property does not own its guest relationship.
Where BNex fits
BNex is the WhatsApp Business Platform product I build, with a shared inbox, contact history and template flows. For a hotel the useful part is unglamorous: the guest thread belongs to the property number, whoever is on shift can see what has already been answered, and the 24-hour window is visible per contact so an in-conversation reply stays free-form instead of being sent as a paid template.
Hospitality is a fit for us because properties already live in WhatsApp. Guests send photos, ask in their own words, and expect a reply in the same app they booked through. Moving that traffic into a ticketing system nobody opens would be a downgrade.
If you run a hotel or guesthouse and guests are messaging a phone that walks home at night, message me on WhatsApp at +91 73587 22745 with roughly how many guest messages you get a day, and I will tell you honestly whether a shared inbox is the answer or whether the problem is simply that the front desk needs a rota.
Related Reading
Get more insights like this
Join our list for practical automation, web engineering, and growth strategy — written by builders, for builders.
Manikandan S
Founder & Technical Lead at ZiyncFounder and technical lead at Ziync. I build high-performance websites and web applications for startups and mid-market teams: React, Next.js, Firebase. Based in Chennai, working with clients worldwide.