Reservation Platform

Reservation platforms are the front door of guest data. Resy, OpenTable, SevenRooms, and Tock take the booking, hold the book, run the seating screen during service, and accumulate a guest record out of what they have seen. A restaurant CRM sits above them and reads all of it, because a group’s guest history almost never lives in one book.

Is a reservation platform the same thing as a guest CRM?

No, and the difference is scope rather than sophistication. A reservation platform holds bookings, so it knows who reserved, how many were coming, what the party asked for, and whether they arrived. It does not know what the table ordered or spent, because the check closes in the point of sale. It also knows only its own bookings. A guest who walks in, buys a gift card, replies to an email, or books a private event elsewhere does not exist in that book.

Several platforms include email and guest-marketing tools, and those tools work inside the same boundary. The audience is the people who booked through that platform at that venue, which is a useful list and a partial one.

Why don’t two reservation platforms report the same thing?

Because the platforms do not define the underlying signals the same way, and the differences are rarely documented anywhere an operator would find them. Confirmation is the clearest case. Resy, OpenTable, and SevenRooms each expose a guest-confirmation signal. Tock does not deliver one at all, so an unconfirmed booking means the guest was asked and did not answer on the first three, and means nobody asked on the fourth.

Tags, guest notes, and no-show marking vary in the same way, in structure and in who is allowed to set them. A group running two books is holding two dialects of the same information. Translating between them is work that falls to whatever sits above the platforms, since neither book has any reason to know the other exists.

What happens to my guest history if I change reservation platforms?

Contact details usually travel and context usually does not. Export terms differ by platform and are worth checking in your own contract before you switch, but the pattern operators describe is that names, emails, and phone numbers move while the structured history does not: per-booking notes, tags, visit counts, and no-show marks all sat in the old platform’s own shape. The new book can open with a list of names and little history behind them, which is why switching tends to reset how well a room recognizes its own regulars.

Guest records held outside any single book survive the change. Loyalist reads bookings and guest records out of Resy, OpenTable, SevenRooms, and Tock, and writes tags and guest notes back into the platforms that support it, so the guestbook belongs to the group rather than to the current vendor.