The difference between a mention and a sale.

Checking what an AI says about you only tests the mention, never the gap after it

A countryside spa hotel gets recommended by an AI agent to someone planning a birthday weekend. The mention goes well: accurate, specific, genuinely well-matched. This is the same found-versus-bought gap this hub's own foundational piece describes, examined specifically in the narrow window right after a mention lands. What happens in the next sixty seconds decides whether that becomes a booking or nothing at all, and almost none of it is about how good the mention was.

The AI, or the person reading its recommendation, needs to know whether the actual dates are free. Then the actual price for those dates, which might differ from a generic rate quoted on a page. Then whether the room type mentioned is the one that's really available, not a similar one. Then a way to hold or confirm the booking, there and then, rather than being sent off to call the hotel during opening hours. Every one of those is a separate small check, and a single one failing is enough to lose the booking, however good the original mention was.

A hotel checking what an AI says about it sees the mention, reads it, and if it's accurate, moves on satisfied, with no way to know the gap even exists. That check only ever tests the mention itself, not what happens in the sixty seconds after it. The only way to find the gap is to try to push a real booking through the whole path, dates, price, room, confirmation, and see exactly where it breaks.

What tends to break, and why confirmation is hardest to fix

None of these four break in a strict, measurable order, and stating one here would claim a precision nobody actually has. What holds up under reasoning, rather than a claimed statistic, is that confirmation sits in a different category from the other three. Dates, price and room type are all lookups: the true answer already exists somewhere in the hotel's own systems, and the only question is whether an AI can reach it. Confirmation is not a lookup. It's an action, taking a card, holding a room, sending a receipt, and an action is harder to hand to something that isn't a person than a fact is. A hotel can publish a live rate feed and a live calendar without much difficulty. Letting a booking complete without anyone picking up a phone asks more of the system underneath it, which is exactly why it's worth checking first, not because it's been measured as the step that fails most often, but because it's structurally the hardest of the four to get right.

Why fixing this rarely means new work

None of the four checks, dates, price, room type, confirmation, are things a hotel doesn't already handle for a person calling the front desk. Staff already know today's real rate, already know which suite variant is free, already take a card and confirm a hold over the phone in under a minute. The gap isn't a missing capability. It's that none of it is reachable by anything other than a person on the other end of a phone call, at the specific hours someone's there to answer it, which an AI acting on someone's behalf at any hour simply can't work around.

Closing each of those gaps, one at a time, dates, price, room type, confirmation, connected to the booking system a hotel already runs rather than a new one, is what turns a good mention into a completed booking. Selfe's work here is unglamorous on purpose: making sure nothing breaks in the sixty seconds after a mention, not making the mention itself any better.

How do we find out where our own gap is?

Try to push a real booking through end to end, dates, price, room, confirmation, the way an AI would, and see exactly where it stops.

Isn't a phone number enough as a fallback?

It's a fallback for a person. An AI acting on someone's behalf generally can't make a phone call, so a phone-only confirmation step is effectively a dead end for that path.