Powsoo / Guides / Add tap-to-confirm to a Vapi AI voice agent

Add tap-to-confirm to a Vapi AI voice agent

Updated 2026-07-20
A Vapi agent runs the conversation, but it still captures structured fields (emails, phone numbers, dates) by ear, and that is where speech-to-text fails. Independent testing puts voice-AI email capture at roughly 53% correct, and even at a strong 98% per-digit accuracy a ten-digit phone number is only about 82% right, so nearly one in five callers gives a number with a wrong digit. A visual confirmation layer fixes this by letting the caller read and tap instead of spelling values aloud. Powsoo ships this today for Retell; Vapi support is coming soon. When it lands, the agent will call powsoo_show_card with the transcribed value, the caller will tap Confirm or edit a character, and the confirmed value will flow to your backend. The caller reads instead of listens, so a wrong character is obvious at a glance.

Where a Vapi agent loses data

Vapi gives you a composable orchestration layer: your choice of speech-to-text, model, and text-to-speech, wired into a conversational agent. That flexibility is its strength, but the capture problem is the same across every stack. Speech-to-text is tuned to minimise word error rate, which means it protects common words and leaves rare tokens (names, emails, account numbers) exposed.

The numbers bear this out. Best-in-class models reach 95–98% word accuracy on clean audio, but that drops on the accented, noisy, telephone-bandwidth audio real calls actually carry. For an email address, standard voice-AI capture is right only about 53% of the time. For a ten-digit phone number, even 98% per-digit accuracy compounds to roughly 82% fully correct. The agent then reads the wrong value back confidently, and the caller has to catch a single wrong character by ear.

Vapi support is coming soon

Powsoo’s Vapi adapter is on the roadmap but not yet available to connect. It will ride on Vapi’s tool-calling, so you will not rebuild the agent: connect your Vapi account in the Powsoo dashboard, add a powsoo_show_card tool to the assistant’s tools array (with async off so it waits for the tap), and drop the <powsoo-voice> web component plus the widget script onto the page hosting the call. When the assistant calls the tool, a card renders in the browser, the caller taps Confirm or edits one character, and the confirmed value flows to your backend.

Want it today? Powsoo already works with Retell, using the same tap-to-confirm pattern.

Which fields to confirm

Related

Frequently asked questions

Can I connect Vapi to Powsoo today?

Not yet. Vapi support is coming soon. Powsoo works with Retell today. When Vapi lands it will not replace your agent: Vapi keeps running the conversation, and Powsoo handles the moment a structured field needs confirming by rendering a card the caller taps.

How accurate is voice-only data capture on Vapi?

It depends on the field. Grammar-heavy speech transcribes well, but rare tokens fail: research puts spoken-email capture around 53% correct and shows that 96.6% word accuracy can still mean only 77% exact match on a full identifier. One wrong character breaks an email or a phone number.

What about phone-only Vapi calls with no screen?

A pure PSTN call has no browser to render into. For those, use an SMS fallback: the agent texts a one-tap link so the caller confirms on their phone. See the tap-to-confirm vs SMS fallback guide.

Five minutes to zero spelling errors.

Go from zero to live confirmation cards in under five minutes.
No migration required.

Get started Read the docs