A typical onboarding runs about two weeks from your verbal yes to the first real guest call. Faster is possible. Slower happens. Here's the rough cadence.
The two-week shape
Week 1 — Setup
Day 1–2 — Sign-up & access. You complete the sign-up form (legal entity, billing, Twilio campaign info). We start spinning up your tenant in the background.
Day 3–4 — Internal configuration. Our team pre-fills as much of your venue as we can from public info — your menu, hours, OpenTable profile. You don't see this part; it's just so the onboarding call doesn't start from a blank page.
Day 5–7 — The onboarding call. A 60-minute screen-share with Pascal or Jose where we walk through the eight decisions and configure your venue together.
Week 2 — Launch
Day 8–10 — Team training. A 30-minute session with your front-of-house team to walk through the Inbox, the iPad app, and notifications. Anyone who'll touch the Tablevoice app should be there.
Day 11–12 — Pre-deployment testing. We run tests on your setup. You can run your own too. Anything broken gets fixed.
Day 13–14 — Go-live. The phone routing flips. Foodie starts answering real calls. We monitor the first day in real-time.
Week 3 (and beyond)
Around day 21 — The one-week debrief. A 30-minute call to review what's working, what's awkward, what to tune.
Why this much hand-holding
We could send you a setup wizard and a help-center link and call it a day. We don't, because every venue's reservation rules, phone setup, and team workflow have edges that don't show up until somebody walks through them with you. Pascal and Jose have run hundreds of these now — they catch things you wouldn't think to ask about.
What can speed it up
Decision-makers in the room for the onboarding call (not someone passed the meeting from a manager).
Granting us OpenTable Guest Center and CRM access early — lets us configure on your behalf and run testing without a meeting.
Booking the team training before go-live, not after.
What slows it down
A phone-system change (porting, multi-line VoIP) that requires your provider's involvement.
An OpenTable account that needs dining areas configured before integration works — we'll usually fix this for you.
Multi-venue rollouts where the org-level decisions haven't been agreed yet.
]]>