Reservations
Online bookings, phone reservations, walk-ins and cancellations in one book, with availability that reflects the room as it is now.
Loading
Running a restaurant has never been this simple
Take bookings from your own page, the phone and the door, then run the whole service from one screen. BookInn is built to simplify your day, not fill it.
No card to try it. Your booking page is live the same afternoon.
The cooking is the hard part. Keeping track of who is coming, when, and where they will sit should not be a second job done on a phone pad between services.
One Saturday, as it actually arrives.
The same Saturday, in one place.
Six things, each doing one job properly. They share the same data, so a booking taken on the phone is the same booking the floor is looking at.
Online bookings, phone reservations, walk-ins and cancellations in one book, with availability that reflects the room as it is now.
See what is free, what is held and what is running over. When no single table fits, BookInn finds neighbours that can be pushed together.
Visits, allergies, preferences and the occasion, attached to the booking so the team knows before the guest reaches the door.
Confirmations and reminders as standard, and a card held on the tables you cannot afford to lose — paid into your own Stripe account.
Covers, occupancy, repeat guests, peak hours and cancellation rate, from the same data the floor is running on.
A shared view of the service for the whole team, with permissions by role and a record of who changed what.
19:04
Covers on, tables in use, who is seated and who is next — the state of the service in one screen your team can read from across the pass.
38
Bookings today
21
Seated now
79%
Tables in use
11 of 14
2
Waiting
Coming up
The next arrivals, in order
| Time | Guest | Party | Table | Status |
|---|---|---|---|---|
| 19:15 | Okafor | 6 | 4 | Arriving |
| 19:30 | Bell | 2 | 5 | Booked |
| 19:45 | Ash | 4 | W4 | Booked |
| 20:00 | Lindqvist | 2 | W3 | Pending |
| 20:15 | Mensah | 5 | 6 + 7 | Booked |
19:15
Online bookings, phone calls and walk-ins land in the same book, with availability that reflects the room as it is now rather than as it was this morning.
20:15
Your floor plan, live. See what is free, what is held and what is running over — and when a party of five arrives with no table for five, BookInn finds two that can be pushed together.
21:40
Great restaurants remember. BookInn keeps visits, preferences and the things you must not get wrong on the guest, and puts them on the booking before anyone reaches the door.
Amara Okafor
12 visits · last in on 8 August
Previous bookings
23:50
Covers, occupancy, repeat guests, peak hours and no-shows — drawn from the same data the floor ran on, so the numbers are the service rather than a report about it.
185
Covers this week
79%
Average occupancy
34%
Repeat guests
4.1%
No-show rate
Covers by hour
Saturday
Your busiest hour is 20:00, and it is the hour you turn away the most covers.
Twelve covers or twelve hundred, one room or six — the same system, sized to the way you run.
Everything needed to take bookings and run a service, without the complexity of a system built for a chain.
Fill more of the room, see where covers are being lost, and give a larger team one version of the truth.
Several rooms under one account, with settings and permissions that stay consistent across all of them.
Fast turnover, mostly walk-in. A waiting list that quotes a time and calls the party when a table comes free.
The point of the software is to disappear. Everything it takes off your hands is time back on the floor, with the people who came to eat.
Setting BookInn up is an afternoon's work, not a project. Most restaurants take their first online booking the same day.
Draw your floor plan, set your hours, and decide how you want bookings to work. The editor is drag-and-drop, so the plan on screen matches the plan in your head.
Take bookings, seat guests, hold walk-ins and watch the room fill. The team works from one screen, at the pass or on a tablet at the door.
See covers, occupancy and no-shows once service is over, and use what you learn on the next one.
Give your team one place for reservations, tables and guests. Free for fourteen days, no card, and your booking page is live the same afternoon.
Reservation and floor software for restaurants. It holds your bookings, draws your dining room, tracks who is seated and who is late, keeps your guest records, and gives your guests a booking page of their own.
Yes. Every restaurant gets a booking page at its own address, plus a widget you can embed in your own site. A guest picks a party size, a night and a time, and gets a reference — usually in under a minute.
Yes, and they sit in the same book as online bookings. Walk-ins go onto a waiting list with a quoted time, and the queue renumbers itself as parties are seated.
The database refuses them. Two overlapping bookings on one table cannot be written at all, so a clash is not a question of the software checking carefully — it is not possible, however many people are booking at the same moment.
Confirmations and reminders go out as standard, a no-show is recorded against the guest, and you can require a card on the tables you cannot afford to lose. Deposits are paid into your own Stripe account, not ours.
Visits, previous bookings, allergies, preferences and any note your team adds — shown on the booking, so whoever takes the table already knows.
Yes. Several locations sit under one account, each with its own room, hours and booking page, and a staff member’s permissions follow them across the ones they work in.
Something not answered here? Book a demo and ask.