Setting up Tablevoice
Everything you need to get going.
60 articles
- What we test (Tablevoice-side)The pre-launch battery of tests we run end-to-end against your setup — phone, greeting, bookings, CRM, SMS, and transfers.
- Test before you go liveTwo layers of testing before launch — what we do on our side and what you should try yourself.
- Set up dining areas in OpenTable so your AI host seats guests rightConfigure OpenTable dining areas, table types, and floor plans so Foodie can describe seating clearly and avoid the "Other" trap.
- Phone orders & takeoutHow Foodie handles phone orders and takeout — transfer, capture-and-forward, or direct POS integration.
- Handoffs / transfersThe handoff playbook — Foodie introduces the call to your team, drops out on pickup, and falls back to a message if no one answers.
- Catering inquiriesHow Foodie captures off-site catering, drop-off, and large takeout leads and routes them to your CRM or coordinator.
- ComplaintsHow Foodie listens, captures, and routes complaints to a manager — never auto-resolves, never argues with a script.
- Lost itemsHow Foodie captures item descriptions, visit details, and callback info for lost-and-found inquiries.
- Late arrivalsHow Foodie captures a "running late" message, reassures the guest, and pings your host stand.
- Group reservation requestsHow Foodie captures and routes parties above your auto-book limit, without ever auto-booking.
- Reservations: new, modify, cancelThe bread-and-butter playbook — how Foodie books, modifies, and cancels reservations through your reservation system.
- PlaybooksHow Foodie handles each scenario — reservations, group requests, late arrivals, lost items, complaints, catering, transfers, phone orders.
- Going live: Save vs Update AgentThe all-important two-click publish step — Save Changes stores edits, Update Agent pushes them live.
- Pronunciation, keywords, keypadThree small but high-impact features: pronunciation guide (IPA), boosted keywords for speech-to-text, and keypad input detection.
- Phone numbers & transfer settingsWhere the incoming number, SMS-from number, transfer toggle, transfer number, and DTMF detection live in the app.
- Personality, voice, languageWhere in the app to set Foodie's response style, voice, language mode, and opening line — the brand-feel controls.
- Agent behaviorHow Foodie sounds and acts on a call — voice, language, transfer rules, pronunciation, and the all-important publish step.
- Private events & roomsConfigure buyouts, private rooms, catering, deposits, and cancellation policies — the longest config page, with the most moving parts.
- AccessibilityPrecise accessibility info for entrance, restroom, seating, parking, elevators, and loading — what guests with mobility needs rely on.
- TripleSeat: live status & manual pushSee where every TripleSeat lead stands without leaving the app — and push a lead manually when it isn't sent automatically.
- The venue calendar: closures, pauses, holidays & moreOne calendar for everything date-driven — reservation pauses, closures, special hours, holidays, events, and announcements — read by your AI Host.
- Support & contactThree tiers of support — self-serve, async email and your onboarding contact, and urgent cell numbers — plus what we promise and how to escalate.
- What's newRecent Tablevoice product updates by month — features that shipped, changes in behavior, and how to report bugs or request features.
- FAQComposite of the most-asked questions across how Tablevoice works, phones, reservations, languages, going live, after go-live, pricing, and comparisons.
- GlossaryDefinitions for Tablevoice-specific terms (Foodie, Inbox, Playbook), voice-AI vocabulary (PWA, IPA, DTMF, TTS), and common reservation-system jargon.
- ReferenceQuick lookups — glossary, FAQ, what's new, and how to reach the Tablevoice team.
- Compare Locations dashboardSide-by-side benchmarking once two or more venues are live — what to watch for, common patterns, and the right cadence.
- Per-venue customization without divergingStandardize the system, vary the data — what should match across venues, what should differ, and how to keep things from drifting.
- Rolling out across venuesThe four-stage rollout pattern for multi-venue groups — pilot, learn, wave-by-wave, refine — plus common traps.
- Org-level vs venue-level settingsTwo-level model in Tablevoice — what lives at the org level, what lives at the venue level, and how inheritance works.
- For multi-location groupsHow multi-venue groups should think about Tablevoice — org vs venue split, rollout order, and brand consistency.
- Common bumps and what they meanTypical first-week issues — off-brand replies, pronunciation, missed bookings, transfer failures, notifications — and how to fix each.
- The first 24 hoursWhat we do, what you do, and what to look for in the Inbox during your launch day.
- Where to update your numberIf you went with a new Tablevoice number, the prioritized checklist of places to update — website, GBP, directories, signatures, ads, and more.
- New number vs call forwardingComparison of the two launch paths — Tablevoice number you publish, or forwarding from your existing line — with pros, cons, and best-fit cases.
- Going liveTwo paths to live — a new Tablevoice number or a forward from your existing line — plus what happens on launch day.
- Pre-deployment FAQMost-asked questions before launch: test bookings, notifications, reporting, timing, and what happens when something fails.
- What you should testA ~20-minute self-test checklist your team can run before go-live, covering voice, reservations, CRM, knowledge, and edge cases.
- WelcomeAn overview of the Tablevoice onboarding journey — what you'll find in this guide and the two principles that shape it.
- What to expect over the next two weeksThe typical two-week onboarding cadence — sign-up and access, internal configuration, the onboarding call, team training, testing, go-live, and the one-week debrief.
- Who does what — your team and oursA breakdown of which onboarding tasks Tablevoice handles, which you handle, and who on your team should be involved at each step.
- How to use this hubThree ways to read this knowledge base — top-down for first-time operators, targeted for the onboarding call, or reference once you're live.
- Decisions you'll makeOverview of the eight key decisions that shape how Foodie works at your venue.
- Phone routingHow to decide what callers hear: a new Tablevoice number, forwarding from your existing line, or a shipped VoIP phone.
- How reservations get bookedThree modes for handling reservations: Confirmation Needed, Send a link by text, or fully Integrated with your booking platform.
- Large parties & private eventsWhere to set the cutoff between Foodie auto-booking and capturing a group lead, plus CRM and buyout options.
- Cancellations & modificationsWhen Foodie can handle reservation changes directly versus transferring to a human, especially when money is involved.
- Voice & personalityBrand decisions for how Foodie sounds at your venue: response style, voice, language modes, pronunciation, and the opening line.
- Transportation & parkingDirections, parking, transit, bike racks, and EV charging — the boring-but-asked-constantly logistics.
- Events & specialsHappy hour, ongoing promotions, special events, and discounts — keep this current so Foodie quotes the latest offers.
- House rulesPolicies guests ask about most: dress code, alcohol and BYOB, payments, gratuity, gift cards, and pet policies.
- Services & amenitiesYes/No toggles for dining options, meals served, family amenities, and venue features so Foodie can answer common questions.
- MenuMenu text Foodie can quote, dietary toggles, the link to your full online menu, and an allergies statement.
- HoursHow to set regular hours and call transfer hours — including the one-click Google Maps sync. Date-specific changes like holidays live on the venue calendar.
- Live transfersWhen Foodie can hand a call to a human, which number she dials, and how Call Transfer Hours gate the behavior.
- NotificationsWho gets pinged for what events, by email or push, with role-based presets and tips to avoid alert fatigue.
- Multi-location decisionsHow to organize multi-venue groups: org-level vs venue-level settings, rollout order, super-admin access, and cross-sell.
- Business detailsThe basics Foodie needs: venue name, description, address, contact info, time zone, and primary language.
- Venue configuration referenceField-by-field reference for every setting in the Tablevoice app, organized into Restaurant knowledge, Agent behavior, and Playbooks.
- Restaurant knowledgeWhat Foodie knows about your venue — the information she quotes verbatim when guests ask, from hours and menu to amenities and policies.