Decision: if you run more than one venue, how do you organize them in Tablevoice? This page covers the org-vs-venue split, rollout order, and super-admin access. If you're a single venue, skip to Venue configuration reference.
The two-level model
Org-level — the umbrella
Settings that apply to the whole group:
Billing — one Stripe account, one invoice. (Or several if you've asked for separate invoicing per venue.)
Super-admin user accounts — owners, multi-venue GMs, the people who need access to every venue.
Brand-wide playbook templates — the late-arrival message, the complaint script, the language mode — all default to org-level.
Cross-venue analytics — the Compare Locations dashboard.
Venue-level — each restaurant
Settings that vary per venue:
Hours, menu, address, parking — different per venue, obviously.
Voice and language — can vary per venue (a French-Canadian voice for the Montréal location, an American voice for the Toronto location).
Phone routing — each venue has its own number, its own forwarding rule.
OpenTable / Resy connection — each venue has its own.
Notification routing — different team per venue.
Switching between venues in the app
The venue dropdown lives at the top of the left sidebar. Pick the venue you're editing. Always check before you save. It's a common error to edit Hours thinking you're at the Montréal venue and accidentally change Toronto's.
Rollout order
We almost never recommend launching all venues simultaneously. Even for groups that want to. The pattern that works:
Pick one venue to launch first. Not your busiest, not your slowest. Middle-volume, where mistakes are visible but not catastrophic. Sushi by Bou launched at Chelsea first; that worked well.
Run for a week. Tune what needs tuning. Build internal confidence.
Roll the rest in waves. 2–3 venues per week is typical for a 5–10 venue group. Faster is possible — we just don't recommend it because the first-week-of-each-venue tuning load adds up.
Per-venue customization without divergence
The temptation: every GM customizes their venue's voice, playbooks, and message templates differently. The result: an inconsistent brand experience and a maintenance nightmare. The discipline: standardize at the org level, customize only the things that genuinely vary by location — hours, menu, parking, accessibility.
Things that should always match across venues in the same brand:
Voice style (Casual / Friendly / Balanced / Formal / Very Formal)
Late-arrival message wording
Cancellation policy quoting
Complaint-handling script
Things that should vary by venue:
Voice/accent (you might want different)
Hours, menu, address, parking, accessibility
Phone number
Notification routing
Specific named pronunciations
Super-admin access
Who should have super-admin (org-level) access?
Yes: owner, multi-venue GM, head of operations, head of reservations.
No: individual venue managers — they should only see their venue.
No: front-of-house staff — they should only see their venue.
Keep super-admin to the smallest list practical. It's tempting to give it to everyone; resist.
Cross-sell between venues
When Foodie can't book at the venue a guest called for (fully booked, outside hours), she can offer alternatives at sister venues in your group. Configure this per venue:
Cross-sell on / off
Which sister venues are valid alternatives (proximity, brand fit — not every Tabule guest wants Tabule Bayview vs. Riverside)
Seen as a feature by guests, not a bait-and-switch — done well, conversion across the group goes up.
Compare Locations dashboard
Once you have two or more venues live, the Compare Locations tab in your Analytics dashboard ranks venues by:
Call volume
Reservation conversion
Transfer pickup rate
Median resolution time
Complaint rate
Useful for spotting the laggard early. See The Analytics Dashboard for more.
How to change it later
Adding a venue is a setup process — we'll do it with you. Re-organizing brands within an org ("these three venues should split off") is more involved but possible — ask.
Common questions
Can two venues share a phone number?
No. Each venue gets its own number (or its own forward target). This is a hard constraint.
Can I have one venue on Integrated reservations and another on Send-a-link?
Yes. Reservation method is venue-level.
What about brands within a brand — a Tabule group with a Tabule Express sub-brand?
We handle this with venue-level branding (each venue can have its own brand name and voice). Cross-org structures are rare; ask if you have one.
Wizard decision_key: multi-location