Loyalist × Tock

How it works

Most reservation platforms tell a restaurant that someone is coming. Tock often tells it what they have already paid. Bookings arrive in Loyalist with the party size, the service date and time, the state Tock holds for them, the table, and whether the booking was cancelled or recorded as a no-show. Notes stay split the way Tock splits them, so a dietary restriction does not get flattened into a general note. Guest feedback arrives on the reservation as well, which puts a rating and a comment next to the visit they describe. Upcoming bookings are visible ahead of service, so tonight’s book can be read before the door opens.

Key benefits

• All Tock booking, guest, and payment details are brought into Loyalist. The party size, service time, state, and table, plus the guest’s name, email, phone, birthday, anniversary, and postal address, along with tags and notes assembled from the group-level profile, the venue’s own notes, and the guest’s stated dietary restrictions, aversions, and hospitality preferences.
• A prepaid booking arrives with the money already attached. The subtotal, tax, service charge, gratuity, event and custom fees, total, amount paid, refunds, discounts, and the payment methods behind them all come across, and the booking becomes an order on the visit. Spend lands on the profile without waiting for a check to be matched to it.
• Guests can be grouped by what they actually paid. A segment can be built on what a booking was worth, on how often someone books a ticketed experience, or on the dietary preferences they declared. The same data produces tonight’s kitchen brief and the list a campaign goes to.
• Automated messages run off real Tock activity. A first booking can trigger a welcome, a ninety-day gap can trigger a win-back, and an upcoming reservation can trigger a reminder. Tock also carries birthdays and anniversaries, which reservation data rarely does, so the one date a guest is glad to hear about can drive a message as well.
• Guest feedback sits on the visit it belongs to. A rating and a comment arrive with the reservation rather than through a separate review feed, so a remark about a particular night is on that night’s record and reads in sequence with everything else the guest has done.
• The whole book is imported at the start. History loads from the account rather than from the date of connection. Tock accounts can hold a decade of bookings, so large venues are loaded in stages and the starting point is chosen deliberately during onboarding.

Frequently asked questions

How does prepayment from Tock show up in Loyalist?

As an order attached to the visit, not just a note on the booking. The subtotal, tax, service charge, gratuity, any event or custom fees, the total, the amount paid, refunds, discounts, and the payment methods are all read. For a room selling a tasting menu or a ticketed experience, that is the difference between knowing a guest booked and knowing what they spent.

How are dietary restrictions from Tock used?

They stay as their own detail rather than being folded into a general note, which means they can be read as a group instead of one booking at a time. Tonight’s dietary requirements can be pulled for the kitchen before service, and the same information can keep a guest off a message about a menu that would not suit them.

Do my past Tock reservations come across?

Yes. Historical bookings load during onboarding and are matched into the guest profiles already in the guestbook, so a guest known from a check, a review, or an event is not duplicated. Tock accounts can hold years of history, so large venues are loaded in stages rather than in a single pass.

Last updated August 23, 2026