If you run more than one venue under a single brand or hospitality group, this section is for you. Single-venue operators can skip it.
Org-level vs venue-level
Two levels of settings exist in Tablevoice:
Org-level (the whole group) — billing, super-admin access, brand-wide playbook defaults, cross-venue reporting. Set once at the top.
Venue-level (each restaurant) — hours, menu, voice, phone routing, OpenTable connection. Different per venue.
When you log in, the venue dropdown at the top of the sidebar tells you which venue's settings you're editing. Always check before you save.
Rolling out across venues
We almost never recommend launching all venues at once. The pattern that works:
Pick one venue to launch first. Ideally not your busiest, not your slowest. The middle venue, where mistakes are visible but not catastrophic.
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.
Per-venue 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).
Compare Locations dashboard
Once you have two or more venues live, the Compare Locations tab in your Analytics dashboard becomes useful: ranks venues by call volume, conversion rate, transfer pickup rate, resolution time. Spot the laggard early.
Continue to Org-level vs venue-level settings.