Choosing an AI call center vendor: a demo checklist

The short answer

When you choose an AI call center vendor in a demo, the main rule is this: look for evidence on your own calls, not a prepared presentation. Six areas need checking — language and speech, scenario and knowledge, handoff to a human, telephony, data and privacy, and pilot terms. One or two questions per area are enough, but for every answer you should be able to say "show me".

The checklist below is meant to be printed and taken to the demo. Next to each question, write "showed", "said but did not show" or "not available". At the end it becomes easy to compare two or three vendors in one table.

Preparing before the demo

• A short description of your 5–7 most frequent call types, with real example questions for each
• 3–5 test scenarios without names or personal data: a simple question, two questions in one sentence, a request for a human, an unclear answer
• Your current telephony: carrier, PBX type, number of lines
• The list of fields that must appear in the CRM after a call
• Who makes the decision: operations, IT, legal, finance

1. Language and speech

1. 1Which languages does it speak, and how is the language chosen?Per number, per scenario, or within the call? Ask for a live call in your own language during the demo.
2. 2How does it say and hear numbers, addresses and proper names?Test with a phone number, an amount and a street name.
3. 3Is there a choice of voice?Can you pick a voice that fits your brand, and how long does changing it take?

2. Scenario and knowledge

1. 1Who writes the scenario, and how is it changed?Can your team change it in the panel, or does every change go through the vendor?
2. 2Where do the answers come from?Knowledge base, document upload, website; how an outdated answer is updated.
3. 3What does it do with a question it does not know?Does it make something up, say "we will confirm and get back to you", or hand over? Check with a test scenario.
4. 4What information does it extract from the call?Can you define the fields, and how does a field that was not found appear?

3. Handoff to a human

1. 1In which cases does it hand over?The caller's request, a difficult question, a topic listed in the rules.
2. 2What does the operator see when taking the call?A summary, the details collected, the customer's history.
3. 3What happens if the operator does not answer?A queue, another number, a note and a callback — is there a fallback?

4. Telephony

1. 1Do we keep our existing number?How it connects: SIP trunk, PBX or a local carrier.
2. 2How many calls at once?How the parallel-call limit is set, and what happens when it is exceeded.
3. 3How do we find out when the line drops?Registration status, alerts, a fallback route.
4. 4Which call goes where?Rules such as business hours, number and a VIP list, and whether you can test them before they go live.

5. Data and privacy

1. 1Where are recordings and transcripts stored?Country, provider, retention period, deletion process.
2. 2Who has access?Roles in your team, and support access on the vendor side.
3. 3Is your data used to train the model?Ask for a written answer.
4. 4How is the recording notice at the start of the call set up?Can you change the wording?

If you hear a claim about a certification or compliance, ask for the document. A vendor does not ensure legal compliance on your behalf — it only provides the tools; check the requirements with your own lawyer.

6. Pilot terms

1. 1How long is the pilot and what does it cover?One call type, one line, set hours.
2. 2Who measures the success criterion, and how?Which reports exist, and can raw data be exported?
3. 3What happens if the pilot stops?Return and deletion of data, contractual obligations.

How to run the live test calls

Make the test calls from an ordinary mobile phone, not from the vendor's laptop — that is how your customers call. Run at least one call from a noisy place and one with someone who speaks fast and changes their mind half-way through. During the call one person talks while a second notes accuracy, delay, and whether the agent had to ask the question again.

Right after the call, look at what was left in the panel: does the transcript match what was said, are the extracted fields correct, did missing information stay empty or was it made up? This five-minute check tells you more than any slide in the presentation.

References

Ask the vendor for a conversation with one or two customers close to your sector and language. Ask them three questions: how long it took to go from pilot to full use, what problem came up in the first month and who solved it, and who changes the scenario today. If no reference can be given, that is not necessarily a bad sign, but it is a reason to write stricter pilot terms.

Red flags

• The demo shows only pre-recorded calls and live testing is not allowed
• A figure like "99% accuracy" is quoted without explaining how it was measured
• Handoff to a human is presented as a feature coming "soon"
• Every scenario change requires a request to the vendor
• The question of where data is stored gets a vague answer

The comparison table

For each vendor, put the six areas in rows and three statuses in columns: showed, said, not available. "Said" is closer to "not available" — do not rely on it until the pilot proves it. Put price in a separate row and break it down per call minute, per month and for initial set-up; that lets you compare different pricing models.

Limits

A demo is at best a short test; real load, audio quality and customers' unexpected questions only show up in a pilot. This checklist is based on industry practice and does not replace the specific requirements of each sector — healthcare, finance and the public sector need additional checks.

What you can check in a Vexvon demo

In a Vexvon AI Call Center demo you can see these answers in the panel itself: connecting to your existing SIP or PBX line (AzInTelecom, Twilio, on-premise PBX) and the line's live registration status; the scenario — what the agent will say and which fields it extracts; a choice of eight AI voices; the knowledge base shared with the chatbot; priority routing rules and their simulator; handoff to a live operator; and each call's transcript, summary and recording. The conversation language is set in the scenario.

Choosing calls for the pilot is covered in the selection matrix, the economics in voice AI ROI, and the comparison with IVR in this article.

First step

Before the demo, write five test scenarios and give every vendor the same ones. Record the results in the six-area table. More articles are in the voice agent strategy section; to run a Vexvon demo on your own line, get in touch.