Two paths from "all configured" to "answering live calls." Pick based on whether you want to change your published phone number.
Path A — Go live with a new number
What happens
We give you a fresh Tablevoice number.
You update your website, Google Business Profile, and any directories with the new number.
Old number stays live in the background, or gets retired on your schedule.
The cutover is whenever you've finished updating your published number everywhere.
Pros
Cleanest separation — Tablevoice number vs. legacy number.
No phone-provider involvement.
Easy to revert if needed (just publish the old number again).
Cons
Updating every place your number appears is tedious. Hotel concierges, third-party directories, your own old print materials.
Some guests will keep dialing the old number for months.
Best for
New venues without a long phone-number history.
Venues that don't appear in third-party directories you don't control.
Operators who want a clean slate.
Path B — Forward from your existing number
What happens
Your existing number stays public.
Your phone provider sets up a forward to a Tablevoice number we give you.
Two flavors:
Always-forward — every call goes to Foodie immediately.
Conditional forward — your line rings 3–4 times first; Foodie picks up only if no one answers.
Cutover happens the moment your provider activates the forward.
Pros
No published-number changes anywhere.
Hotel concierges, regulars, search results all keep working.
Reversible by removing the forward.
Cons
Depends on your phone provider playing nicely.
Slight delay for callers — they hear a brief silence as the forward activates.
Conditional mode requires careful setup of ring count and timing.
Best for
Established venues with a known phone presence.
Upscale venues where regulars and concierges have your number saved.
Multi-location groups that want to roll out without coordinating a number-change campaign.
Decision flow
Is your phone number… ├─ Widely known to regulars / concierges → Path B (forwarding) ├─ New or low-traffic → Path A (new number) └─ Embedded in third-party directories → Path B (forwarding)
Hybrid: Path B + later port
Most venues we work with start on Path B. After 2–3 months, if they want Tablevoice to own the number directly (instead of forwarding to it), we can port. This combines Path B's no-change rollout with Path A's clean ownership later. Talk to us when you're ready.
There's no rush to port. Forwarding works perfectly well as a long-term setup.