A caller knows the customer's name, number and perhaps a recent order. That still does not prove identity. A natural-sounding voice assistant must not mistake a fluent conversation for authentication.
Match verification to the requested action
| Request | Check | Response |
|---|---|---|
| Opening hours | None | Answer directly |
| Available slot | Low | Reveal no customer record |
| Move existing booking | Medium | Require another factor |
| Change address or payment data | High | Secure channel or human |
Every call need not begin like an interrogation. Increase assurance only when the assistant is about to disclose protected information or make a consequential change. The customer experience stays light while the boundary remains clear.
Useful additional factors
- A one-time code sent to an existing phone number or email.
- A reference that is not public information.
- Confirmation inside an authenticated customer portal.
- Human handoff when checks fail or the pattern looks suspicious.
A date of birth and address may already be known. A new number supplied during the call is not a second factor. Treating the caller's voice as an identity credential would require a deliberately designed biometric process, not a guess by the model.
Refusal needs a useful next step
Do not reveal which answer failed. Say: “I cannot complete this change by phone yet. I can send a secure confirmation or connect you to the team.” That protects the record without abandoning a legitimate customer.
Our guide to Voice AI and data protection covers disclosure and recording. For consequential actions, draft, approve, execute adds operational control.
Sources
FAQ
Must every caller be identified?
No. General information can be given freely. Assurance should increase with the sensitivity of the data and impact of the action.
Is caller ID enough?
No. Numbers can be spoofed and devices can be used by another person.
Can Voice AI ask for a date of birth?
It may be one weak knowledge factor but is often insufficient for sensitive changes.
What happens after a failed check?
Reveal no protected data, block that action and offer a secure alternative or human handoff.