# A code you can hear, for the users SMS misses.

Voice verification places a call and reads the one-time code aloud — for landlines, for users who can't receive SMS, and as the fallback when a text doesn't arrive. It's rolling out as an orderable channel in the same per-country plan, addressed by the same phone number and confirmed by the same check.

## The channel that reaches users when text can't.

Voice is a phone-family channel on the Bird Verify API: the recipient is the same phone number, and voice becomes an orderable entry in the per-country plan — typically the fallback after SMS. Landline-only users, accessibility needs, and markets where SMS underdelivers are exactly where a spoken code earns its place.

## What voice verification adds.

Rolling out as a channel in the existing plan.

## Voice is an entry in the plan.

Order voice after SMS in the configuration and the create call is unchanged. As delivery-driven advancement rolls out, the session uses voice when the channel ahead of it doesn't complete.

## How the fallback works.

Order SMS first and voice second, and a single verification works the plan in order. SMS is attempted; if it doesn't arrive, the session moves to a voice call that reads the code aloud, and every code in the session stays valid so the user can use whichever reaches them. Automatic, delivery-driven advancement is rolling out with delivery status.

## Reach every user, on the channel that gets through.

Voice joins email, SMS, and WhatsApp as a channel in the same per-country plan — a spoken fallback on the same two endpoints.