Integrations
Loyalist connects to the systems your room already runs on
Point of sale, reservations, delivery, marketing and reviews: every fragment of the guest, reconciled into one profile.
42 integrations
Reservations
ResyResy 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.
OpenTableConnecting OpenTable puts every booking and note on the guest rather than in the book, so a regular at one venue is recognised across the group and marketing runs off real booking activity. Notes and tags written in Loyalist go back into OpenTable, where the floor already works.
SevenRoomsConnecting SevenRooms puts every booking, note, and consent state on the guest rather than in the book, so a regular at one venue is recognised across the group and marketing runs off real booking activity. Notes written in Loyalist can be pushed back onto the reservation, where the floor already works.
TockA prepaid Tock booking arrives in Loyalist already carrying what the guest paid, so spend reaches the profile without waiting for a point-of-sale check to be matched. Dietary notes stay separate from general notes, guest feedback comes in on the reservation itself, and the guest record includes the anniversary and address Tock collects.
WiselyWisely holds the waitlist and the reservation book, so walk-ins and booked tables arrive in Loyalist as one stream. A guest who usually walks in and occasionally books is one relationship rather than two, and marketing runs off the whole picture.
POS
ToastConnecting Toast puts what a guest actually spends onto their profile. Every closed check, the items on it, and the modifiers behind them attach to the person who ordered, so a restaurant can see lifetime spend per guest and target campaigns on buying history: the regulars who order heavily from the wine list, the guests whose checks run large.
SquareConnecting Square puts what a guest actually spends onto their profile. Closed orders arrive with the items rung in, and where a Square customer record is attached to the payment, the order reaches that guest directly. A restaurant can then see lifetime spend per person and market on buying history.
UpserveConnecting Upserve puts what a guest actually spends onto their profile. Checks arrive with the items rung in and the modifiers attached to them, and each is matched to the reservation that held its table, so spend becomes part of a guest's history rather than a nightly total.
SpotOnConnecting SpotOn puts what a guest actually spends onto their profile. Checks arrive with the items rung in, the modifiers attached to them, and any discounts applied, and each one reaches a guest through the reservation, so a restaurant can market on buying history rather than on covers alone.
SalidoConnecting Salido puts what a guest actually spends onto their profile. Checks arrive with the items rung in and the modifiers attached to them, and each is matched to the reservation that held its table, so a restaurant can build campaigns on what guests order rather than on covers alone.
LightspeedConnecting Lightspeed puts what a guest actually spends onto their profile. Checks arrive with the items rung in and the modifiers attached to them, and each is matched to the reservation that held its table, so a restaurant can build campaigns on buying history rather than on covers alone.
OmnivoreOmnivore brings check and item detail into Loyalist from point-of-sale systems connected through an Omnivore terminal. Each check is matched to the reservation that held its table, so spend becomes part of a guest's history rather than a nightly total.
SilverwareConnecting Silverware puts what a guest actually spends onto their profile. Checks arrive with the items rung in, the modifiers attached to them, and the discounts applied, and each is matched to the reservation that held its table, so spend becomes part of a guest's history.
Oracle SimphonyConnecting Simphony puts what a guest actually spends onto their profile. Checks arrive with the items rung in, the modifiers attached to them, and any discounts applied, and each is matched to the reservation that held its table, so spend becomes part of a guest's history rather than a nightly total.
TouchBistroConnecting TouchBistro puts what a guest actually spends onto their profile. Checks arrive with the items rung in, the modifiers attached to them, and any discounts applied, and each one reaches a guest through the reservation, so a restaurant can build campaigns on buying history.
RevelConnecting Revel brings closed checks into Loyalist and matches each one to the reservation that held its table, so spend becomes part of a guest's history rather than a daily total. A restaurant can then see what a guest is worth over time and build campaigns on it.
SauceDelivery and takeout orders arrive from Sauce carrying the guest's name, email, and phone, so an off-premise order reaches a profile directly instead of waiting on a table-and-time match. What people order off-premise then counts towards the same guest as what they order in the room.
ParrotLoyalist connects Parrot for our Latin American restaurants, putting what a guest spends in the dining room onto their profile. Closed checks arrive with the items rung in, the modifier options chosen on each one, any discounts applied, and the covers on the table, and each check reaches a guest through the booking that held it.
AlohaAloha checks come into Loyalist with the items rung in, the voids and discounts applied, and the service charges, and each is matched to the reservation that held its table. Spend then belongs to a guest rather than to a nightly sales report.
AgilysysAgilysys runs the outlets across a whole property, so a guest's spend in the restaurant, the bar and by the pool arrives in Loyalist as one person's activity rather than three separate outlet reports. Room charges tie that spend back to the stay.
HeartlandHeartland checks arrive in Loyalist with the items rung in and how the check was settled, including house accounts. Each is matched to the reservation that held its table, so what a guest spends over time sits on their profile rather than in a sales report.
FigureFigure orders arrive in Loyalist with the items and modifiers rung in and the price of each, and are matched onto the guest who was sitting there. What somebody orders then reads as preference rather than as a line in a sales report.
Events / catering
TripleseatPrivate 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.
Perfect VenuePrivate event bookings from Perfect Venue land on the guest profile beside their reservations and spend, so the person who booked the back room is recognisable as a regular of the dining room rather than a separate customer.
SpoonfedCatering orders come from Spoonfed into Loyalist with their line items and the contact behind them, so a corporate lunch account sits on the same guest record as the dining room and the private events a restaurant already tracks.
DICEA ticket buyer gives their name and email to buy, so DICE is one of the few things a venue runs where the audience identifies itself. Those buyers, what they paid and which artists they came for arrive in Loyalist as guest records.
Hotel / PMS
StayntouchStayntouch stays join the same guest record as that person's restaurant visits, so somebody staying in the hotel and eating in the dining room is recognised as one guest rather than two unrelated customers. Restaurant history is then available before a hotel guest arrives, and what they spend on a stay counts towards what they are worth.
CloudbedsCloudbeds stays land on the same guest record as that person's restaurant visits, so a hotel guest who eats in the dining room is one relationship rather than two. Notes move in both directions, which means a preference recorded at dinner can reach the front desk.
MewsMews keeps a guest profile that exists in its own right rather than only inside a booking, so a returning hotel guest is recognisable across stays. Those stays join the same record as their restaurant visits, making one guest out of two halves of the property.
Oracle OPERAOPERA runs the front desk at a large share of full-service hotels, holding the guest profile, the reservation and the folio. Connecting it puts a stay on the same record as that guest's restaurant visits, so the property sees one person rather than two.
InforInfor HMS holds the stay and the guest profile behind it, including the preferences a property records over time. Connecting it puts that history on the same record as the guest's restaurant visits, so a returning guest is known by both sides.
Reviews & listings
Google ReviewsGoogle reviews come into Loyalist and land on the guest who wrote them wherever the details support it, so a complaint sits beside that person's visits and spend rather than in a review inbox. Replies can be sent from Loyalist without opening the Google dashboard.
YelpYelp reviews come into Loyalist and attach to the guest who wrote them wherever the details support it, so a review reads alongside that person's visits rather than in isolation. Replies can be sent from Loyalist rather than from the Yelp dashboard.
SundayGuests who pay by scanning a code at the table are asked how it went while they are still sitting there, and that feedback comes into Loyalist on their profile. Paying is the moment people actually answer, so it arrives in volume rather than occasionally.
MetaLoyalist pushes business hours to a Facebook Page and then reads the Page back to confirm the change landed, so the listing's live state is something a restaurant can verify rather than assume. Holiday and seasonal hours reach the Page too, so a closure decided this morning can be published this morning.
TripAdvisorTripAdvisor reviews come into Loyalist and land on the guest who wrote them wherever the details support it, so a review sits beside that person's visits and spend rather than in a separate feed. TripAdvisor then reads alongside the other review platforms a restaurant is on.
Membership / loyalty
PeopleVineA member's PeopleVine standing arrives in Loyalist and sits on their profile, so membership is visible next to their visits, spend, and preferences. Clubs can then treat members as members without their team opening a second system. A member's spend across every room in the club adds up on one record rather than in several.
PaytronixA guest's Paytronix loyalty standing arrives in Loyalist and sits on their profile, so their tier and the perks attached to it are visible alongside their visits and spend rather than only inside the loyalty platform. A floor team then knows who they are dealing with, and marketing can treat members and non-members as the separate audiences they are.
Payments
Analytics & other
AveroAvero brings check spend into Loyalist from point-of-sale systems that have no direct connection of their own, including Aloha, NCR, and Micros. Each check is matched to the reservation that held its table, so spend becomes part of a guest's history rather than a nightly total.
ShopifyRetail and online orders from Shopify join the same guest records as dining visits, so a customer buying wine or merchandise is the same person who books a table. Email-capture signups arrive too, even when they have never ordered anything.
Up 'n GoFeedback a guest leaves when they pay at the table comes into Loyalist as a review on their profile, so it reads alongside their visits and whatever they have said on public platforms. Paying is the moment a guest is most likely to answer, which is why this feedback arrives in volume.
