Loyalist × Revel
Connecting 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.
How it works
Revel records what a table spent, not who was sitting at it. Checks arrive in Loyalist with the spend, any discounts applied, and the table. The check names nobody, as no point-of-sale system does for dine-in service, so each is paired with whichever reservation covered that table that evening. Once a check belongs to a person, spend accumulates per guest rather than per night, and lifetime value becomes something a restaurant can act on rather than a figure in a report.
Key benefits
- Check spend and discounts are brought into Loyalist. The check total, any discounts applied, and the table it was opened on, so what a guest is worth over time is visible on their profile rather than only in a nightly report.
- Checks are matched to guests automatically. A Revel check arrives with no guest attached, so it is paired with the reservation that held its table at that time. Spend then adds up per person, and a frequent modest spender becomes visible next to an occasional large one.
- Campaigns and journeys can be built on what guests actually spend. Lifetime value, average check, and time since the last visit can each define a group, so a message reaches the guests it was meant for rather than the whole list.
- The entire check history is imported at the start. Earlier checks come from the Revel account rather than from the connection date onward, so a regular’s spend is present immediately.
Frequently asked questions
What can I do with Revel spend once it is on a guest?
Treat it as the measure of what a guest is worth. Lifetime value, average check, and time since the last visit all become filters, so a campaign can go to the top spenders who have gone quiet rather than to a general list, and a journey can trigger off a guest’s spending pattern.
How does a Revel check reach the right guest?
Through the reservation. A dine-in check carries no guest identity in any point-of-sale system, so Loyalist pairs each one with the booking that held its table at that service time. A check with no booking behind it stays unmatched, which is why match rate depends on how completely the book is kept.
What happens to my Revel history?
It transfers. Earlier checks load at setup and merge into guest records already held instead of forming a separate list, so totals are correct from the outset.
Last updated