The monthly number on a voice AI quote is the part of the price that is easiest to compare, which is exactly why vendors compete on it. The rest of the cost lives in the sections of the agreement nobody reads until the third invoice.
None of this is unique to voice AI. It is how software gets sold. But restaurants sign these agreements with a specific handicap: call volume is seasonal, menus change constantly, and the person signing usually has no way to predict either as a number. That combination is what makes the extras land harder here than in most categories.
Setup and onboarding, and what "included" covers
A setup fee is defensible. Someone has to build your menu into the system, connect it to your POS, sort out delivery zones and hours, and test the whole thing against real calls. That is genuine work.
The question is not whether there is a fee. It is what the fee buys and where it stops. Ask specifically: if the menu build has errors, are corrections included? For how long? A vendor who charges for setup and then charges again to fix their own build has designed a fee that grows the worse their work is.
Ask the same about the POS connection. If your system needs middleware to reach the register, find out who pays for it, whether that is a one-time or recurring charge, and whether it appears on their invoice or someone else's. X1 Voice connects directly to Square, Clover, and OrderCounter, and reaches Toast, Lightspeed, TouchBistro, SpotOn, Aloha, Revel, PAR Brink, and Micros through Deliverect, all of which is laid out on the integrations page. Which path your POS falls on is worth knowing before you budget, because the two are not the same amount of moving parts.
Menu change fees are the one that surprises people
This is the cost operators underestimate most consistently, because it does not scale with anything they are used to thinking about.
If you run a fixed menu that changes twice a year, a per-change fee is a rounding error. If you run weekly specials, a rotating soup, seasonal produce, and a chef who eighty-sixes things by feel, a per-change fee is a monthly line item that has no relationship to how many calls you took.
Three things to establish before signing. What counts as a change: is adding a special the same as restructuring a category? Can your manager make edits directly, or does every change go through a support ticket? And how fast do edits go live, because a menu update that takes three business days is a menu update you will stop making. The operational side of that is covered in keeping your menu in sync.
The best answer here is self-service editing at no charge, with the vendor handling only structural work. If a vendor cannot offer that, the fee schedule needs to be small enough that you will not start avoiding menu accuracy to save money. That is a real failure mode. A restaurant with a stale menu in the phone system loses more to wrong orders than it ever saved on edit fees.
Overage, and what a billable minute actually is
Most plans include a bundle of calls or minutes. Beyond the bundle, you pay per unit, and the per-unit rate is almost always well above the effective in-plan rate.
Take the arithmetic seriously. Pull your busiest month from your phone records. If you took 2,000 calls in December against a 1,200-call plan, 800 calls bill at overage. At a dollar a call that is $800 on top of your base. At three dollars a call it is $2,400, and your December bill exceeds your entire first quarter. Run that multiplication before you sign, not after.
Then ask what a billable unit is. Does a fifteen-second wrong number count as a call? Does a call that transfers to a human count once or twice? Is a minute rounded up per call, which on short calls can inflate a bill substantially? The differences between per-minute and per-call structures are laid out in per-minute versus per-call pricing math, and they matter more for restaurants than for most businesses because restaurant calls are short and numerous.
X1 Voice plans start at $250/month. Whatever vendor you are evaluating, ask them to quote your worst month, not your average one.
Terms, minimums, and the auto-renewal clause
Annual commitments are fine when the discount is real. They are a problem when the term is long, the notice window for cancelling is short, and the renewal is automatic.
The pattern to look for: a twelve-month term that renews automatically unless you give written notice thirty or sixty days before the end. Miss that window by a week and you have bought another year. Put the notice date in your calendar the day you sign. Not the renewal date, the notice date, with a two-week buffer in front of it.
Minimums deserve the same scrutiny. A minimum monthly spend means a slow February costs the same as a busy December, which is the opposite of how a restaurant would prefer to buy anything. If you are seasonal, say so during negotiation and ask what flexes.
Broader contract language worth reading closely, including data ownership and what happens to your call recordings when you leave, is covered in voice AI contract terms to avoid.
Build the annual number, then compare
The only honest comparison between two quotes is an expected annual total built from your own numbers.
- Setup fee, plus any charge to connect your specific POS
- Monthly base times twelve
- Expected overage, calculated from your three busiest months rather than your average
- Menu change fees at your actual change frequency, which is probably higher than you think
- Any middleware, telephony, or number-porting charge that appears on a separate invoice
Do that for both vendors and the ranking often reverses. A $250 base with self-service menu editing and generous call bundles frequently beats a $180 base with per-change fees and tight overage. The monthly headline is the least informative number in the agreement. Slotting the result into a full-year budget is the subject of budgeting for voice AI month by month.
The question that surfaces everything
Ask for a sample invoice from a restaurant of roughly your size and volume, with the name redacted.
A vendor with clean pricing will send one, or walk you through a line-by-line mock invoice using your numbers. A vendor who deflects to the quote sheet is telling you the quote sheet is not what the invoice looks like. That single request will tell you more about a contract than an hour of reading it, and it takes one email.