Appointment booking software built around the floor, not the calendar
Most booking tools are a calendar with names written in it. The difference here is the fit engine underneath: every request is checked against a real table, room or chair, with the turn time and the buffer applied, before anyone is told yes.
01
The widget that lives on your own site
One snippet puts booking on your website in your own styling, and the booking page runs on your own domain. Guests book without making an account, with a name, a phone number and an email, and you keep every record.
- Inherits the fonts, colours and radius of the page it sits on
- Booking page on your domain, not on ours
- Works on WordPress, Squarespace, Wix, Shopify and hand-built sites
- Plain booking link for a Google profile, an Instagram bio or a QR code on the table
- Party size, date, time and service in four taps on a phone
02
The fit engine, which is the part that stops the arguments
A request comes in for six at 19:30. The engine finds the smallest table that seats six, applies your turn time and your buffer, checks what is already on that row and respects the service window. If 19:30 does not fit, it returns the three nearest times that do, because a venue loses the booking when the answer is just no.
Smallest suitable table, room or chair, so the big ones stay free for big parties
Turn time per party size and per service
Buffer between two parties on the same table
Service windows, closed days and seasonal hours
One booking per table at a time, so double booking is blocked at the source
Combinable tables for parties that need two pushed together
03
One timeline for tables, rooms and chairs
The board is one row per table, room or chair and one column per slice of the service. Bookings from the widget, the phone, Google and Instagram all land on it. Moving a booking re-runs the fit instead of just moving a label, so tidying up cannot create a clash.
- Colour-free status carried by weight: held, confirmed, at risk
- Walk-in queue with a quoted wait time, so the door and the book agree
- Guest record on the booking: visit history, allergies, notes, the seat they always ask for
- Party notes visible to the kitchen and the host at the same time
04
Deposits, card holds and a risk score you can read
Deposits are the blunt instrument. The risk score is the precise one, and the two work together.
Deposit and card-hold rules by party size, day part, service and guest history
Card taken on the booking page, with no card reader at the venue
No-show risk score on every booking, with every factor and its weight listed
Signals used: lead time, party size, day part, channel, new or returning guest, phone confirmed, deposit held
Waiting queue that offers a cancelled slot to the next party automatically
A no-show fee policy you can actually enforce, because the guest agreed to it when booking
05
Confirmations and reminders that bring the guest back
The confirmation goes out the second the booking is made, and the reminder sequence is counted back from the booking time. One tap confirms, one tap cancels, and a cancellation that arrives at 16:00 is a table you can still sell.
Confirmation email immediately, with the details and a cancel link
Reminder 24 hours before and again 3 hours before
SMS reminders with two-way confirm and cancel on Growth and above
Your wording and your sender name, in your own language
Every message logged against the booking, so nobody has to ask whether it went out
06
Numbers your accountant recognises
- Covers, cancellations, no-show rate and deposit recovery by venue, by service and by day part
- Where bookings come from: widget, Google, Instagram, phone, walk-in
- Group reporting across up to five venues on Multi-Venue
- CSV export of bookings and guest records, on request and without asking us
- API, webhooks and POS or PMS export on Multi-Venue and Enterprise
- SAML single sign-on, SCIM and an audit log on Enterprise, described on security
The same engine, set up for your kind of venue
Every feature on this page is in every paid plan
The plan decides how many venues, logins and bookings you have, not which parts of the product you get.