If you run SpotOn, the only question that decides whether a voice agent is worth paying for is whether the order lands in SpotOn correctly. Voice quality is the thing vendors demo and the thing that matters least. A pleasant agent that drops a modifier hands you a remake, a refund, and a customer who will not call back, which is worse than the call you simply missed.
Here is what the connection does, the way it usually fails, and what to test before you commit.
How the order gets from the call into SpotOn
X1 Voice reaches SpotOn through Deliverect, the middleware many restaurants already run to pull third-party orders into their POS. The agent reads your live SpotOn menu with its modifiers and prices, holds the conversation against that menu, and writes the finished order back as a ticket that fires the way your other digital orders fire.
The round trip is the whole value. A system that sounds human and then hands a staff member a transcript to key in during a rush has relocated the work rather than removed it, which is the argument laid out in why POS integration depth matters more than voice quality. Ask any vendor to show you the ticket, not the conversation.
If you want the step-by-step of what the route looks like in practice, the SpotOn voice order flow walks it end to end.
What it changes on a real shift
Not silence. The end of triage.
Take 6:30 on a Friday. Your host is seating a table, two guests are waiting to be greeted, and the phone rings three times inside two minutes. Today one of those calls gets answered, badly, while a guest stands there. The other two hear ringing and call somewhere else.
With an agent on the line, all three are picked up immediately. Two pickup orders write into SpotOn with times attached. The third caller asks about parking and gets the answer you configured, and if you never configured one, it escalates to the host as a single interruption instead of three.
The labor effect is real and modest. Multiply your calls per shift by your honest average handle time and you get the floor minutes returned. Use your own numbers. The version on a vendor slide is almost always generous.
Decide the handoff before you go live
This is the setting operators skip and later regret. Complaints, large catering inquiries, and any caller who asks twice for a person should reach a person, and the agent should hand off cleanly rather than trying one more clarifying question. Those are policy choices you make, not limits you discover in a bad review. Human handoff and failover covers how to write the rules and, just as important, how to confirm the escalation rings somewhere a human will actually hear it mid-rush.
The failure mode: the menu drifts
Everything matches on day one because you just imported it. Six weeks later it does not.
The kitchen 86s the special every Saturday by eight. A limited-time item goes into SpotOn under a name no caller would ever say out loud. A price moves on the register and the phone quote stays where it was. None of that raises an error anywhere. It shows up as a customer arriving for food you cannot make, or a small tax discrepancy at close that nobody wants to chase down.
The fix is procedural. Whoever owns the SpotOn menu owns the phone menu, and every menu change earns a test call the same week. The specific ways sync goes sideways are catalogued in POS 86 sync failure modes, and it is worth twenty minutes before you go live.
Payment on the call
Callers can pay by card while they are still on the phone for pickup and delivery, and the payment reconciles alongside your other tender types, so end-of-day close does not sprout a new manual pile.
The underrated benefit is what stops happening. No digits read aloud at a counter, no card number written on a ticket sitting by the register until close, no staff member holding a stranger's payment details in their head. That path is gone.
The numbers to check in the first month
Four, in order of how much they should influence you.
Answered-call rate moves immediately and is the reason you bought this. Order accuracy matters most, and the only credible way to measure it is pulling twenty phone tickets and checking them against transcripts rather than reading a dashboard. Escalation reasons are your work list once you sort them into handoffs that were correct by design and handoffs that were defects. Average phone ticket tells you whether the agent's prompts do anything, and it is the number most easily flattered by a small sample.
If accuracy holds and answered-call rate goes from something like 70 percent to near 100, the system is doing its job. If accuracy slipped, stop everything else and fix the menu.
One trap in that first month is counting every phone order as new revenue. Some share of it is volume you were already capturing, just through a different door, and reading the lift honestly means separating the two. Attribution between phone and online orders covers how to set that up so the month-two review is a real number instead of a flattering one.
Setup, realistically
Connecting takes minutes. Being ready to go live takes about a day.
You link SpotOn through Deliverect, import the menu, set hours and phone-only rules, run test calls including one deliberately awkward order, then forward your number. Most single locations are live inside 24 hours, and our team will handle the menu pass if you would rather not. Plans start at $250 per month.
Mixed estates are fine. X1 Voice connects directly to Square, Clover and OrderCounter and reaches SpotOn, Toast, Lightspeed, TouchBistro, Aloha, Revel, PAR Brink and Micros through Deliverect, so locations on different systems can run the same phone experience. The current list lives on the integrations page.
The test that settles it
Call the demo line, from us or any vendor, and place the worst order your kitchen sees. No onions, sub the fries, add a drink, apply the promo, then change your mind about the size. Look at the ticket that comes out.
If the ticket is right, the rest is tuning. If the voice repeated your order back perfectly and the ticket is wrong, no amount of onboarding will fix that, and you learned it in five minutes rather than over a season of comps.