A booking button, not a booking system.
The booking button you add to your existing site. Guests pick a date, party size, and time, pay a deposit if you require one, and get a confirmation with a self-service modification link. Your host stand is already updated before they hang up.
A flow they already know how to use.
The booking flow lives inside your site, not a third-party popup that takes guests off your page. Guests pick their details, pay the deposit, and get a confirmation. The whole thing takes under two minutes — which means fewer abandoned bookings and more covers on the books.
Deposits collected at time of booking
- Party size 4 guests
- Date Sat 12 July
- Available times 6:00 PM · 6:30 PM · 7:00 PM
- Selected 7:00 PM
- Deposit required $20 per person
Three details that move a browser to a booking.
-
01
Deposits that commit guests
Requiring a deposit at booking shifts the no-show risk to the guest, not the venue. You set the amount and the cancellation window — the system handles collection, holds, and refunds when the rules say so.
-
02
Self-service modifications
Every confirmation email includes a link for the guest to reschedule or cancel within your rules. Your team handles exceptions — guests manage routine changes themselves without calling the venue.
-
03
Real availability, not a maintained grid
Slot availability comes directly from your live floor map and existing reservations. There's no separate availability grid to keep current — what the booking flow shows is what the floor actually has.
From the first click to the table being ready.
The guest journey and the operator journey happen in parallel. By the time a party walks in, your team already has everything they need.
-
Guest selects date, party size, and time
The available slots come from your live floor map and existing reservations — not a separately maintained calendar. What's shown is what's actually free.
-
Deposit collected at checkout
If your venue requires a deposit, payment is taken before the booking confirms. The amount, cancellation window, and refund rules are set by you — applied automatically for every booking.
-
Confirmation sent with modification link
The guest receives a confirmation email from your venue name with a direct link to reschedule or cancel. No need to call. Changes happen within your rules, automatically.
-
Host stand updates in real time
The booking appears on your host stand the moment it confirms — with party size, any dietary notes, and the guest's name. No import, no morning reconciliation, no printout.
-
Reminder goes out before service
An automated reminder is sent ahead of the booking — timing configurable per venue. Guests who need to cancel do so via their link before they become a no-show.
What operators ask before adding the booking button.
Most questions come down to two things: what the guest experience looks like, and whether it adds work to the front-of-house team.
-
Does it replace my current booking system?
It can, or it can run alongside what you have. The booking button works as a standalone widget connected to the Equimise reservations engine — if you're already using Equimise for your host stand and floor map, everything connects automatically.
-
What happens to deposits if a guest cancels?
Refund behaviour follows the rules you set: full refund outside the cancellation window, partial refund or no refund inside it. The system applies this automatically — no manual processing for routine cancellations.
-
Can guests modify a booking themselves?
Yes. Every confirmation includes a self-service link. Guests can reschedule or cancel according to your rules without calling the venue. For changes outside the rules — like adding guests beyond the max party size — they'll need to contact you directly.
-
Does it work if my site is built on Squarespace, Wix, or WordPress?
Yes. The booking button is a short snippet of code that drops into any page. You don't need a developer — paste it where you want the button to appear and it works.
The booking side and the service side, on the same data.
-
Platform: reservations
Configuration, reporting, and deposit management for your reservations setup — the operator controls behind the booking button.
Read more → -
Reservations (operator)
Your host stand and floor management tools during service — the operator counterpart to guest-facing bookings.
Read more → -
Platform: ordering
If you take pre-orders or set menus with reservations, the ordering platform handles the fulfilment side.
Read more →
Close the gap between booking and service.
Book a 30-minute walkthrough. We'll show you the guest booking flow, the host stand sync, and how deposit rules are configured for your venue type.