8 Questions to Ask an AI Receptionist Vendor Before You Sign

Before you sign with an AI receptionist vendor, get written answers to eight things: what the total bill looks like in your busiest month, whether booking is included in the tier you are quoted, contract length and cancellation terms, how the AI is disclosed to callers, how call recording consent is handled by state, what happens when the AI cannot help, which systems it actually writes to, and who owns your call data. Most bad outcomes in this category trace back to one of those eight going unasked.

The demo is not where deals go wrong. Demos are good now across most of the category, because the underlying voice technology is genuinely capable and every vendor has a polished script. Deals go wrong two months later, when the bill is double what you expected, or you discover booking was a higher tier, or you want out and there are ten months left on an annual contract. Here is the list to work through before you sign anything.

1. What does the bill look like in my busiest month?

Do not ask what it costs. Ask what it costs in the month everything goes wrong. Pricing in this category comes in three shapes and they behave very differently under load.

• Per minute. The traditional answering service model, roughly $1 to $2 a minute, higher on nights and weekends in most contracts. The bill rises exactly when you are busiest.
• Minute buckets. A monthly allowance with an overage rate. The headline price is attractive; the overage rate is where the real cost lives. Ask for it in writing.
• Flat monthly. One fee regardless of volume. Predictable, and the busy month costs the same as the quiet one.

Give the vendor your actual numbers: calls per month, average call length, share after hours. Ask them to price that. If they will not put a figure against your real volume, that is information too. Also ask about setup fees and per-location charges, which are common and rarely mentioned unprompted.

2. Is booking included in the tier you are quoting me?

This is the single most common surprise in the category. Several vendors include calendar booking only from a middle or upper tier, so the entry price you were quoted buys a service that takes messages. If the whole reason you are buying is to stop calling people back, a message-only plan hands the work straight back to you.

Ask it precisely: in the specific plan you are quoting me, does the AI check live availability and write the appointment into my calendar during the call? Not "does the product support booking." Products support lots of things. You are buying one tier.

3. How long is the contract, and how do I leave?

Annual contracts are standard at the platform end of this market and unusual at the small-business end. Neither is wrong, but you should know which you are signing. Ask for the contract length, the notice period, whether it auto-renews, and what happens to your phone number and call history if you leave.

That last part matters more than people expect. If you forwarded your main business line, you want a clear, written answer about unwinding that cleanly. A vendor who cannot describe their offboarding in two sentences has probably not thought about it, which tells you something.

4. How is the AI disclosed to my callers?

Ask whether the AI identifies itself as an AI, and when. A good vendor discloses in the first sentence of the call as a matter of policy. Some let you turn disclosure off, which is worth thinking hard about before you use it.

There is a compliance dimension: several US states have moved to require disclosure when a consumer is interacting with an automated system, and the direction of travel is clear. There is also a plain trust dimension. Callers who are told up front tend to rate the interaction better than callers who work it out halfway through and feel misled. Disclosure is not the weakness vendors sometimes treat it as.

5. How is call recording consent handled?

Recording consent in the US is state by state. Roughly a dozen states require all parties to consent, and the rest require one. If you take calls from more than one state, and almost everyone does, you need to know whether the system handles that automatically or whether you are expected to configure it.

Ask specifically whether recording consent is applied based on the caller's state, and what the caller hears. Then ask where recordings and transcripts are stored and for how long. We go through the underlying rules in our guide to call recording consent laws.

6. What happens when the AI cannot help?

Every AI receptionist will meet a call it should not handle: a genuine emergency, a furious customer, something legally sensitive, something simply strange. What the system does at that moment is a bigger quality signal than anything in the demo.

Ask what triggers a handoff, whether you can define your own escalation rules in your own words, whether it warm-transfers to a live person or takes a detailed message, and what happens if nobody picks up the transfer. A vendor with real answers here has been running production traffic for a while. A vendor who says the AI handles everything has not.

7. What does it actually write to, and how?

Integrations are the most oversold part of every demo. There is a large difference between a vendor that writes appointments directly into your scheduling system and one that emails you a summary you retype. Both get described as "integrates with your calendar."

Name your systems out loud, your practice management software, your scheduler, your CRM, and ask three questions about each: does it write, or only read? Is it native, or through a middleware connector you would also pay for? Is that integration live today, or on a roadmap? Ask to see it happen in the demo against a test calendar rather than a slide.

8. Who owns the call data, and how is it protected?

Your call recordings and transcripts contain customer names, phone numbers, addresses and sometimes health or financial details. Ask who owns that data, whether it is used to train models, whether it is shared with subprocessors, how long it is retained and whether you can delete it on request.

If you are in a regulated field, push further. Healthcare practices should ask directly whether the vendor will sign a business associate agreement, since an answering service handling patient information is squarely within HIPAA's scope. The same discipline applies to how any AI system in your business is permitted to access tools and data on your behalf, which is worth settling before a vendor is wired into your calendar and your customer records rather than after.

Two things to do during the demo itself

First, call it yourself, from your own phone, without the salesperson steering. Interrupt it mid-sentence. Change your mind about the appointment time. Ask something slightly off script, like whether you can bring a second person. Mumble a bit. You are not trying to break it; you are checking that it recovers gracefully, which is what your real callers will do to it on day one.

Second, ask for a reference in your industry and roughly your size. A dental practice and a plumbing company put very different demands on the same product. A vendor with real customers can produce one.

Putting it together

Get the answers in writing, in email, before you sign. Not because you expect to litigate them, but because the act of asking a vendor to commit in writing to their overage rate, their booking tier and their offboarding terms surfaces the soft answers fast.

If you are still assembling a shortlist rather than negotiating with one vendor, we compare the main options on these exact terms, including where each competitor is genuinely the better choice, in our roundup of the best AI receptionist tools. And if the underlying question is whether you want AI or a human service at all, AI receptionist vs answering service works through that decision first.

The pattern behind all eight questions is the same. Vendors compete on the demo, but you live with the contract, the bill and the escalation path. Spend your diligence there.