The questions we hear most often before launch. If yours isn't here, ask your onboarding contact — they'll add the answer.
Test bookings
Will the test bookings be real reservations in our system?
Yes. All test bookings go through your live OpenTable / Resy / etc. configuration so we can be sure everything works exactly as guests will experience it. We keep them 2–3 months in the future and limit testing to 2–3 reservations total. If you've granted us Guest Center access, we cancel them directly — no action from your team.
Do we have to do testing? Can we skip it?
You can. Things often work without it — most venues go live without issues. That said, every reservation system has its quirks (party-size limits, shift rules, blocked-off events) and we'd rather catch them before your first real guest call. We strongly recommend testing. The choice is yours.
What if our booking window doesn't allow reservations far enough out?
We work within your window. If your booking window is short, we'll book as far out as it allows.
Will test leads show up in our CRM (Tripleseat / Perfect Venue)?
Yes — a small number of test leads will be submitted to confirm the integration works. They're clearly marked as tests. If you've granted us CRM access, we'll remove them after — no work for your events team.
Will this affect our pipeline or reporting in our CRM?
Possibly, depending on how your team tracks lead activity. It may be worth a quick internal conversation about whether test leads can be fully excluded from reporting (rather than simply being marked rejected, which can still count against conversion metrics).
Notifications during testing
Will our team get flooded with notifications during testing?
No. We disable all Tablevoice-generated notifications for the duration of the testing window and re-enable them once testing is complete. Your team won't be aware it's happening.
Test calls
Will any test calls be transferred to our actual phone line?
Yes, but minimum — typically 3–4 transfers to confirm the handoff is working correctly. Your team may briefly answer them. We'll let you know roughly when this is happening so it doesn't catch anyone off guard.
Will anyone on our team need to be available during testing?
In most cases, no. If you've granted us Guest Center access, testing is handled entirely on our end — we'll let you know when it's scheduled and confirm when it's done. If you haven't, we'll book a short call to review test bookings together before cancelling and proceeding to launch.
Reporting
Will test calls show up in our Tablevoice dashboard?
No. We remove all test calls before going live, so they're not included in your reporting.
Timing
How long does pre-deployment testing take?
We like to have 24–48 hours, but it can be completed faster if needed.
When something fails
What happens if something doesn't pass testing?
We fix it. In most cases, configuration issues are something we can resolve on our end without involving your team. We'll only reach out if we need additional information from you, or if the fix involves a material change to how guests interact with the system — in which case we'll walk you through it before going live.
During-test support
Who do we contact if we have questions during testing?
Your dedicated Tablevoice onboarding contact is your point of call. You can also reach the team at [email protected]. We aim to respond within a few hours.