Business guests are not leisure guests

Business guests and leisure guests need different messages: the same hotel, the same room, two different journeys.

A couple arriving on Friday for two nights wants the spa hours, a late checkout and a restaurant recommendation. A consultant arriving Tuesday at midnight for one night wants the WiFi password, the invoice details and to be left alone. You can send both of them the same six messages, and you will be wrong for one of them every time.

Most properties discover this the same way: by sending something slightly absurd to a guest who then mentions it at the desk. The messages were well written. They went to the wrong person.

Where automations go wrong

• The "how is everything?" message two hours after check-in. It reaches a business guest who arrives at midnight and was checked in by hand at 18:00 because the company booked early and the desk wanted the room off the arrivals list. The guest gets a cheerful welcome question at 20:00 while still in a meeting, and a second one at 02:00 if your quiet hours are set by the wrong clock.
• The pre-arrival message offers a birthday kit to someone on a company booking. Flowers, a bottle, a romantic turndown. All lovely. All being paid for by an employer who will see the line on the invoice.
• The checkout reminder fires on a corporate stay that changed length twice. Extended stays are normal in business travel. A reminder to pack on the morning of what is now day three of five reads as an error, and it makes the guest doubt everything else you send.
• The satisfaction survey lands during the conference. A guest attending an event in your own hall is in a session all day. The survey arrives, is ignored, and your response rate drops for reasons that have nothing to do with the stay.
• The upsell for a second night at the weekend rate. Sent to someone whose travel policy does not allow it.

None of these are catastrophes on their own. Together they teach a guest that your messages are not worth reading, which is expensive, because the messages that matter are in the same channel. Timing is half of why an offer lands or grates, which is the argument behind micro-upsells and the psychology of perfect timing.

Filter by booking source

Your property system already knows the source of every reservation: direct, OTA, corporate account, travel agent, event block. This field exists, it is reliable, and almost nobody uses it to shape the guest journey.

Start with three lanes.

Corporate and agent bookings get a shorter journey. Arrival details, how to get in late, WiFi, parking, and who to contact about the invoice. That is close to everything a business traveller wants from you before arrival. Cut the upsells, cut the romance, cut the "plan your trip" content.

Leisure bookings get the full journey. Upsells, spa and restaurant, the satisfaction check, the post-stay follow up. This is where your revenue extras live, and this is the audience that wants them.

Agent bookings that were paid by the agent skip the payment step in online check-in. Asking a guest for a card when the agent has already settled the room is a guaranteed support ticket, and it is one of the most common reasons an otherwise healthy online check-in stalls. It is the same failure described in the payment field that quietly kills your digital check-in.

Then add the rules that fall out of your own operation. Event block guests get the event information and nothing else. Long stays get a different mid-stay message. Rooms booked by a company but occupied by a family on a bleisure weekend are the awkward middle, and the honest answer is to treat them as corporate until the guest tells you otherwise.

One warning. Booking source tells you who paid, not always who is sleeping in the room. A corporate rate booked for a colleague's parents exists. Keep the corporate journey polite and useful rather than assuming a suit, and you will never look foolish in either direction.

Time by arrival, not by status

The second half of the problem is timing, and it is where most journeys actually break.

Automations usually trigger on a status change. Checked in, so send the welcome. That works when the status changes at the moment the guest walks in. It does not work in a property where the desk checks guests in early to clear the arrivals list, or marks a room occupied when housekeeping releases it, or processes a late arrival the next morning.

If your staff change statuses by hand, trigger on expected arrival time with a delay, not on the status alone. For a guest whose expected arrival is 23:30, a welcome message at 02:00 helps nobody. Hold it until a civilised hour the next morning, or skip it entirely for a one night business stay and send the checkout information instead.

Three practical rules:

1. Set a quiet window and honour it for every message that is not urgent. Late arrivals get their welcome in the morning.
2. For stays of one night, collapse the journey. Pre-arrival, then checkout. Nothing in the middle.
3. Recalculate on change. If a stay is extended, the checkout message moves. If it is not recalculated automatically, it will fire on the wrong day, and the guest will remember that more clearly than any of the messages that were right.

Getting these two filters in place, source and time, fixes more guest complaints about messaging than any amount of rewriting the copy. The copy is usually fine. The targeting is not. It is worth doing before you refine the messages themselves, because the same message is either helpful or intrusive depending on who receives it and when. The same logic applies to asking for marketing consent: a corporate guest checking out at 06:00 for a flight is not the moment.

Takeaway

One journey for everyone means the wrong message to someone. Split by booking source before you split by anything else.