Answering an AI Agent: What Your Hotel's Messaging Must Handle

The message arrives on WhatsApp from a guest's number. It reads: Early check-in requested for the 14th, reservation under Weiss. Please confirm parking availability for a mid-size car and the current pet policy for one small dog. Notify if any spa slot opens between 17:00 and 19:00.

Polite. Complete. Four requests in one message. It was not written by the guest.

What the agent expects

Everything a human guest tolerates, an agent does not.

A complete answer to every part. Four requests, four answers. A reply that addresses the check-in and ignores the dog is, to the agent, a failed exchange.

Precision. Early check-in is possible is not an answer. Early check-in from 11:00, 30 fee, subject to availability on the day is. The agent will act on the specifics and pass them to the guest.

Consistency with your other sources. The agent has read your website, the OTA listing and the map profile. If your reply contradicts them, it notices, and it trusts neither.

Speed. The agent is running a task. A reply in seconds keeps the task moving. A reply tomorrow morning stalls it, and the agent may complete the task elsewhere.

No menus. An agent does not click. A reply that says press 1 for reservations ends the exchange.

Why the last generation fails completely

A decision-tree chatbot reads the message above, matches the word check-in, and shows a menu of check-in options. The agent cannot select from a menu. The exchange is over, and the agent records that this property could not answer.

Not a partial failure. Total.

A language-model assistant grounded in the property's facts reads the same message, parses all four requests, and replies with four answers - check-in policy, parking, pets, and a note that the spa request has been passed to the team who will confirm. Each from the knowledge base. Each consistent with the website, because it is the same source.

This is the sharpest dividing line between the two generations of hotel messaging. For human guests, a tree is merely frustrating. For an agent, it is invisible.

The escalation an agent needs

The assistant will not know everything. The spa slot request above needs a person to check a schedule and hold a booking.

The wrong reply is an improvised one - yes, slots are available - because the agent will act on it and the guest will arrive expecting a slot that does not exist. The right reply is precise about the handover: The spa request has been passed to our team, who will confirm availability by 15:00 today. Then an escalation carrying the full original request, verbatim, to whoever owns spa bookings, on a channel they watch.

Agents cope well with an honest handover and badly with a confident guess. Which is also true of human guests, only slower.

What your knowledge base has to contain

The agent asks the same questions guests ask, only more precisely and all at once. So the knowledge base has to hold specific, current answers to the practical questions - not descriptions, facts:

• Check-in and check-out times; early and late terms and fees
• Parking - location, size limits, cost, reservation
• Pets - where, cost, exceptions
• Cancellation and modification terms
• What is included, and what costs extra
• Accessibility specifics
• Transport and shuttle
• Hours for everything with hours

Each one a sentence an agent can act on. Each one identical to what the website says, because the agent has read the website.

How you will know

Often you will not, at first. The message arrives on the normal channel, in natural language, from the guest's own number. The signs are precision, multi-part requests, and follow-ups that quote the exact wording of your reply back to you.

It matters less than it seems. The response is the same whether the sender is a person or their assistant: answer every part precisely from current facts, and escalate honestly when you cannot. A property that does that for guests is already ready for agents.

What to do

Read your assistant's last fifty replies. Count how many were complete, specific, and consistent with the website. Then send it the message at the top of this article and see what comes back.

If the reply answers all four parts and hands over the fourth honestly, you are ready. If it shows a menu, you have found the problem before the agents did.