19:47 — Martin's in. He'll want the booth.
Every guest, remembered.
The Guest Graph is a memory your restaurant builds automatically. It's keyed on the one thing guests always give you — their phone number — so the same person is recognised whether they book online, ring up, or walk in.
Real guest cards: visit rhythms, preferences, no-show history and consent — collected as a side effect of taking bookings.
What it knows, and why it matters
Visit rhythms
"33 visits, usually Fridays, last in yesterday." Rhythm is what lets Autopilot know who's overdue rather than just who exists — the difference between a welcome nudge and spam.
Preferences & tags
Window seat. Malbec. Coeliac in the party. Never late. Tags surface on tonight's book and in server briefing cards, so a new starter treats a twenty-visit regular like a twenty-visit regular.
No-show history
Guests who've no-showed before are flagged on tonight's book before it happens again — so you know exactly who needs a confirmation nudge or a deposit.
Consent, done properly
PECR-compliant by design
Consent is captured per guest, per venue, at the moment of booking, and every change is recorded in an append-only log. Marketing messages only ever go to guests who've opted in; service messages like reminders sit on the right side of the line. STOP always works, instantly.
Your guest data is yours. Not a marketplace's. Not ours.
The contrast worth knowing
OpenTable's network fills tables with its members and charges per cover for the privilege. The Guest Graph works the other way: it turns the people who already love your restaurant into the regulars who keep it full. OpenTable rents you their customers. We turn yours into regulars.
Read the honest comparison →Your regulars are already in your diary.
Eightish just remembers them. Start free, or book a setup call.