A 24–48 hour window before launch where our team runs a battery of tests on your setup. Most venues don't need to do anything during this — we'll handle it end-to-end.
What we test
Phone routing
Calls to your Tablevoice number reach Foodie.
If you're using Option B (forwarding), forwarding from your existing number works.
If you're using conditional forwarding, the ring-then-pickup logic timing is right.
Greeting and basics
Foodie answers with the right greeting.
Voice and language match what you picked.
Boosted keywords are heard correctly (Foodie hears your venue's name on the first try).
Pronunciation entries are applied (Foodie says your venue's name correctly).
Reservation booking
A real test booking is created in your reservation system.
Confirmation text is sent.
The booking shows up in Guest Center / Resy / SevenRooms.
We cancel the test booking after confirming.
Group / catering capture
A test group inquiry lands in your Inbox or your CRM.
Notification routing fires.
SMS
Foodie can send a text from your assigned outbound number.
The recipient receives it.
Transfers
A test transfer attempt reaches your transfer number.
The fallback message-capture works if no one picks up.
How we run the tests
Test calls are placed against your live setup, generally 2–3 days before go-live.
We schedule them when traffic is lowest — mid-afternoon on a slow day.
Notifications are temporarily disabled for your team during the testing window so the iPad doesn't light up.
Test bookings are made for dates 2–3 months in the future and are cancelled before launch.
What you'll see
During testing: nothing, if you don't want to. We're operating in the background.
After testing: a quick summary from your onboarding contact — "All clear, ready for launch" or "Found one issue, fixing it."
What might fail
Failure | Cause | Fix |
Reservation lands as "other" dining area | OpenTable dining areas not configured | We fix it for you (or coach you to). |
Foodie can't book — "max party size" error | OpenTable max party size mismatched with venue config | Align the two. |
Transfer doesn't connect | Transfer number wrong, or loop with forwarding | Use a different transfer number. |
SMS not sent | Twilio campaign not yet approved | Wait for campaign approval (1–3 days). |
Most issues are catchable and fixable on our side without you involved.
If you've granted us OpenTable Guest Center access and CRM access, we can fix everything we find without scheduling a meeting. Granting these accesses is the single biggest accelerant for testing.