Phone orders are still a real slice of revenue for most restaurants, and if you run Clover, the only question that matters about a voice agent is simple: does the order end up in Clover correctly? A great-sounding voice that drops a modifier or sends the kitchen the wrong ticket is worse than a missed call.
Here's how X1 Voice works with Clover, where these setups actually go wrong, and what to check before you buy.
The order has to land in Clover, cleanly
X1 Voice connects directly to Clover. It reads your live Clover menu, prices every phone order the way your register already prices it, and drops the finished ticket back into Clover as a normal order. Nobody re-keys anything. The value is in the round trip: reading the live menu and firing a correctly-modified ticket, not just sounding human on the call.
The one thing to test with any vendor, Clover or otherwise, is a deliberately awkward order. Try "no onions, sub fries, add a drink, apply the coupon" and confirm it arrives in the POS right, not just that the voice repeated it back. Repeating the order correctly and writing the order correctly are two different jobs, and only one of them shows up at the pass.
What it looks like on a Friday at 7:15
The practical difference is not on the call, it's at the expo window twenty minutes later.
Today, a phone order at peak goes like this: someone leaves the register, takes the call on a cordless handset, writes on a pad, then walks back and re-keys it into Clover between walk-in customers. Two transcription steps, both done while someone is being asked a question. With the connection running, the ticket prints itself while the caller is still on the line, and the person who used to take the phone stays at the counter.
The second change is quieter. Your Clover ticket now carries the same modifier text your kitchen already reads, because it came out of your own catalog rather than from a note. That matters more than the labor saving on nights when the difference between a remake and a clean plate is one word.
Where Clover setups actually break
Almost never at the connection. Nearly always in the catalog.
Clover catalogs get built by whoever set the store up, and item names are written to be tapped, not spoken. A button labeled "LG 2TOP" is unambiguous on a screen and useless on a phone call. Modifier groups are the other common trouble spot: a group with a required minimum of one that nobody ever notices on the register becomes a question the agent has to ask every single caller, and it will, until you fix the group.
Three things worth auditing before you go live, and each takes a few minutes:
- Item names a caller would say out loud, with the register abbreviation kept as an alias rather than as the name.
- Modifier groups with a required selection that should really be optional, or a default that was never set.
- Duplicate items left over from an old menu, still active in the catalog, still priced from two seasons ago.
We go deeper on the naming half of this in menu naming for voice clarity, and on the modifier half in how voice AI handles menu modifiers. If your catalog is clean, setup is genuinely a same-day job. If it has five years of accumulated buttons in it, the catalog cleanup is the project, and it would have been worth doing anyway.
Payments and reporting
Callers can pay by card on the phone for pickup and delivery. That payment reconciles alongside your other tender types, so your end-of-day numbers stay in one place. Staff never read a card number out loud or write one down, which removes the pad of paper by the phone that was always the weakest link in the room.
You can also keep pay-at-pickup for phone orders and use card-on-call only for delivery, or the reverse. Most operators land on taking payment up front for delivery and anything over a set dollar amount, because those are the tickets that hurt when nobody shows. The phone payment safety walkthrough covers how the card data is handled and what it means for your own scope.
Setup, and what actually takes the time
Connecting Clover takes minutes: link your account, import the catalog, set your hours and any phone-only rules, run a test call, and go live. Most single-location restaurants are live the same day, and our team can handle white-glove setup if you'd rather.
What takes longer than people expect is the decision list, not the wiring. Which calls should always reach a person. Whether phone orders get a pickup window quote or a flat "20 minutes." What the agent says when someone asks for the manager. None of that is technical, and all of it is worth ten minutes of thought before the first live call rather than after the first awkward one. The onboarding checklist is the version of this list we hand to new locations.
If you run more than Clover across locations, that's fine too. X1 Voice reaches 80+ POS systems, directly or through Deliverect, so a mixed estate isn't a blocker.
The numbers to check in your first two weeks
Four, and all of them come out of your own reporting rather than a vendor dashboard.
Answered-call rate, compared against the same weekdays before you switched. Order accuracy, measured by pulling twenty phone tickets and checking them against the recordings rather than by trusting a percentage. Average phone ticket, segmented by channel so you're reading the phone specifically. And the count of orders that reached Clover but needed a staff correction before they fired, which is the one number that tells you whether your catalog cleanup was thorough enough.
That last one should trend toward zero in the first fortnight. If it doesn't, the fix is almost always a specific item or modifier group, and it's cheap to fix once you know which one. Sample tickets at random across dayparts rather than reading the ones a manager flagged, or the number will only tell you what you already knew.
The decision rule
Run a week with the connection live and count two things: phone calls answered, and phone tickets that reached the kitchen without anyone retyping them. If those two numbers are both close to your total inbound volume, the integration is doing its job and the remaining questions are about pricing and call handling, not about Clover. If either one lags, the cause is in your catalog, and you can see exactly which items are responsible before you decide whether to keep going. Details on the connection itself are on the Clover integration page.