Upsell at booking.
Pairings, private rooms and keepsakes, sold while guests book, right after, and in one email before they arrive.
Upsell at bookingReconfirmations, deposits, cards on file and a policy per experience, running quietly on every booking. The seats you sold are the seats that arrive.
Locavore NXT · Ubud, BaliThe same system that seats Locavore NXT, Soléa, Empat Group and other venues across Bali every day.
Each one is a setting in Revasi. Switch it on per experience, write the policy in your venue’s words, and the booking flow does the rest.

High-end venues don’t need a heavier hammer. They need the reservation system to do this work in the background, without breaking the brand or the floor team’s rhythm.
Compiled from each platform’s public materials in September 2026. Features vary by plan and region, so if something has changed, tell us and we’ll correct it.
| Feature | Revasi | Resy | Chope | SevenRooms | TableCheck |
|---|---|---|---|---|---|
| Deposit or card on file at booking | Yes | Yes | Yes | Yes | Yes |
| A message asking the guest to reconfirm | Yes | Yes | Yes | Yes | Yes |
| Cancellation policy set per experience | Yes | Yes | Yes | Yes | Partial |
| Fee charged to the card on file | Yes | Yes | Partial | Yes | Yes |
| No-show history on the guest profile | Yes | Not documented | Yes | Partial | Not documented |
| Guest emails in your venue’s name, not the platform’s | Yes | No | Partial | Yes | Yes |
| Feature | Revasi | Resy |
|---|---|---|
| Deposit or card on file at booking | Yes | Yes |
| A message asking the guest to reconfirm | Yes | Yes |
| Cancellation policy set per experience | Yes | Yes |
| Fee charged to the card on file | Yes | Yes |
| No-show history on the guest profile | Yes | Not documented |
| Guest emails in your venue’s name, not the platform’s | Yes | No |
Deposits, policies and reconfirmations, and how they fit a venue that runs more than one kind of evening.
Ahead of each booking, guests are asked whether they’re still coming, and one tap reconfirms. Deposits, cards on file and a cancellation policy per experience mean a no-show isn’t a total loss, and a guest’s earlier no-shows are on their profile when they book again.
Yes. Deposits and cards on file are set per experience, so the tasting menu and the chef’s table can ask for one while à la carte and bar bookings stay quick to book. The cancellation policy is set per experience too.
Your policy for that experience applies. The guest read it before booking and again in their confirmation email, and the deposit or card on file is already in place. If the policy calls for a fee, your team charges the card from the booking.
Like your venue. Confirmations, reconfirmations and cancellation emails go out in your venue’s name, with your own copy, and on Pro in the guest’s language.
Yes. Every guest has a profile with their booking history and your team’s notes. When a known guest books again, earlier no-shows and late cancellations are there before the table is prepped.
Yes. Keep the reconfirmation and skip the deposit for the bar, and ask for a deposit on the tasting menu. Each experience has its own settings and policy, so one system covers both.
Pairings, private rooms and keepsakes, sold while guests book, right after, and in one email before they arrive.
Upsell at bookingAllergies and dietary needs captured at booking, with the follow-up questions your kitchen needs, and kept on the guest’s profile.
Dietary management