Loading…
Loading…Loading…
Loading…Hotel enquiries get lost on WhatsApp when they land on personal phones with no shared record. A verified business account and a logged inbox fix that.

Founder & CEO, Airful
A guest finishes reading about your property at eleven at night and sends a WhatsApp message. She wants to know if the garden suite is free for the second weekend of March. The message lands on the phone of whoever the number was shared with last season. That person is asleep or off shift.
By morning she has asked two other properties the same question. One of them answered within the hour. Your reply goes out at ten, written from memory, and it misses the dates she mentioned in a voice note. No report will ever show this enquiry existed, because it never touched a system the business can see.
Hotel enquiries get lost on WhatsApp because they arrive on personal phones, outside shift hours, with no record that links the chat to a booking. When the person holding the phone is off or leaves, the conversation goes with them. The fix is an official business account connected to a shared, logged inbox. Each message then goes to the right person, and the record shows who answered.
Nobody loses an enquiry on purpose. It falls through small gaps that nobody owns, and we see the same few at almost every property we work with in Hospitality and Retreats.
Start with timing. Guests message when they plan, usually in the evening. Staff answer when they work. A midnight message waits until someone picks up a personal phone, and by then the guest has often moved on.
Then the shift change. The receptionist who started a conversation hands over to a colleague who cannot see it. The guest repeats herself, or waits. After the first reply, follow-ups happen from memory, so a guest who said "let me check with my partner" rarely hears back.
Even when a chat turns into a stay, nothing links the two. The booking engine shows a reservation. The WhatsApp thread sits on a phone. Ask the general manager which channel produced the booking and you get a shrug.
The worst gap is the leaver. When an employee goes, the number often goes too, along with every past guest who saved it. Repeat guests keep messaging someone who no longer works for you.
Most properties start on a personal WhatsApp account or the WhatsApp Business app on a single handset. Both tie the channel to a device, and usually to one person. The official route is the WhatsApp Business Platform, which Meta offers for businesses that need a channel the whole team can work from.
On the platform, the account belongs to the business. Meta's platform overview describes a WhatsApp account that holds your phone numbers and display name, attached to your business portfolio. The number is registered to the business, and the business itself is verified with its documents. Staff come and go, but the number stays with you, and so does the history once it lives in a shared inbox.
Free-form replies are allowed inside a 24-hour customer service window that opens and resets each time the guest messages you. Outside that window you can only reach a guest with a template, and templates generally need approval before you can send them. So the rules reward fast answers and planned follow-ups. A hotel wants both anyway.
Once the number lives on the platform, it can feed a shared inbox. Each conversation has one history that anyone on shift can read. The night manager can see what the morning receptionist promised.
Each message carries a name, including replies sent by automation. You find out who quoted that rate the guest is now disputing. New staff can read how good answers were written.
Routing sends each enquiry to the person who should handle it. Wedding and group enquiries go to the events lead. Spa questions go to the spa. Rules decide, so it stops depending on who saw the message first.
Then there is the daily digest. Each morning the team sees what came in overnight and what is still waiting. Anything unanswered past an agreed window gets flagged before the guest gives up.
The channel your guests prefer should never depend on whose phone happens to be charged.
Automation is good at the repetitive work. A first response confirms the message arrived and says when a person will reply. The menu option a guest picks decides the routing. Approved templates handle booking confirmations and pre-arrival details, and staff get a nudge when a thread goes quiet.
It should never make the judgment call. Holding a room without a deposit, or answering a complaint, needs a person who has read the whole conversation and knows the property. We set automated replies within rules you approve, and a person can take over any conversation at any point.
Our test is short. If a wrong answer could cost a booking or a review, a person sends it. If the answer is the same every time, a template can.
A shared inbox on its own is one more screen to check. It starts paying off when the channel connects to the system the team already uses, whether that is a CRM, a property management system or an Operations Platform for Operators. A separate WhatsApp tool that talks to nothing repeats the problem described in The Real Cost of Tool Sprawl in Growing Companies.
Here is the order. A new conversation creates an enquiry record with the guest's number, the dates and the campaign or page that sent her. When the reservation is made in the booking engine, it is matched to the enquiry by phone number or booking reference.
Now every booking has a history. You can see who handled it and which campaign started it. You can also see the enquiries that never converted, and where they stalled. That may be the first real number you have ever had for WhatsApp.
The first change is quiet. Messages stop going missing. Nobody has to ask who spoke to the guest. Overnight enquiries get an immediate acknowledgement, then a real answer from the first person on shift.
The next one takes a few weeks. The digest shows what the team could only guess at before: the hours when most enquiries arrive, and the questions that come up daily and deserve a template.
Habit is the hard part. Staff who have answered from their own phones for years will keep doing it until the shared channel proves faster. So we run the new channel alongside the old one for a week before anyone switches over.
We have more than five WhatsApp integrations running for clients. Our WhatsApp Operations Layer engagement covers account setup and verification, integration into your platform or CRM, templates and routing, the shared inbox, the digest and training. It takes two to three weeks. Engagements in this shape typically run $5,000 to $7,500, then five hundred dollars a month for the channel. Meta bills template messages per message on its own terms, and we size that for your volume before you commit.
Most are lost because they arrive on a staff member's personal phone, outside shift hours, with no record linking the chat to a booking. When that person is off or leaves, the thread and its history go with them.
It is Meta's official way for a business to message customers through an account the business owns, on a phone number registered to that business. Because the account and number belong to the business, the inbox built on it keeps every conversation when staff change.
The repetitive parts can be automated, such as the first acknowledgement, routing to the right person, reminders and approved templates. Judgment calls like holding a room without a deposit or answering a complaint should stay with a person who can see the full conversation.
Connect the WhatsApp channel to the system the team already uses, so each new conversation creates an enquiry record. When the reservation is made, it is matched to that record, which shows who handled the guest and which campaign started the enquiry.
We set up WhatsApp as a shared, logged channel connected to the system your team already uses. If your guests message first, we can start with the number they already know.
Book a Scoping Session
The average 50-person company uses 40+ SaaS tools. Most of them overlap, none of them talk to each other properly, and the integration tax is quietly eating your margins.

Every company has process debt. The workarounds, manual steps, and tribal knowledge that worked at 10 people but collapse at 50. Here's how to spot it before it becomes a crisis.

70% of CRM implementations miss their goals. Here are the failure patterns we see repeatedly, and a framework that actually works — based on the projects we've rescued and built.
Book a 30-minute audit call. We review your current stack and recommend the first module. No generic sales pitch, no 12-page proposal.