Guests book on your page, not theirs.
A branded booking portal hosted on your domain. Live availability, deposit at confirmation, self-serve modification links, and automatic reminders — guests complete the booking without leaving your site or seeing another brand's name.
Search, pick, pay — in under two minutes.
The guest types a date and party size, sees real-time slots pulled from your live floor capacity, picks one, and pays a deposit. The booking appears on the host stand before the confirmation email lands.
Slots from live floor capacity — not a static grid
- 6:00 PM Available
- 6:30 PM Available
- 7:00 PM 2 tables — main room or terrace
- 7:30 PM Available
- 8:00 PM Full — join waitlist
Third-party booking site versus your own portal.
Third-party booking platforms are useful for discovery. They are a poor fit as the primary booking channel for a venue with an existing audience — because every booking through their portal is a guest they've introduced you to, not one you've kept.
Third-party booking platform
Their page. Their brand. Their guest.
- Cover fees charged per booking — compounding across every service
- Guest data held by the platform, not the venue
- Redirect breaks the booking flow mid-journey
- Reminders and confirmations carry the platform's branding
- No-show policy set by the platform's defaults
- Reviews and reputation managed on the platform's terms
Your Equimise portal
Your page. Your brand. Your guest.
- No per-cover fees — flat monthly pricing regardless of booking volume
- Every guest record, dietary note, and occasion detail in your CRM
- Stays on your domain from search to deposit confirmation
- Reminders and emails match your brand voice
- Deposit policy, timing, and refund rules set by you
- Guest relationship belongs to the venue from first booking
The questions worth answering before you switch.
Most venues considering the shift from a third-party portal to their own booking page have the same handful of concerns. Here's what the numbers say.
-
Will guests actually find the booking page if it's not on a marketplace?
For an established venue with an existing web presence, most bookings already come from guests who already know the name. The portal replaces the final step — the redirect — not the discovery. For new guest acquisition, the third-party platforms are still useful as a lead channel; you can link both.
-
What happens if two guests try to book the same slot at the same time?
Slots lock the moment a guest enters checkout. If another guest confirms first, the slot is removed from availability before the first guest completes payment. There is no double-booking race.
-
We've never taken deposits before. Won't it put guests off?
Card-on-file deposits — where no charge is taken unless the guest no-shows — convert almost as well as a deposit-free flow and reduce no-shows by 40–60%. Upfront deposits work well for high-demand services like degustation evenings. The portal supports both, and you control which applies to which booking type.
-
Can guests modify or cancel their own booking?
Yes. Every confirmation email includes a self-serve modification link. Guests can change party size, date, time, or add a note without calling the venue. Changes write back to the floor plan in real time.
-
How does it connect to the reservation management side?
The portal is the guest-facing surface. The configuration — table layout, capacity rules, pacing, deposit amounts — lives in the reservations management product at /product/reservations. Changes made there take effect immediately on the public portal.
-
Does it handle walk-ins and the waitlist on a busy night?
When a date or time is full, the portal offers a waitlist join. Hosts manage the walk-in queue from the same floor view as advance bookings. When a table opens, the next person on the waitlist gets an SMS.
A booking page on the venue's own domain converts at roughly twice the rate of the same flow on a third-party portal — partly trust, partly the absence of a redirect that breaks the guest's attention at the exact moment they're ready to commit.
Equimise operations playbook
-
40–60%
lower no-show rate when a deposit is collected at booking
-
2×
conversion rate on-domain versus a third-party redirect
-
Live
availability resolved against the floor plan, not a static slot grid
From the booking page to the pass — on the same data.
-
Reservations management
The operator side — table layout, capacity, pacing, deposit rules, and host stand view that the portal reads from.
Read more → -
Online reservations widget
The booking button you add to your existing site — same engine, smaller footprint for venues with their own marketing pages.
Read more → -
Phone agent
Calls about a booking go to an AI voice agent that books, modifies, and cancels in the same system as the portal.
Read more →
Put bookings back on your page.
Book a 30-minute walkthrough. We'll theme the portal to your brand, run a full booking flow — search to deposit to confirmation — and show you what guests see at every step.