Hotel Guest Communication With a Human Approving Every Send

Most hotels I talk to in Belize have the same problem with hotel guest communication. The messages that matter get sent when someone remembers, by whoever is at the desk, in whatever words they reach for that day. Arrival directions go out for some bookings and not others. Review requests go out for the guests who were friendliest, which is not the same as all of them.

The fix is not a robot that talks to your guests. The fix is a system that drafts the right message at the right moment and then waits for a person to read it and press send.

That is how I built the guest journey module in Direct Belize, my hotel website and direct-booking platform. Nothing leaves the building until a human has seen it.

What does automated guest messaging actually do?

The module schedules messages at set points in the stay. Each one is built from a template, which is a reusable message with blanks in it, filled in from the booking's own details: guest name, room, dates, number of people.

The points are the ones you would write down yourself if you sat and mapped a stay:

1. Booking confirmed. A confirmation that reads like it came from your property, not from a booking channel.
2. A few days before arrival. Directions, what to bring, what time the gate is open, anything the guest should know before they are in a taxi.
3. Arrival day. A short welcome and the practical details for the day itself.
4. During the stay. A check-in that opens the door to a request before it becomes a complaint.
5. After check-out. A thank-you, and a drafted review request.

Each of those is drafted ahead of time and held in a queue. Someone on your team opens the queue, reads what is there, edits anything that needs editing, and sends. If a message does not suit that guest, it does not go.

Why hold every message for approval?

Because automated messages fail in ways that are hard to predict and embarrassing in public.

A guest cancels and the "see you tomorrow" message goes anyway. A family books a room and the template greets one person. A guest complained at breakfast and an hour later a cheerful "how is everything?" lands on their phone. None of those are template bugs. They are situations a person on site knows about and software does not.

Approval gating is the cheap fix. The system does the remembering and the drafting, which is the tedious part. The person does the judging, which takes seconds when the draft is already written.

There is a second reason, which is tone. Small hotels in Belize compete on feeling like a place rather than a chain. A message that sounds like it was generated is worse than no message. When a human reads every draft before it goes, the voice stays yours, and over time the templates get edited into something that sounds like you by default.

The stay portal

Alongside the messages, each guest gets a link to a stay portal, which is a simple web page for their booking and nothing else. Dates, room, what they paid, what they still owe, the practical details of getting there.

This matters more than it sounds. Guests lose emails. They forward one to a travelling companion and the companion has questions. A link that still works and still shows the current state of the booking cuts out a surprising amount of back and forth at the front desk.

The portal is also where upsells live, if you want them.

Can the system sell extras without being pushy?

It can offer them. Early check-in, a tour, whatever you actually have capacity to deliver. The offer sits in the pre-arrival message and in the portal, and the guest either takes it or ignores it.

I would rather describe this honestly than promise a revenue lift I cannot evidence. What I can say is that an offer made a few days before arrival, while the guest is still planning, gets considered. The same offer made at the desk on arrival day, while they are tired and holding bags, usually does not. The timing is the whole advantage.

And like everything else, the message carrying the offer is held for approval. If you are full, or the tour operator is not running that week, you do not send it.

How do review requests work?

After check-out, the system drafts a review request. Someone reads it and sends it.

The point is consistency. Hotels that ask every guest, politely, shortly after the stay, accumulate reviews. Hotels that ask when they remember accumulate fewer. There is no trick in it beyond actually doing it every time, which is exactly the kind of thing software is good at remembering and people are not.

Where the human step earns its keep is the guest whose stay went badly. That draft gets held, or rewritten, or replaced with a phone call.

Doing it by hand, doing it fully automated, doing it with approval

Here is the honest comparison.

By hand. Costs nothing to set up. Works well when occupancy is low and one person knows every booking. Falls apart in high season, which is precisely when the messages matter most. Nobody can tell you which guests were contacted and which were missed.

Fully automated. Nothing is forgotten. But you will eventually send something wrong to someone, in writing, and you will not know until they reply. The tone drifts towards generic because nobody is reading the output.

Scheduled and approval-gated. Nothing is forgotten, because the system schedules it. Nothing goes out unseen, because a person clears the queue. The cost is a few minutes a day of someone's attention, which is less than the time currently spent trying to remember who needs directions.

The third option is the one I build, and it is built into Direct Belize rather than bolted on, so the messages are drawn from the same bookings that come through your own site and through the channel manager that syncs availability with Booking.com, Airbnb and Expedia.

What you would need to have ready

The software is not the hard part. The content is. Before any of this works, you need:

• Your actual directions. Written down once, properly, including the landmark people miss.
• Your arrival and departure times, and what you are willing to flex on.
• A short list of extras you can genuinely deliver, with who delivers them.
• One person who owns the queue. Not a committee. One person who opens it each morning and clears it.
• A decision on tone. Formal, warm, brief. Pick one and let the templates follow it.

Most of that is a morning's work with a notepad. It is also the part that pays off whether or not you ever commission software, because it is the first time most properties write down what they already half-know.

Where to start

1. Map your own stay. Write the five moments where a guest should hear from you, and what you would say at each. Use your own words.
2. Count the gaps. For last month's bookings, mark which ones got pre-arrival directions and which got a review request. The gap is the thing you are buying a fix for.
3. Write one template properly. The pre-arrival one. It is the message that prevents the most phone calls.
4. Decide who approves. Name the person and the time of day they will do it.
5. Look at what already exists before commissioning anything custom, because a hosted platform that already does this may cost you less than a build.

If you want to talk through which of those routes fits your property, you can get in touch and I will tell you plainly whether I think a build is warranted or not.