The system, room by room
Six rooms of one house.
Eightish is not a diary with features bolted on. It is one system that follows a single booking from the moment a guest taps your link to the moment you find out whether they came back — and every part of it exists because one specific thing goes wrong in a restaurant without it.
One booking, all the way through
Here is the same booking passing through all six parts, which is the fastest way to understand what any of them are for.
A guest finds you on Instagram at half past ten at night and taps your link. The booking widget loads on their phone, recognises their number from the last time they came, and takes the booking in four taps with no account to create. The Guest Graph quietly notes that this is their fourth visit and that last time somebody in the party was coeliac.
The day before, Eightish sends a reminder — not an email nobody opens — and if they can't make it, cancelling is one word, which turns a no-show at eight o'clock into a table you can still fill at five. On the night, the host stand shows the whole room live: which tables are finishing, where the walk-in for four fits, and which bookings are flagged as no-show risks before they happen.
Next Wednesday looks thin. Autopilot notices before you do, picks a handful of regulars who are overdue a visit, offers them a held table, and keeps a holdout group back so it can prove the covers it recovered were actually incremental. On Sunday, reports tell you in plain English what your no-show rate was, what messaging cost, and whether any of it worked.
The six parts
Host stand →
A live floor plan of tonight rather than a grid you have to decode. Table states, zones, turn timers, walk-ins, the waitlist, and no-show risks flagged before service starts. Works offline — changes queue and sync when the connection returns.
Without it: the book and the room disagree, and only the person holding the pen knows which is right.
Autopilot →
An agent that watches the diary, finds the quiet night ahead, and offers held tables to your own overdue regulars — with the reason it chose each guest, the cost of each message, and a holdout group that proves the lift was real.
Without it: quiet Tuesdays are something that happens to you.
Guest Graph →
Every guest remembered by phone number: visit rhythms, preferences and allergies, no-show history, and per-venue consent captured properly under PECR with an append-only record of it.
Without it: your fourth-time regular is greeted like a stranger.
Booking widget →
A mobile-first booking page with no diner account to create, returning-guest recognition by number, and deposits where the risk actually justifies one. Embeds on your own site or works as a standalone link.
Without it: bookings happen only when someone is by the phone.
WhatsApp-first reminders and confirmations with SMS fallback, in one thread per booking. Reminders that get read are the single most effective no-show tool there is, and they only work if cancelling is easy.
Without it: you discover the no-show at 8pm, which is too late to do anything about it.
Reports →
Your week in sentences, not dashboards: covers, no-show rate, covers recovered, and what messaging actually cost. Plus a nightly brief on how service went.
Without it: you have a strong feeling about how last month went and no number to check it against.
What we deliberately did differently
The floor plan is the main view, not a second tab
Most booking systems lead with a grid — time along one axis, tables down the other. A grid is better for a 200-cover site running several sittings. A floor plan is better for a room you can take in at a glance, which is what most independent restaurants actually are. We chose the second, on purpose, and the grid timeline is still there when you need it.
Every automated message shows its reason
When Autopilot picks a guest, it tells you why it picked them — last visit, visit count, the gap it is filling. Marketing tools generally show you a send and a result. If a system is going to message your guests in your name, you should be able to see its reasoning before it does.
Recovered covers are proved, not claimed
Autopilot holds a group of guests back from every outreach cycle. Comparing the two groups is the difference between "we sent messages and bookings went up" and "these covers would not have happened otherwise". It is a slower way to report a number and the only honest one.
Questions restaurateurs actually 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 only turn on Autopilot when there are a few months of guest history for it to work from. Every part works without the others.
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 entry and walk-ins sit on the same floor plan as online bookings. A booking system that only knows about the bookings it took itself isn't a booking system.
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 required. If you're moving from another system, switching takes one 45-minute session.