Loyalist × Resy
Resy reservations arrive in Loyalist with the party size, status, table, shift, and booking source, along with the guest record behind them, including guest notes, tags, and VIP status. Tags and notes written in Loyalist can be pushed back into Resy, so the book a host works carries what the guestbook knows.
How it works
Resy connects to Loyalist as a two-way integration. Bookings and the guest records behind them are read in through the service day, and guest notes, tags, and VIP status can be written back into the book. Historical reservations are loaded during onboarding, back to the venue’s first booking rather than to the date of connection.
Key benefits
- All Resy guest and visit details are brought into Loyalist. Party size, status, table, seating area, shift, special requests, floor notes, server, and seated time, plus the guest’s name, email, mobile number, birthday, notes, tags, and VIP status. Bookings are labelled by source, so ResyOS, app, phone, walk-in, and concierge stay distinguishable.
- Matching Resy bookings to POS, reviews, and guest data creates a complete guest profile. A reservation stops being a standalone record and sits beside what the table spent, what the guest wrote afterwards, and any private event they hosted. That is what makes visit frequency, lifetime value, and campaign results countable.
- Marketing runs automatically off Resy activity. A first visit can trigger a welcome, a ninety-day gap can trigger a win-back, and a returning regular can be flagged to the floor before they arrive, all from reservation activity rather than from someone watching the book.
- Guest segments are built from real Resy visit behaviour. Visit frequency, recency, party size, and no-show history all become filters, so the guests who came three times last quarter and have not been back since can be pulled up in a moment and sent something worth returning for.
- Guest notes and tags are synced between Loyalist and Resy. Resy holds guest notes as separate entries, so a note written in Loyalist sits alongside what a manager wrote last month instead of replacing it.
- The full reservation history is imported at onboarding. History loads back to the venue’s first booking rather than the date of connection, so a guest who has been coming since 2019 looks like a regular on day one instead of a first-timer.
Exclusive offer
Restaurants running Resy OS get an exclusive Loyalist partner offer when they connect. The connection itself is the same either way: reservations and guest records read in, tags and notes written back. The offer covers the commercial terms for Resy OS venues, and the current terms are on the Resy partner page.
Frequently asked questions
What happens to my Resy reservation history?
It comes with you. Historical reservations are loaded during onboarding, back to the venue’s first booking in Resy rather than to the date of connection, and each one is matched into the existing guest profiles rather than creating a parallel set of records. From then on, new bookings and their changes flow into the guestbook through the service day, so the profile a host reads is current.
Can Loyalist write guest notes back to Resy?
Yes. Guest notes, guest tags, VIP status, and reservation notes can all be written back into Resy, so what the team learns in Loyalist reaches the book where reservations are worked. Resy holds guest notes as distinct entries, so a note written from Loyalist sits alongside what the venue has already written instead of replacing it.
Do I need my own developers to connect Resy?
No. Connecting Resy is handled during onboarding, including the historical load, and nothing has to be built on the restaurant’s side. The work that does need a decision is on the guest-data side rather than the technical side: which tags matter, what belongs in a guest note, and which statuses a team wants written back into the book.
Last updated
