Reserving takes bookings from your own website, fits every party to a real table, room or chair, and keeps the whole floor on one board. Deposits and reminders bring the guests who booked.
Harbour Room
Service 17:00 to 23:00
Service board
Table fitted
Deposit rule
No-show risk
Reminders
The engine above is the one that runs a venue. It is set to Harbour Room, the venue we built for this demo: eleven tables across two, four and six seats, service from 17:00 to 23:00, a 105 minute turn on a four-top and a 15 minute buffer between parties. Change the party size, pick a time, and the fit runs in front of you.
01
The engine picks the smallest table that seats the party, applies the turn time and the buffer, and checks the bookings already on that row. If the exact time is gone, it returns the three nearest times that genuinely fit instead of an empty result.
02
The booking is drawn on the timeline against the table it was fitted to, next to everything else in that service. One table holds one booking at a time, so the same six-top cannot be promised twice.
03
Your rules decide whether a card is asked for: party size, day part, service and whether the guest has been in before. The demo names the rule that fired and shows exactly what the guest would see on the booking page.
04
Every booking gets a score you can read rather than believe. Lead time, party size, day part, channel, new or returning guest, phone confirmed and deposit held each carry their own weight, and the demo lists what every factor contributed.
05
Confirmation goes out the second the booking lands. The reminder sequence is counted back from the booking time, 24 hours before and 3 hours before, each with one tap to confirm or cancel so the table comes back while it can still be sold.
A snippet goes on your site and the widget matches your fonts and colours. The booking page runs on your own domain, so the guest never leaves your brand and you never pay a commission on a regular who was already yours.
Phone, widget, Google, Instagram and the walk-in queue land in one book. The fit engine holds turn times, service windows and buffers, so a table can carry one party at a time and the paper diary stops being the source of truth.
Deposit rules on the bookings that deserve them, a reminder sequence with one-tap confirm, a waiting queue that fills a cancelled slot automatically, and a risk score that tells the host which bookings to call first.
A group with a dining room, four rooms upstairs and two treatment chairs runs all three on one board with one login, instead of paying three vertical systems that never talk to each other.
How it works
01
Copy the snippet and drop it into your site, your Squarespace or WordPress page, your Linktree or your Google profile. The widget inherits your styling and the booking page answers on your domain.
02
Enter the tables and their seats, the rooms or the chairs, your service windows, your turn times and the buffer you want between parties. This is the part that makes the fit real instead of a calendar with names in it.
03
Bookings land on the board the moment they are made, confirmations go out on their own, reminders go out on the schedule you set, and deposits are asked for where your rules say they should be.
| Table | Seats | Turn |
|---|---|---|
| T1 to T4 | 2 | 75 min |
| T5 to T9 | 4 | 105 min |
| T10 to T11 | 6 | 135 min |
| Buffer | 15 min |
For groups
Reserving is bought by operations as often as it is bought by a host stand. Multi-Venue puts up to five venues on one account, with roles and permissions per venue, shared guest profiles across the group and one export that covers all of them.
Covers, cancellations, no-show rate and deposit recovery, per venue and across the group, in one place and in one export. Roles decide who sees what, so a venue manager sees their venue and the group sees everything.
Covers per service, average spend, current no-show rate and the deposit rate you would set. The calculator works on your numbers and shows what recovering part of those covers is worth in a month. We publish no benchmark of our own, because the only honest numbers here are yours.
Covers lost a month
Revenue in those covers
Pricing
Pricing is per venue and per month, and it does not move when you get busy. There is no free plan and nothing is sold as a one-time purchase. Every plan renews until you cancel it, and the demo above runs without a card.
Core
49 USD per venue
What the month includes
1 venue, 3 staff logins, 300 bookings, email confirmations and reminders
Growth
Deposits and SMS149 USD per venue
What the month includes
10 staff logins, unlimited bookings, deposits, SMS, risk score, waiting queue
Multi-Venue
499 USD, up to 5 venues
What the month includes
5 venues, unlimited logins, group reporting, yield rules, API and webhooks
Enterprise
Talk to sales
What the month includes
Unlimited venues, SSO and SCIM, audit log, uptime commitment, invoicing
Growth adds deposits and the reminder sequence, the two things that move the no-show number.
Compare
Platforms that charge per cover bill you again for the regulars you brought in yourself, and the bill grows on exactly the nights that went well. Reserving charges for the venue, not for the guest, so a full Saturday costs the same as a quiet Tuesday.
| What you are comparing | Per-cover marketplace | One system per vertical | Reserving |
|---|---|---|---|
| What the fee follows | the number of guests seated | the venue, but one vertical only | the venue, flat per month |
| Tables, rooms and chairs | tables only | one of the three | all three on one board |
| Where the guest books | mostly on the platform | on your site | on your site and your domain |
| Who owns the guest record | shared with the platform | the venue | the venue, exportable any time |
| What a busy month costs | more than a quiet one | the same | the same |
It replaces it. Existing bookings come across by CSV import, you can run both systems side by side for a service while the team gets used to the board, and your booking page keeps the same address so nothing you have printed or linked goes stale.
The same as when you are quiet. The fee is per venue per month and it does not move with covers, so a sold out weekend does not raise the bill.
A table, room or chair holds one booking at a time. The fit engine applies the turn time, the buffer and the service window before it accepts anything, so two parties cannot land on the same six-top at 19:30.
No. The widget asks for a name, a phone number and an email, and that is the whole booking. Nobody is asked to sign up to eat at your place.
No. Deposits and card holds are taken on the booking page when the guest books, and your rules decide which bookings are asked for one.
Yes. The widget inherits your site styling and the booking page runs on your own domain, so guests stay inside your brand from the first click to the confirmation email.
You do. Guest records, booking history and notes belong to the venue, and you can export or delete them on request. Security says where the data lives and who can reach it.
Yes, on Multi-Venue and Enterprise, with roles and permissions per venue and shared guest profiles across the group.
Those sit on Enterprise: SAML single sign-on, SCIM provisioning, an audit log, annual invoicing against a purchase order and a security review before you sign.
Create your account with one email address and set up your first venue. No card, and nothing is charged until you pick a plan.
Enter the email address that runs your venue and we take it from there. One field, no card, no sales call.
By creating an account you agree to the terms and the privacy policy.