Feature Spotlight: Tripleseat to Resy

What it does

Your events team carries on working exactly as they do now. The status they set on an event in Tripleseat is what drives the tables in Resy, so there is no second system to update and no new habit to pick up.

The hold that lands in Resy is not a mystery block. It carries the event name, the time and the party size, so whoever is looking at the book knows what it is and who to ask about it.

And your team is told when anything changes. An event created, moved or cancelled generates an alert, which is what lets people stop checking.

Why it matters

Because until something does this, two teams are sharing one dining room through a system of remembering.

The events team sells the private room, or the back half of the floor, or the whole restaurant on a Tuesday. That lives in Tripleseat. The book carries on selling tables to anyone who wants one, because Resy has no idea the room was promised to somebody else. Between those two facts is a person who has to notice, open the reservation platform, and pull the tables out by hand.

It goes wrong in both directions.

Forget to block, and you have sold the same table twice. Someone has to be cancelled, and it is usually the guest. One diner described a three-Michelin-star restaurant cancelling their honeymoon reservation because of a sudden private event. The restaurant had an event to honour. The guest had a story to tell.

Forget to release, and a tentative event that never got confirmed leaves a hold sitting on your best tables. You walk into a Saturday with a section nobody can book. That one costs you quietly, which is why it usually goes unnoticed for longer.

Resy OS does not sync Tripleseat events into the book on its own, so the usual alternative is a manual process that has to be repeated for every change and every cancellation. It works, right up until the night it does not. Most groups end up running a weekly audit where somebody compares the two calendars line by line. That audit is the tell. If you need a weekly check to catch what the process missed, the process is not working.

What else it does for your events team

Keeping the book in step is the part people notice first. Once Tripleseat and Resy are talking through Loyalist, three more things come with it.

Event hosts are tagged in Resy. The person who booked your forty-person holiday party is one of your most valuable guests, and in most restaurants the host stand has no idea when they walk in for dinner. Loyalist tags event hosts in the reservation system, so the floor knows who they are looking at.

One pre-shift report for the whole night. Tonight’s events and tonight’s dining reservations land in the same pre-shift report. The manager running the floor sees the buyout in the back room and the regular at table 12 on one page, instead of reading two systems and reconciling them in their head.

Your dining room becomes an events pipeline. Your best future event clients are often already eating with you. Loyalist surfaces the diners who look like event hosts, such as high spenders or guests booking from a company email, so your events team can reach out to people who already like the room.

The full set of event tools is on the Loyalist x Tripleseat page.

How restaurants are using it

It has been running since the second quarter of 2026, across accounts from single rooms up to groups doing seven and eight figures a year in event revenue.

The pattern is the same at both ends. The weekly audit stops. Nobody compares the Tripleseat calendar against the Resy book on a Monday, because there is nothing left to catch.

At the larger groups, where events and reservations are separate teams who may not sit in the same building, the thing that changes is that neither team has to trust the other to remember. The handoff that used to depend on one person at the end of a long shift is simply not a handoff any more.

The failure that disappears first is the quiet one. Double bookings get noticed, because a guest is standing in front of you. Stale holds on a Saturday section never get noticed at all, and that is the revenue this gets back.

What to expect

The sync happens hourly.

It will not cancel a guest. If a table is already booked when an event comes in, the conflict is flagged and a person decides what happens next. That is deliberate. The alternative is software cancelling somebody’s anniversary dinner at two in the morning.

It is not retroactive. Events that already existed before you switch it on are not blocked. One pass over your book at setup and you are current.

It runs one way. Tripleseat is the source of truth for events. Changes made to a block inside Resy do not travel back.

Getting started

The sync is included on Pro, and available as an add-on on Core. Setup happens with our onboarding team and takes one session.

Sources

• Loyalist Tripleseat to Resy sync product documentation, and the Loyalist x Tripleseat events suite.
• Tripleseat help center: OpenTable Guest Center and SevenRooms integration articles. Tock help center: Tripleseat Events integration.
• Resy help desk: how to block a table for a shift in Resy OS (manual blocking).
• Reddit r/finedining: “Last minute reservation cancellation due to restaurant ‘privatization’.”

---