Loyalist × Tripleseat
Private events are usually tracked in one system and dining in another, so the same person looks like two customers. Tripleseat events land on the guest profile beside their reservations and spend, and confirmed events can be written into the Resy book, so the floor and the events office work from one record.
How it works
Private events happen in a different system from dining. Tripleseat holds the buyout and the rehearsal dinner, the book holds the Tuesday two-top, and the same guest can sit in both without either system knowing. Loyalist reads events out of Tripleseat and keeps them current as they change, so an inquiry that becomes a tentative hold and then a definite booking stays one record rather than three. The planner who booked a rehearsal dinner in March and a holiday party in December lands on one profile. From there the events office can see that a prospect is already a regular, and a segment can include the people who book rooms rather than only the ones who book tables.
Key benefits
- All Tripleseat event and inquiry details are brought into Loyalist. The status Tripleseat holds for the event, the date and time window, the guest count, the rooms it occupies, the event type, the market segment, and the subtotal and total on the contract. Notes from the original inquiry come across with it, along with the corporate account it was booked under.
- Every event a guest has hosted adds up on one profile. A guest who spends a few hundred dollars twice a month in the dining room and thirty thousand on a December buyout is one relationship, and in most groups two teams track it in two systems. On one profile the floor can see that the Tuesday two-top runs the company party.
- Journeys can follow up on an event inquiry without anyone remembering to. A new inquiry can start a nurture sequence, an event reaching confirmed can start a different one, and a lead that never became a booking can be re-engaged later. Event follow-up stops depending on who has time for it that week.
- Loyalist is the only platform that can sync Tripleseat to Resy. A confirmed event is written into the book as a reservation that holds the space for its duration, with the mapped tables, the guest count, and the planner’s contact details in the note. Later edits or cancellations move or release it, so a host reading the book sees the whole night.
- The entire event history is imported at the beginning. History loads back through the whole Tripleseat account rather than starting at the date of connection, so a room’s regulars are recognisable immediately instead of after a year of rebuilding the record.
Frequently asked questions
Do event bookers and regulars end up as one guest?
Usually, yes. Tripleseat identifies the person who booked each event, so two events from the same planner are recognised as one guest rather than treated as two people who happen to share a name. The guest who planned a forty-person holiday party and the regular at table 12 stop being separate records, and their event history and dining history read as one timeline.
Can Loyalist connect Tripleseat to Resy?
Yes, and Loyalist is the only platform that does it. Qualifying events are created in the Resy book as reservations that hold the space for the event’s duration, with the mapped tables, the event’s guest count, and a note carrying the planner’s contact details. Which events qualify is set per venue by status, keyword, and buffer rules, and later changes or cancellations in Tripleseat update the booking.
Are inquiries that never became bookings still kept?
Yes, and they are worth keeping. An inquiry is ingested in its own right, so a lead that was turned down or simply went quiet stays in the record of who has asked about the room. That history is what a re-engagement journey runs on later, and it is also the honest picture of demand for a space that a converted-events list alone will not show.
Last updated
