Thirty minutes is a realistic number for a single-location restaurant with a menu that's already in reasonably good shape, not a marketing claim. Here's what actually happens during that half hour, whichever vendor you use, and what tends to blow past the 30-minute mark if you're not ready for it.
Before you start: what to have ready
Setup goes fast when you walk in with these already gathered:
- Your current menu, ideally as a POS export or a clean PDF, not a photo of a printed menu with three years of handwritten price changes on it
- Your modifiers and combos written out (sizes, toppings, sides, sauces) since these take longer to configure than the base menu items
- Your hours, including any different hours for delivery vs. pickup vs. dine-in phone orders
- Login access to your POS, if you're planning to connect one
- A decision on escalation: which calls should always go to a human, if any (catering, complaints, large orders)
If your menu is messy (inconsistent naming, prices that don't match what's actually charged, modifiers that only exist verbally), expect setup to take longer than 30 minutes, because that cleanup work has to happen somewhere. It's worth doing it now regardless of which system you use; a clean menu also makes your POS and online ordering more accurate.
The setup walkthrough
- Import the menu (10–15 minutes). Most platforms let you upload a POS export or CSV, then you review it item by item. This is the step to actually double-check rather than skim. A wrong price or a missing modifier here is what causes a bad customer call later.
- Set your voice and greeting (2–3 minutes). Pick a voice, write or approve the greeting script (restaurant name, basic framing), and decide whether it should mention specials.
- Configure escalation rules (5 minutes). Decide what gets transferred live to a staff member, what goes to voicemail with a transcript, and what the AI should handle end to end.
- Connect your POS, if applicable (5–10 minutes). This is usually an OAuth-style login to your POS account rather than anything technical on your end. If you don't have POS integration available, orders can typically route to a screen, printer, or SMS/email instead.
- Forward your number (2 minutes). This is a call-forwarding setting through your existing phone provider. You're not porting or changing your number, just telling it where to route.
- Run test calls (5–10 minutes). Call in yourself. Order something normal, then something slightly odd — a substitution, a "no onions," a question about hours. This is the step people skip and shouldn't.
What actually goes wrong
- Menu items with the same name but different prices across dine-in and delivery. Decide up front which the phone system should quote.
- Modifiers that exist "in the cooks' heads" but were never written down anywhere, so the AI has no way to know about them until you tell it.
- Forwarding set up incorrectly, so calls ring through but audio doesn't connect. Always end with a real test call from a phone that isn't in the building.
- No plan for a system outage. Ask your vendor what happens if their service goes down: does the call fail silently, or fall back to ringing your phone normally?
After you go live
Setup isn't really "done" after the first day. It's worth checking call transcripts for the first week to catch anything the menu import missed (an unusual modifier request, a mispronounced dish name it didn't recognize). Most of what looks like an AI "mistake" in week one turns out to be a menu configuration gap, and it's a five-minute fix once you see it.
The honest timeline
Thirty minutes covers the mechanical setup. Give yourself the better part of a week before you fully trust it unattended — not because the software is slow, but because that's how long it takes to catch the handful of menu edge cases every restaurant has and nobody thinks to mention until a customer asks for it.