If you run OrderCounter, one question decides whether a voice agent is worth buying: does a finished phone order land in OrderCounter as a correct ticket, priced the way your register would have priced it? Voice quality is what every demo leads with and the least useful thing to judge. An agent that sounds excellent and drops a modifier costs you more than an unanswered ring, because you make the food twice and the person on the other end was already a customer.
X1 Voice connects to OrderCounter directly. It reads your live menu, prices each phone order the way the register does, and drops the finished ticket back in as a normal order. Nobody re-types anything at the counter.
The direct part is worth a paragraph, because it is the main practical difference between this integration and most of the others.
What a direct connection changes
Most voice vendors reach most POS systems through a middleware layer, usually because building and maintaining a direct connection per POS is expensive. That routing works, and it costs you two things.
It costs you a publishing step. On a routed integration, your menu has to be published into the middleware before the agent can read it, and it has to stay published as the menu changes. Direct means one fewer system holding a copy of your menu, and one fewer place for the copies to disagree.
It costs you time on availability. Routed connections sync on a cadence. Direct connections do not have that extra hop, so a change on your side reaches the agent faster. On a Saturday at seven, when the wings run out, that gap is the difference between the phone selling something you don't have and the phone declining it. It is the detail most operators skip in an evaluation and the one they most often regret skipping.
None of that makes a direct integration automatically better than a routed one for your restaurant. It does mean the questions you should ask are different, and it means one less thing to keep in sync. The OrderCounter integration page has the current specifics, and OrderCounter menu sync tips covers the configuration details that make imports come across cleanly.
What it looks like on a real shift
It's 6:45 on a Friday. Two lines are ringing, the counter is four deep, and somebody wants to know whether the sauce has dairy in it.
The agent answers on the second ring, takes a pickup order with a substitution and a hold, charges the card, and the ticket prints at expo with the modifier attached. Nobody behind the counter looked up.
A second caller asks about catering for thirty on Sunday. The agent doesn't attempt it. It captures the name, number, headcount and date, transfers if a manager is on the floor, and leaves a transcript if not. That behavior is a configuration decision rather than a capability, and it is the one worth checking in a demo. Human handoff and failover covers how to write the rules so the agent gives up on exactly the calls you want a person taking.
The gain shows up in calls you currently have no record of, which is why most operators underestimate their own miss rate. A phone ringing out during a rush leaves no trace. Count the calls you miss in a typical week, multiply by your average ticket, and check whether the problem is as small as it feels before you decide it isn't worth solving.
The failure mode nobody puts in a demo
Modifier structure, and it is worth being blunt about it.
Menus grow by accretion. Somebody adds a half-and-half option to one item and not its sibling. Somebody builds three sizes as three separate items rather than a size group. A required modifier group carries a default that only makes sense with a person standing at the screen. None of that hurts you today, because the employee ringing it in knows what the buttons mean and works around the structure without thinking.
An agent has no such judgment. It follows the structure literally, so it will either refuse a combination that is obviously fine or fire a ticket that validates and is wrong at the pass.
The fix is structural rather than conversational, and for most menus it is a couple of hours of one-time work. Simplifying modifier trees covers the shapes that break.
So test for it before you buy. Ask the vendor to take a deliberately awkward order on your real menu: "large, half one way half the other, no onions on the second half, sub the side, add a drink, apply the promo." Then walk to the printer and read the ticket. Do not accept the agent repeating the order back correctly as evidence, because the repeat-back and the injected ticket are two different systems and only one of them feeds the kitchen.
The numbers to pull after a month
Four, and they take about twenty minutes.
Answered-call rate, which should approach 100 percent and is the reason you bought it. Order accuracy, measured by reading a sample of phone tickets against their transcripts rather than trusting a dashboard, using the order accuracy measurement method. Escalation reasons, sorted into "by design" and "by defect," where only the defect bucket is a to-do list. And phone revenue against the same weeks before you turned it on.
If answered calls went up and phone revenue did not, the agent is absorbing calls staff were already picking up. That still buys back labor, but it is a different case than incremental revenue, and you should know which one you are actually making.
What setup costs you in time
The connection is minutes. Reviewing what came across is the part that takes attention.
Plan on someone sitting with the imported menu once, reading item names aloud, and fixing the ones that sound like database fields. Set your hours, delivery zones if you deliver, and any phone-only rules such as a delivery minimum. Then place five or six test calls yourself, ordering the way your regulars talk rather than the way the menu is written. Most single locations are live inside a day, and plans start at $250 a month, which you can size against your own call volume on the pricing page.
If you run OrderCounter at some locations and something else at others, that is not a blocker. X1 Voice also connects directly to Square and Clover, and reaches Toast, Lightspeed, TouchBistro, SpotOn, Aloha, Revel, PAR Brink, Micros and others through Deliverect, so a mixed estate runs on one agent configuration.
The decision rule is small enough to run this week. Place five hard test calls on your own menu, walk to the printer each time, and count how many produced a ticket you would have been glad to see a new hire ring in. Five means the integration is doing its job. Three means the problem is almost certainly your modifier structure rather than the voice, and that is worth fixing before you sign anything.