We run a battery of tests on your setup before flipping the switch. You can also test it yourself, and we recommend it — your team will catch nuances we won't.
Two layers of testing
What we test
The phone number routes correctly.
Foodie picks up with the right greeting.
A real test booking lands in OpenTable / Resy.
A test group lead lands in Tripleseat or Perfect Venue.
SMS sends and receives.
Transfers reach a human.
We handle this end-to-end. If you've granted us Guest Center / CRM access, you don't need to lift a finger.
What you should test
Call from your own phone. Hear the greeting. Try a few questions.
Run a reservation in your test environment. See if it shows up.
Ask Foodie about your menu, parking, dress code.
Try a request you don't want Foodie to handle on her own — see how she falls back.
The whole thing takes ~20 minutes and surfaces the small stuff worth fixing before guests hear it.
Why we bother
Most venues go live without major issues. But every OpenTable configuration is a snowflake — party-size limits, shift rules, blocked-off events, deposits — and we'd rather catch the surprises 48 hours before launch than 48 minutes after the first guest calls.
Pre-deployment FAQ
We've answered the questions we hear most often — will test bookings show up in our reports? will my team get spammed with notifications? — in Pre-deployment FAQ under this section.
Up next: What we test (Tablevoice-side) and What you should test.