TL;DR: A voice agent can capture and confirm a caller's number correctly and still lose the lead. Production workflows need validation, confirmation through SMS or WhatsApp, and an alternative contact path when critical details cannot be verified.
A voice agent can sound natural and still lose the lead.
Piotr's GPT-Live-1 test raised an important point about entity capture: names, addresses and phone numbers have to survive the conversation accurately.
This weekend, my voice agent answered a call from a South African hairdresser.
She wanted help answering calls while busy with clients, including calls involving complaints.
The agent captured her callback number, read it back, and received confirmation.
But when I tried the number, it did not exist.
I listened to the recording. The stored number matched what the caller said and confirmed. I cannot know whether she supplied the wrong number intentionally or made an honest mistake.
The model did what we asked. The workflow still failed.
The problem was not transcription. It was relying on one piece of contact information with no recovery path.
A production workflow needs more than read-back confirmation:
capture → validate → confirm through SMS or WhatsApp → request an alternative when confirmation fails
Natural conversation earns attention.
A recoverable handoff protects the business outcome.
What fallback does your voice workflow use when critical contact information cannot be verified?
Patrick Michael
-----------
If you find this content useful, please share it with this link: [https://patrickmichael.co.za/subscribe](https://patrickmichael.co.za/subscribe)