Guest messages from the booking sites, answered on the booking itself

A guest books your cabaña through Airbnb, then writes two days before arrival to ask whether the shuttle from the Belize City airport can be arranged, and whether the room has a fan or air conditioning.

A second guest, booked through Booking.com, asks the same two questions.

A third, on Expedia, asks whether you can hold a late check-out.

Three questions, three different inboxes, and each one behind its own login. That is the part of the job nobody talks about. It is not difficult work. It is just scattered, and scattered work is the kind that gets dropped.

Where the messages used to live

Most small properties in Belize have worked out a system of sorts. Someone checks the Airbnb app on their phone in the morning. Someone else logs into the Booking.com extranet when the laptop is free. Expedia gets looked at when a booking comes through and then not again for a week.

The system holds until it does not. The owner is in San Ignacio collecting supplies. The phone with the Airbnb app on it is in her bag, on silent. The guest asking about the shuttle hears nothing until the evening.

Meanwhile the message history lives nowhere useful. If a guest agreed to a late check-out on Booking.com in March, the only record is inside Booking.com, and only the person who replied remembers it.

The expectation gap is real. Studies of travellers who message businesses online report that 82% expect an immediate reply — roughly within five minutes — and 40% expect one within the hour. That is not a standard a two-person guesthouse can meet across three extranets with one phone between them.

Messages on the booking, with an unread badge

The channel manager that keeps your calendar in sync with Booking.com, Expedia, Airbnb, Vrbo and Google also carries messages. When a guest writes through the site they booked on, that message is pulled into the Direct Belize admin and attached to the booking it belongs to.

So the reservation record shows the dates, the room, the rate, the channel, the deposit if there is one — and the conversation, in order, underneath.

A badge marks anything unread. Front desk opens the admin at the start of a shift and can see which bookings are waiting on a reply without opening anything else.

Staff answer from the booking page. The reply goes back out through the same site the guest used, so the guest sees it where they expect to see it, in the Airbnb thread or the Booking.com thread. They do not get an email from an address they do not recognise, and nothing lands in a spam folder.

The guest stays in the app they trust. You stay in one screen.

That is the whole of it, really. Not clever, just tidy.

You can read more about how the sync works on the channel manager and OTA sync page.

What this changes for a guesthouse, and for a twenty-room hotel

The two cases look different and the fix is the same.

The two-person guesthouse in Hopkins. One phone, two people, and whoever is nearest the laptop deals with whatever has come in. Messages from all three sites arrive in one place, so the morning check is one check. If one of you replies about the shuttle, the other can see it was answered and by whom. No duplicate replies, no silent gaps because each of you assumed the other had it.

The twenty-room hotel in Placencia or San Pedro. Three shifts, several staff, and the problem is not volume so much as handover. Night shift answers a question about early check-in. Morning shift arrives and has no idea unless it was written in a book. With the conversation sitting on the booking, the handover is the record. Anyone with permission to view that booking sees what was said.

Staff logins carry a View / Edit / Create / Delete matrix per area, with preset roles — administrator, front desk, marketing, read-only — so a housekeeping supervisor can see what they need and nothing more.

The same admin runs both. Direct Belize plans are sized by rooms — Starter for 1–6, Growth for 7–14, Pro for 15–25 — and the difference between a guesthouse and a hotel is how many logins are in use, not a different system. The pricing page sets out what each plan covers.

What cannot be sent

Worth knowing before you promise a guest something you cannot deliver in the thread.

The booking sites control their own messaging, and they protect it. In practice that means:

• Links are often stripped or blocked. Sending a guest a link to your tour menu or your directions page may simply not arrive. Some sites remove the URL; some block the message.
• Attachments are not reliable. A PDF map or a signed form is not something to count on sending through an OTA thread.
• Contact details may be filtered. Phone numbers and email addresses in a message before check-in are frequently removed, which is the sites' way of protecting the booking they brought you.

None of this is unreasonable. Those sites brought the guest and they earn their commission on that booking. The sensible approach is to answer the question in plain words inside the thread — "yes, the shuttle can be arranged, BZ$ rate confirmed at check-in, we'll meet you at arrivals" — and save the links, the maps and the upsell portal for after arrival, or for guests who came to you direct.

Once a guest is yours, the automatic journey messages by email or WhatsApp do the rest. WhatsApp messages are reported to be opened 92–96% of the time against 18–22% for email, which is why most properties use it for the arrival-day note.

The quieter benefit

Having every conversation on the booking means you stop hunting. A guest arrives in Corozal and says they were told the room had a kitchenette. Someone opens the booking, reads the thread, and knows within a few seconds what was actually promised and by whom.

That is not dramatic. It is just the difference between a conversation that ends well and one that does not.

Setup is typically done within a couple of weeks, and there is no long-term contract.