One guest book for the whole group — allergies first
Every visit, preference and allergy follows the guest from one location to the next. Your team greets regulars by name; your kitchen never gets surprised.
Know every guest
- Preferences, structured allergies (safety-critical, never freetext), tags, VIP flags, birthdays and anniversaries, and full visit history.
- Auto-tags that explain themselves — regular, big spender, no-show-prone — each with its reason ("avg \$180/cover vs \$45 house average") and a per-rule pause switch.
- Smart lists: saved segments that stay live — build one from filters, or ask in plain English and save the answer ("regulars we haven't seen in 90 days").
- Categorized staff notes with authors and timestamps, plus private post-visit feedback that lands on the profile — never a public review site.
- Real spend and lifetime value per guest when your POS is connected (Pro).
- Instant search from any screen — ⌘K finds a guest, tonight's booking or a confirmation code.
Clean data by design
- Duplicate detection on every guest create with an explicit merge tool — never a silent merge.
- A phone match while seating a walk-in asks "same person?" instead of quietly reusing a profile.
- GDPR export and right-to-erasure that anonymizes visits while preserving your analytics.
- Import your OpenTable guest book with automatic column mapping and free-text dietary notes converted to structured allergens.
Use it during service
- Tap any seated guest for their full card right on the floor — allergies leading, contact, preferences, notes and recent visits.
- Attach several known guests to one party; shared visits build a connections graph that powers "often dines with" suggestions.
- Per-seat allergy cards on the live floor — "Seat 3, no shellfish" where the server actually looks.
- Optional AI pre-arrival briefings: "3rd visit, anniversary last time, prefers the window" (Pro).
- VIP alerts ring a bell on every staff screen when a VIP — or anyone on a watch list — books or arrives, with the host briefing attached.
- Public reviews match back to the actual visit, so a 2-star "we waited forever" sits beside that table's real course timeline.
More of the platform
See it on your own floor plan
Start free, build your room in an afternoon, and take a booking on your own website today.
Common questions
Does TableStack share the guest book across locations?
Yes. Guests belong to the organization, not a single venue, so preferences, structured allergies and visit history follow the guest to every location in the group.
How does TableStack store allergies?
As structured allergens with severities — never free text. Allergy flags render on the seat card and the floor view, because this is a safety feature as much as a hospitality one.
Can TableStack handle a guest's right to be forgotten?
Yes. Erasure anonymizes the guest — name, contact details, notes, preferences, allergies and tags are scrubbed — while visit history is preserved in anonymized form for analytics.