Voice AI: why most POCs never reach production.
In Voice AI, the POC almost never dies on the model. It fails on data, governance, and integration — precisely where production begins.
The problem is not model performance in a demonstration. The problem is the move to the real world, with messy flows, unclear rules, and systems already in place. A POC that ignores this proves nothing. It only shows that an idea can impress for twenty minutes. As soon as it must absorb incomplete calls, silences, varied accents, and security constraints, the demo curve loses its value. The real question is not "does it work?" It is "does it hold when everything chains together?"
Data decides before the model
In Voice AI, transcript quality, latency, and access to the right contexts make the difference. A model that shines on a clean corpus degrades fast on real calls. Accents, overlapping speech, noise, silences, and domain terms break the promise. Audio data is not an input detail. It sets the quality ceiling, and the model merely composes within that ceiling. If the signal is unstable, the best architecture primarily produces coherent errors — therefore hard to spot early.
Start by examining the audio source, conversation segmentation, and metadata availability. Ask whether the architecture consumes the real-time stream or a delayed file. Ask the loss rate on short segments and interruptions. If the vendor cannot measure this, they cannot industrialise. Ask this exact question: "What is your recognition rate on raw calls, without manual cleaning, over the last five days?" Require a verifiable criterion: same test set, same channels, same codec, same network conditions. Classic trap: hidden manual cleaning inside the POC. Everything looks smooth because a team corrects difficult cases by hand. In production, that safety net disappears and error rate spikes, often on short calls, proper nouns, and urgent requests.
Governance blocks more often than AI
The real subject is knowing who authorises what, and when. In production, a voice recommendation may commit a refund, a complaint, or an escalation. Without validation rules, the system becomes either overly cautious or dangerous. In both cases, it gets rejected. Governance is not legal packaging. It is the mechanism that converts a probable response into an acceptable action. As soon as an intent touches the customer, risk, or money, you need to know who decides, who blocks, and who takes responsibility.
Always ask for the complete decision chain. Who validates sensitive intents? Who arbitrates ambiguous responses? Who holds the business veto right? If the answer fits in a vague sentence, the POC is not ready for a regulated environment. Ask in the meeting: "At what exact moment does the machine stop — and who takes over?" Require a contractual criterion: every sensitive intent must have an explicit validation authority identified before production launch.
Integration is where most POCs die
The POC ran on a controlled data extract. Production runs on a live system, with a real CRM that has its own update rhythm, a recording infrastructure that has its own access rules, and a telephony that has its own codec constraints. Connecting the model to these systems is never a weekend's work.
The problem is systemic. Each integration adds latency, failure modes, and maintenance dependencies. An API that works perfectly during the POC can behave differently under production load. A CRM field that was reliable in the test dataset can be absent or malformed in 15% of real cases. These gaps do not appear in controlled demos. They appear the first Monday morning after launch, when traffic is real and the team is not expecting it.
Map the integrations before judging the model. Ask: "What are all the external systems the model calls during a conversation, and what is the timeout if one of them does not respond?" Require an integration test on production-representative data — not cleaned samples. Check how context is rebuilt if a system is temporarily unavailable. A model that depends on a single source of truth that is sometimes slow or absent will produce inconsistent experiences at exactly the moments when reliability matters most.
THE AUTHOR
Yassine Rogui
President of ExpertiaX. 19+ years in contact centres. Formerly Orange Business, NTT DATA. Writes in French, sometimes in English, never in jargon.
LEARN MORE ABOUT YASSINE →TO GO FURTHER
Receive the full checklist
The PDF summarising this article and the other 11 pitfalls. 6 pages.