Most of the work falls on us. The decisions that can't fall on us are clearly marked.
What we do
Pre-fill your venue's basic info (menu, hours, address, parking, accessibility) from your public profile.
Configure your reservation integration (OpenTable, Resy, etc.) end-to-end.
Fix dining-area setup in OpenTable when it's missing.
Run pre-deployment tests, including a few real test bookings (and clean them up after).
Set up your phone routing with your provider where we can.
Train your team on the Inbox.
Monitor the first 24 hours after go-live in real-time.
Tune Foodie's pronunciations, knowledge gaps, and behavior in the first week.
What only you can do
The eight decisions. These are about your business, not ours.
Phone-system changes that require your provider. If you're keeping your existing number with conditional forwarding, your phone company needs to set the forward.
Granting access to OpenTable Guest Center, your CRM (Tripleseat / Perfect Venue), and Tablevoice itself.
Training your team — we run the session, but the muscle memory has to come from your staff using the Inbox.
Updating your published phone number if you go live with a new Tablevoice number instead of forwarding.
Telling us when something feels off in the first week. Foodie won't always know.
Who on your side should be involved
Role | Where they're needed |
Owner / decision-maker | The onboarding call. The eight decisions are theirs. |
GM | The onboarding call + team training + the one-week debrief. |
Head host / head reservationist | Team training. Day-to-day Inbox owner. |
Front-of-house staff | Team training. iPad daily flow. |
Phone provider / IT | Only if forwarding from your existing number. We give them what they need; they execute. |
Who on our side
Pascal or Jose — your dedicated onboarding contact. Runs the live sessions. Cell-number reachable through go-live week.
Marc — co-founder. Cell-number reachable for anything urgent.
The Tablevoice team — monitors the first 24 hours of every new launch. Tunes Foodie behind the scenes.
]]>