Loyalist × OpenTable

How it works

A reservation platform tells a restaurant that a table is booked. It does not tell them who is coming. Loyalist is an OpenTable integration partner, and the connection runs both ways: bookings and the guest records behind them come in, while notes, tags, and new reservations go back out. OpenTable keeps guest notes in several separate fields, covering general notes, food and drink, seating, and relationships, and all of them are read and merged onto one profile rather than one being chosen. Birthdays and anniversaries arrive as notable dates. OpenTable also keeps a no-show marker on a reservation even when the party turns up late and is seated, so Loyalist only counts a no-show where there is no record of the party being seated at all. Without that check a venue’s no-show rate reads higher than it really is.

Key benefits

• All OpenTable reservation and guest details are brought into Loyalist. Party size, the scheduled time, the arrival and seated times, the table and seating area resolved against the right floor plan, the shift, diner notes, venue notes, reservation tags, the server, and the experience booked. Referral and campaign parameters stay on the reservation.
• A regular at one venue is recognised at every other one in the group. Visit history, notes, and tags sit on the guest rather than on a venue, so someone booking their first table at the second restaurant reads as a regular of the first instead of as a stranger.
• Automated marketing runs off real OpenTable activity. Visit frequency, recency, party size, and no-shows all become filters, so a first visit can trigger a welcome message, a ninety-day gap can trigger a win-back email, and a returning regular can be flagged to the floor before they arrive.
• Notes, tags, and new reservations go back into OpenTable. What the team learns in Loyalist reaches the screen the floor already uses during service, and a VIP hold or a recovery offer can be booked without anyone opening a second system. Floor teams do not adopt a second screen mid-service, so the recognition has to arrive where they are.
• Marketing consent transfers with the wording the guest agreed to. OpenTable reports whether a guest opted in or out of a venue’s email marketing, and the exact opt-in wording they saw is recorded alongside it. The guests who said no stay off the list, and the ones who said yes can be emailed without anyone guessing.
• The whole reservation history is imported at the start. Bookings load back to the venue’s first reservation in OpenTable rather than to the date of connection, and each is matched into the guest profiles already in the guestbook instead of creating a second set of records.

Frequently asked questions

Can Loyalist write guest notes back to OpenTable?

Yes. Guest notes, guest tags, and reservation notes and tags can all be written back, and new reservations can be created in OpenTable as well. One condition is worth knowing. A tag needs the guest to already exist at that venue in OpenTable. A guest Loyalist knows from somewhere else may need a first booking there before the tag has anywhere to land.

How does OpenTable consent work once it is in Loyalist?

OpenTable reports each guest’s email marketing opt-in or opt-out for the venue, and Loyalist records it along with the wording the guest was shown when they agreed. That means an opt-in carries evidence of what was actually consented to, and a guest who said no is left out of marketing sent from Loyalist rather than quietly reappearing on a list.

What happens to my OpenTable reservation history?

It transfers. Historical reservations load during onboarding, starting from the venue’s first booking in OpenTable rather than from the day of connection. New bookings and their changes are pulled through the service day, then again after the day closes. A reservation that went from booked to seated to done is not left frozen at whichever state it arrived in.

Last updated August 23, 2026