Most restaurant operators read a software contract once, skim the parts that look like boilerplate, and sign. That's understandable — the document is long, the language is unfamiliar, and the vendor is friendly. But a handful of clauses in voice AI agreements have real operational teeth, and they're almost always negotiable if you raise them before signing rather than after.
The terms worth your attention fall into four groups: how you get out, what happens to your data, what the price actually does over time, and who is responsible when something breaks. None of these are exotic legal traps. They're ordinary commercial terms that happen to matter more than they look.
Auto-renewal with a narrow notice window
This is the one that catches the most people. The structure is simple: a twelve-month term that renews automatically for another twelve months unless you give written notice within a specific window, often thirty days before the anniversary.
The problem isn't the renewal, it's the window. Thirty days is short, restaurant owners are busy, and the anniversary of a contract you signed a year ago is not something you're tracking. Miss it and you've committed to another full year of a product you may have already decided against.
What to ask for: a longer notice window (sixty or ninety days), a calendar reminder obligation on the vendor's side, or month-to-month renewal after the initial term rather than another full year. The last one is the cleanest and vendors grant it more often than you'd think, because by month thirteen they'd rather keep you happy than locked.
Data and recordings you can't take with you
Your call transcripts, order history, and customer records are business records. Whether you can leave with them is a contract question, not a technical one.
Ask what happens to your data on termination. Specifically: can you export transcripts and order history in a usable format, is there a fee for that export, how long does the vendor retain your data after you cancel, and can you require deletion. A vendor that will only provide a dashboard view and no export is holding something that belongs to you.
This overlaps with a broader set of questions about who owns what and how call recordings are handled, which we cover in voice AI data ownership and privacy. The contract is where the answers become binding.
Per-location fees that appear at store two
If there's any chance you open a second location, get the multi-location terms in writing now, while you're still a prospect they want.
The questions: is the price per location or per account, does a second location get the same rate or a new one, are included minutes pooled across locations or siloed per store, and does adding a location restart the contract term? That last one matters. Some agreements treat each new location as a fresh twelve-month commitment, which means a growing operator is never actually out of contract.
Franchise and small-group operators should push harder here — the shape of a rollout changes the economics substantially, which is why we treat it as its own topic in the franchise rollout playbook.
Price escalators and "then-current rates"
Look for two phrases. "Then-current rates" means the vendor can reprice you at renewal to whatever the list price is at that time, with no cap. An "annual escalator" means a specified percentage increase each year, which is at least predictable.
A specified escalator is a normal term. An uncapped "then-current rates" clause on an auto-renewing agreement is the combination worth pushing on, because it's a renewal you didn't actively choose at a price you didn't agree to. Ask for a cap, or ask for the right to terminate without penalty if the renewal price increases by more than some amount.
Vague uptime language with no remedy
"Commercially reasonable efforts" to maintain availability is not a service level. It's a description of intent. A real SLA states a target, defines how uptime is measured, defines what counts as an outage, and specifies what you get when the target is missed.
For a restaurant, the remedy conversation is a little unusual. Service credits are the standard remedy in software, but a credit worth a fraction of a monthly fee does not compensate for a Friday dinner rush where nobody answered the phone. That doesn't mean you'll get something better, but it does mean you should read the outage-handling terms — what happens to calls during an outage — as the more important clause. We go through that in voice AI SLAs and uptime for restaurants.
Fees that live outside the price page
Ask for a complete fee schedule, not a plan comparison. Onboarding and setup fees, menu-import fees, fees for menu changes after go-live, number-porting charges, SMS charges passed through to you, integration fees for your POS, and support tiers that cost extra. Each of these can be entirely reasonable. None should surprise you in month two.
Then ask the question that flushes out the rest: "Is there anything I could be billed for that we haven't discussed?" It's a fair question and the answer tells you about the vendor as much as about the fees.
Exclusivity and restrictions on your own phone number
Occasionally an agreement will restrict what you can do with your phone number or require that all inbound calls route exclusively through the vendor. Be careful here. Your main line is a core business asset. You want the unambiguous right to port it out, and you want the ability to route some call types elsewhere if you choose. Number portability is a regulated right in the US, but the contractual friction around it can still be real, which is why we wrote a phone number porting guide.
What a reasonable agreement looks like
Not every contract needs to be month-to-month to be fair. A reasonable voice AI agreement generally has: a real trial or pilot on live calls before commitment, a defined and exportable data set that you own, a notice window long enough that a busy operator can actually hit it, published fees with no undisclosed line items, and clear language about what happens to calls when the system is unavailable.
If you get those five, term length matters much less. If you don't get them, a short term is protection against the rest.
The bottom line
Read the exit terms, the data terms, and the fee schedule before you read the feature list. The features are what you're buying; those three sections are what you're actually agreeing to. Ask for the changes you want while you're still the one deciding — the leverage is entirely on your side of the table right up until you sign, and entirely on theirs afterward. Bring the diligence questions from our buyer's checklist to the same conversation and you'll cover most of the ground in one pass.