Sidequest

Telling a guest they’re talking to an AI

The instinct is to hide it. The instinct is wrong, and the reason has nothing to do with regulation.

Tables laid under trees at a beach restaurant before service.

The first question every hotelier asks about a voice agent is whether the guest will know. The second, usually about a second later, is whether they have to be told.

Our position is that they should be told, in the first few seconds, without being asked. Not because a regulator says so somewhere — the rules vary by jurisdiction and are changing — but because of what happens on the call when you don’t.

The failure mode is not being an AI. It is being caught being one.

Picture the call where it goes wrong. Ninety seconds in, the guest asks something slightly sideways. The agent handles it a little too smoothly, or not smoothly enough, and the guest realises. And now the entire call is retroactively about something else. Every polite thing that was said is re-heard as a trick. The guest is not annoyed that a machine answered; they are annoyed that they were allowed to think otherwise.

That is a bad guest experience regardless of how well the rest of the call went. And it attaches to the property’s brand, not to the technology vendor, because the guest was never told there was a vendor.

Disclosure removes that failure mode completely. There is nothing to discover, so there is nothing to feel foolish about.

Nobody minds a machine answering the phone. People mind having been fooled — and those are not the same objection, though they arrive in the same sentence.

Said early, it reads as confidence

There is a tonal detail that matters more than it should. Disclosure at the top of the call sounds like assurance. The same disclosure extracted halfway through sounds like an admission.

The words are nearly identical. The position in the call is what changes the meaning, and it is worth being deliberate about it — a single short sentence at the greeting, in the property’s own register, and then straight on to being useful. Not a disclaimer. Not a paragraph. A fact, mentioned, then dropped.

The escape hatch has to be real, and quiet

Related, and easy to get wrong in either direction.

If a guest asks for a person, they get a person. Every time, without a negotiation, and without three attempts to solve it first. That is not a courtesy; it is the thing that makes the whole arrangement acceptable.

But it should not be advertised in every sentence. A system that opens with “or say representative at any time” teaches every caller to say representative immediately, and it never earns its keep — and the property is back where it started, plus a machine nobody trusts.

Respected, not promoted. That distinction is most of the design.

What this looks like in practice

The property decides the manner — the greeting, the voice, how formal it is, how it handles a caller who is clearly upset. That is not a setting we grant; it is the part only a hotelier can answer. What we hold as a default, and would argue for in every case, is that the first few seconds are honest.

We have yet to hear a good argument against it that survives the question: what happens on the call where they find out?


The fastest way to understand this is to hear it.

(305) 555-0148

Call it. You'll be talking to the product.

Request a conversation