A guest finds your restaurant through ChatGPT. They describe what they want - cuisine type, location, occasion, time - and the AI recommends you. The booking is made without them ever visiting your website. You got the booking, but what do you actually know about that guest?
This is the question most operators haven’t got to yet. The conversation about AI in hospitality has focused on discovery - will guests find me through AI channels? The harder question is what you own when they do.
It has three parts. What data do you actually receive when a booking comes through an AI channel - is it the same as a direct booking, or is it stripped back to name, party size, and date/time? Who owns the guest profile - does it sit in your system, or does it live in the platform’s database with you getting a limited view of it? And what are you actually allowed to do with the data you do receive - can you market to that guest directly, or do the platform’s terms restrict how you use it? You might have the data in your CRM and still not be permitted to act on it.
None of this is new. Every third party booking channel - OTAs, Reserve with Google, aggregators - has always raised the same questions. The operators who asked them early are in a better position today than those who didn’t. AI booking channels are the same dynamic in a new channel. The difference is that AI channels are moving faster, the platforms building them are larger, and the terms are being written now while most operators aren’t paying attention.
The question worth asking your reservation platform isn’t just whether they’re integrated with AI booking channels, it’s what data you receive when a booking comes through one, who owns the guest profile, and what you’re permitted to do with it. The answer will tell you a lot about whose guest they think it is.