19:47Martin's in. He'll want the booth.

Every guest, remembered.Restaurant guest CRM and returning diner recognition

A memory your restaurant builds automatically, keyed on the one thing guests always give you: their phone number. The same person is recognised whether they book online, ring up or walk in.

Eightish Guest Graph showing guest cards with visit counts, usual visiting days, preference tags, no-show history and consent status

Real guest cards: visit rhythms, preferences, no-show history and consent, collected as a side effect of taking bookings.

Visit rhythms

33 visits, usually Fridays, last in yesterday. Rhythm is what lets Autopilot know who is overdue rather than just who exists.

Preferences and tags

Window seat. Malbec. Coeliac in the party. Tags surface on tonight's book so a new starter treats a twenty visit regular like one.

No-show history

Guests who have no-showed before are flagged on tonight's book before it happens again, so you know who needs a nudge or a deposit.

PECRConsent, done properly

Your guest data is yours. Not a marketplace's. Not ours.

Consent is captured per guest, per venue, at the moment of booking, and every change is recorded in an append only log. Marketing goes only to guests who opted in. STOP always works, instantly.

The contrast

OpenTable rents you their customers. We turn yours into regulars.

Its network fills tables with its members and charges per cover for the privilege. The Guest Graph works the other way round.

Read the honest comparison

Your regulars are already in your diary.

Eightish just remembers them.