One Guest Profile Across Every Branch
A guest who eats at your Marina branch on Friday and your Downtown branch on Tuesday thinks of you as one restaurant. Your systems often disagree: two profiles, two points balances, and an allergy remembered in one branch and forgotten in the other. One profile per guest fixes that.
Why it matters
- Allergies travel with the guest. A nut allergy noted in one branch should flag dishes in every branch.
- Loyalty adds up. Points and tiers should reflect every visit, not split across locations.
- You see the real regular. A guest who visits each branch occasionally may be your most frequent customer overall.
- Win-back is accurate. A guest who moved to another branch has not lapsed.
What a good profile holds
What the guest chose to tell you, and what they did:
- Name and contact details, and marketing consent
- Allergies and food and dining preferences
- Visit and order history, across branches
- Tier, points and rewards
- Family dates such as birthdays, if they shared them
On WowMenu, the profile's preference graph is built from what the guest does in the QR menu, so it fills in without anyone typing notes.
How your team uses it
At the table, waiters see a read-only profile: tier, points, allergies and preferences. Managers see the full directory, with tags such as VIP, Regular, Corporate or First Timer, allergy flags, visits and spend.
Consent and privacy
One profile means more responsibility, not less. Keep it simple and honest:
- Guests sign in by choice
- Marketing consent is separate and starts unticked
- Consent shows on the profile, so nobody messages a guest who said no
- Only use what the guest shared
Getting there
Invite guests to sign in once, with a small welcome reward, and switch on loyalty. If you are moving from another system, import your existing guest list with consent mapped; read bulk guest import when switching systems.
See the guest CRM and multi-location ordering.
