Guest messaging for hotels: before, during and after a stay

Updated 2026-09-24 · 4 min read · By the Convo360 team

Three stages, three different problems

Hotel messaging looks like one queue and behaves like three.

Before arrival, guests ask about check-in time, early check-in, airport transfers, parking, whether breakfast is included and how to find the place. These repeat almost word for word and are entirely automatable.

During the stay, they ask for towels, report that the air conditioning is not working, request a late checkout or a restaurant booking. These are urgent in a way few support messages are: a request for towels at 10 pm is worthless at 8 am.

After checkout, they ask about a bill line, a forgotten item or a refund. These are slower but they decide the review.

Treating all three with one process means the urgent ones wait behind the routine ones, which is the single most common failure in hotel guest messaging.

Occupancy makes it worse in the obvious way. The night your property is full is the night the most requests arrive and the fewest people are free, and that is also the night with the most first-time guests forming an opinion.

Pre-arrival, fully automated

Put the property's details into a knowledge base and the bot answers these at any hour, which matters because guests plan at night and often from another time zone.

• Check-in and checkout times, and the cost of early or late.
• Directions, the nearest station, and what a taxi should cost.
• Parking, and whether it needs booking.
• What is included: breakfast, wifi, pool access.
• Policies: pets, extra beds, children, identification required.

Send a pre-arrival message two days before with the essentials and a line inviting questions. It removes most of the inbound volume and it is the moment to ask about an early check-in, which is easier to arrange with notice than on the morning.

In-stay requests need routing, not forwarding

The common setup is that everything reaches the front desk, who relay it verbally. That works at low occupancy and collapses at high.

Route by request type instead. Housekeeping requests to housekeeping, maintenance to maintenance, dining to the restaurant, with the front desk seeing everything but owning only what is theirs.

With the Support Desk in Convo360, each becomes a ticket with an owner and a deadline measured in minutes rather than hours. A towel request with a fifteen-minute target and an escalation to the duty manager behaves completely differently from the same request relayed verbally during a busy check-in.

Guests notice this more than anything else on this list, because the gap between a hotel that responds in ten minutes and one that responds in an hour is the whole experience.

Give housekeeping and maintenance a way to close their own tickets from a phone. If closing requires walking to a desktop at reception, requests will be done and not recorded, and the reports will show a problem that does not exist.

The problem worth catching before checkout

Almost every bad hotel review describes something the hotel could have fixed if it had known.

A short message on the second evening asking whether everything is comfortable costs nothing and catches an astonishing amount. A guest who mentions a noisy air conditioner in a private message is a guest you can move; the same guest writes about it publicly a week later.

Make the reply route to somebody who can act tonight. The value is entirely in the speed: a problem acknowledged and fixed during the stay usually improves the review rather than damaging it, because the guest now has a story about service.

After checkout

Forgotten items deserve special attention. They are emotionally charged, they have a short window before housekeeping processes the room, and handling one well produces disproportionate goodwill.

Ask for the public review only after a private acknowledgement, and only from guests whose stay went well. Asking everybody is how a hotel collects the reviews it least wants.

Handle the bill query quickly even when you are certain you are right. Guests query charges from an airport or a train, with limited patience, and a slow answer becomes a card dispute that costs far more than the line item.

Languages and international guests

Hotels serve a more linguistically varied audience than almost any other business, and this is where an AI agent earns its cost.

The bot replies in whatever language the guest writes, which for an Indian property might be English, Hindi, Marathi, French or Japanese within the same week. A front desk cannot cover that, and a translated static FAQ cannot answer a specific question.

Keep the knowledge base in one language and let the model translate. Maintaining several versions is how a property ends up with the wrong checkout time published in two languages.

Be careful with anything contractual, such as cancellation terms. Those should be answered with the exact wording from your policy, and the prompt should say so explicitly rather than allowing a paraphrase.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.