Reservations that respect your floor plan and pacing. A loyalty engine that remembers birthdays, allergies, wine preferences, and last-visit favorites. Guest history that follows the guest, not the location.
Every capability listed below is included in the base module. No add-ons, no unlock fees, no per-seat surcharges. If you're on xRESTAURANTx, you have this.
Direct booking page under your domain. Guest picks time, party size, and gets the confirmation email seconds later. No third-party marketplace markup.
Configure your pacing — max covers per turn, guest-facing time slots, kitchen capacity limits. The booker respects them so the kitchen never gets slammed.
Guest arrives. Server sees: last 4 visits, favorite table, food allergies, wine preferences, birthday. Two-second guest-recognition.
Points, tiers, birthday freebies, referral rewards — configure the model that fits your brand. Loyalty follows the guest across locations for franchise groups.
Full room? Add to the waitlist, the guest gets an SMS with wait estimate. Two seats open, they get an SMS. You don't lose them to the sushi place three doors down.
Push availability to OpenTable, Resy, and Google Reserve while keeping your own booking page as primary. No double-booking, no dashboard tab-hopping.
Every operator we onboard runs this same tutorial in their first week. Most complete it in one sit-down; the whole team is comfortable inside two shifts.
Tables, capacity, section owner. Then the pacing config: how many covers per turn per section, minimum turn time, buffer for slow tables. The booker respects the config.
One-click publish to your subdomain (reserve.yourrestaurant.com) or embed on your existing site. Guests book, confirmations fire, calendar syncs.
Guest gives allergy info during booking (voluntary). Server sees it on arrival. Chef sees it on ticket. Cross-contact protocol enforces at every station.
Pick the model — points, tiers, visit-based, spend-based, referral-based. Set the redemption catalog. Loyalty is optional for guests; opt-in from the booking flow.
Enable waitlist mode. When you're full, guests join the waitlist and get an SMS with an estimated wait. Two seats open, first guest on the list gets a 'come now' text.
xRESTAURANTx modules are not sold separately. Bundle everything — you pay one flat rate keyed to your restaurant's size, not a per-module upsell.
Concrete scenarios from actual operators using the module in production. Every scenario carries a metric or a mechanism, not a marketing slogan.
Guest books. System pulls history: 4 prior visits, always Table 6, always the tasting menu, no seafood, spouse is on a low-sodium protocol. Captain greets them by name and confirms the tasting.
Same guest books Location A on Friday, Location B on Sunday. Their tier, points balance, and preferences follow them. Loyalty math computes once, across the group.
Yes. Push availability to OpenTable; xRESTAURANTx becomes the source of truth. Bookings from OpenTable land in your dashboard alongside your direct bookings. You keep the direct-booking margin AND the OpenTable discoverability.
Yes. Every guest owns their profile. Data is scoped per-restaurant unless the guest explicitly connects two restaurants. GDPR + CCPA compliant end-to-end.
Yes. The default templates cover 90% of restaurant loyalty models, but the engine is configurable — tier thresholds, point earn rates, redemption catalog, expiration rules. Anything you can describe, we can configure.
xRESTAURANTx modules are designed to work together. These four are the ones most operators use alongside Reservations & Loyalty.
Book a 20-minute demo. We'll walk through Reservations & Loyalty on your actual menu and show you how it lands on the floor.