17:30Before doors
Six rooms of one house.Everything in the Eightish restaurant booking system
One system follows a booking from the tap on your link to the night the guest comes back. Each part exists because something goes wrong in a restaurant without it.
22:30One booking, all the way through
The same table, six times.
A guest taps your link from the sofa
The booking page recognises their number from last time and takes the booking in four taps. No account to create.
The Guest Graph takes a note
Fourth visit. Last time someone in the party was coeliac. It remembers so your new starter doesn't have to.
A reminder they'll actually read
A text the day before, with a one word cancel. A cancellation at five is a table you can still fill. A no-show at eight is not.
The host stand runs the room
The floor plan shows who is finishing, where the walk-in for four fits, and which bookings are flagged as a risk.
Autopilot looks at next Wednesday
It's thin. Autopilot offers held tables to a handful of overdue regulars and keeps a holdout group back so it can prove the lift.
The week, in plain English
Reports tell you the no-show rate, what messaging cost, and whether any of it worked.
Host stand
→Tonight as a live floor plan. Works offline, syncs when the connection returns.
Autopilot
→Fills the quiet night from your own regulars, with the reason for every send.
Guest Graph
→Every guest by phone number, consent included.
Booking page
→Mobile first. Embeds on your site or works as a link.
Reminders
→One thread per booking. Cancelling is one word.
Reports
→Sentences, not dashboards. Plus a nightly brief.
Three things we did on purpose.
The floor plan is the main view
Most systems lead with a grid. A floor plan is better for a room you can take in at a glance, which is what most restaurants are. The grid is one tap away.
Every automated message shows its reason
If a system is going to message your guests in your name, you should see why it picked them before it does.
Recovered covers are proved, not claimed
A holdout group is held back from every Autopilot cycle. Slower to report, and the only honest way to.
Questions restaurateurs ask
Do I have to use all of it?
No. Most restaurants start with the booking page and the diary, add reminders once they trust it, and turn on Autopilot when there are a few months of guest history for it to work from.
Does Eightish replace my POS?
No. Eightish manages the diary, the floor and the guest relationship. Your till stays where it is.
Can I take phone bookings and walk-ins in the same diary?
Yes. Manual entries and walk-ins sit on the same floor plan as online bookings, and they are never counted or charged.
What happens if the internet drops mid-service?
The host stand keeps working. Table changes queue locally and sync when the connection returns.
Run one Friday on it.
Start with the free booking page, or see what everything costs. No form, no call.