Powsoo / Guides / Collecting dates and dates of birth accurately on voice agents

Collecting dates and dates of birth accurately on voice agents

Updated 2026-07-13
Spoken dates carry two errors at once. The digits can be misheard, and the format is ambiguous: “02/03” is 2 March in the EU and 3 February in the US, and “the third” depends on which month the agent assumed. A voice-only read-back cannot show the caller which interpretation the agent parsed, so a caller can approve “the third of March” while the system stored 3 February. For a date of birth on a healthcare or finance intake form, that mismatch fails a verification check or a record lookup. Showing the date written out in full on a card, such as “3 March 1990”, lets the caller confirm the exact day, month, and year in one tap. They see what the agent parsed, edit it if it is wrong, and Powsoo returns the confirmed value by webhook before it reaches your system.

Two errors in one field

A date has to survive transcription and interpretation. First the agent has to hear the digits correctly. Then it has to parse them into a day, a month, and a year, and spoken dates are full of ambiguity: “02/03”, “the third”, “next Tuesday”, and regional day-first versus month-first order all resolve differently.

Reading the date back as digits does not expose the interpretation. “Oh-two, oh-three” still hides whether the agent stored 2 March or 3 February.

Confirm a written-out date

A card writes the parsed date in full, such as “3 March 1990”. The caller sees exactly which day, month, and year the agent chose and taps Confirm or edits it. That catches both the misheard digit and the wrong format before the value leaves the call.

Powsoo renders this card on Retell today, with Vapi and ElevenLabs coming soon, through the same powsoo_show_card function used for emails and phone numbers, and returns the confirmed date by webhook with the call session ID.

Related

Frequently asked questions

Why are dates error-prone on voice calls?

Two problems stack. The digits themselves can be mis-transcribed, and the order is ambiguous: day-month-year, month-day-year, and spoken forms like 'the third of next month' all resolve differently. A voice-only confirmation cannot show the caller which interpretation the agent chose.

How does a card remove date ambiguity?

The card writes the date out in full, for example '3 March 1990', so the caller sees the exact day, month, and year the agent parsed. They confirm or edit before it reaches your system, which catches format mistakes a spoken read-back hides.

Does this work for date of birth on intake forms?

Yes. Date of birth is a common intake field in healthcare and finance where a wrong value fails a lookup or a verification check. Powsoo renders the parsed date as a card and returns the confirmed value by webhook.

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