Authenticate customers globally with Voice OTPs
Provide a convenient and secure verification process with the most inclusive communication channel. Voice OTP delivers a one-time password as an automated phone call, so customers without mobile data, a smartphone or a working SMS route still receive their code.
Sign up and try our platform today. See Voice pricing here.
195 countries for outbound Voice OTP calls
Mobile and landline numbers reached, including users with no mobile data
Pay only for answered OTP calls
What is a Voice OTP and how does an OTP call work?
A Voice OTP is a one-time password delivered through an automated phone call instead of a text message. The platform calls the user’s registered number and reads the code aloud, digit by digit, using a pre-recorded or synthesized voice. The user enters the code in your app or website to complete verification.
Businesses in banking, e-commerce and ride-hailing use Voice OTP as an alternative to SMS, or as a fallback when SMS delivery fails or is delayed. A voice call reaches landlines, feature phones and users with no mobile data, and it gives customers who cannot read a screen an accessible way to authenticate.
When to choose Voice OTP
-
SMS cannot reach the user, or delivery is delayed
-
The user has a landline, a feature phone or no internet connection
-
Accessibility requirements call for an audio channel
- You want an additional verification step for sensitive actions
The benefits of Voice OTPs
Using an established and reliable channel like Voice has functional, performance, and cost advantages.
Maximize reach for authentication messages
Provide user choice
Prevent fraud
Send one-time PINs (OTPs) using Voice Messages API
Send OTPs to users via a configurable voice message that is read out loud when they pick up the phone.
- Flexible configuration options for an optimal user experience
- Adjust the speech rate to give time for users to enter the OTP code
- Allow users to easily replay voice messages
-
Add pauses to make the speech pattern sound more natural
How call OTP verification works, step by step
STEP 1
Login
The customer logs into their account with a username and password.
STEP 2
Channel choice
A screen is displayed offering them a choice of channels for the delivery of an OTP to authenticate them.
STEP 3
Request OTP by call
The customer opts to receive a phone call.
STEP 4
Code read within the call
The automated call reads out a code.
STEP 5
OTP input
The customer inputs the OTP from the call into the website/application
Send your first OTP call in minutes
Create a free account, send a test Voice OTP to your own verified number and hear automated voice verification in action before you commit to any volume.
Try for freeUse a secure and flexible channel for sending OTPs
Voice OTP vs SMS OTP: when to use each, and how to combine them
SMS OTP is the most common verification method for login flows because it is fast, silent and familiar. Voice OTP is the alternative for the cases SMS cannot cover: numbers without SMS capability, users who need to hear the code rather than read it, and messages that do not arrive. Running both channels, with fallback between them, gives every user a second route to their code.
| Voice OTP | SMS OTP | |
|---|---|---|
| Delivery format | Automated phone call reads the code aloud | Text message contains the code |
| Reaches landline | Yes | If the carrier has a custom solution |
| Works for users who cannot read the screen | Yes, audio channel | Text only |
| Delivery path | Voice network, subject to DND rules, and the call is answered by the user | SMS route, subject to operator filtering and DND rules |
| Requires the user to answer | Yes | No, delivered silently |
Use Voice as the fallback when SMS delivery fails
Infobip’s 2FA API generates and verifies the PIN and can deliver it over SMS, Voice or Email from a single integration. Because one API covers all three, you can request a PIN on a second channel when the first one is not delivered. Infobip Authenticate automates this with multistep failover across SMS, Voice, WhatsApp, RCS, Viber and Email, with optimized routing, so every customer gets one code through the channel most likely to reach them.
Configure every OTP call to match your security policy
The attempt limits, PIN lifetime and send limits you set on a 2FA application apply to SMS and voice PINs alike, and voice adds its own template options for speech rate and replay key. Set the rules once and apply them across channels for consistent, secure authentication.
PIN length and type
Choose the PIN length and type
PIN time to live
Define how long a code stays valid, for example 15 minutes
Attempt and send limits
Cap verification attempts per PIN and sends per phone number per day
Replay on request
Let the user press a key, for example 1#, to hear the code again
Speech rate
Slow the read-out (0.5 to 2.0 times normal speed) and space the digits so 5 8 4 2 is read as four digits, not as a number
Language
Select the language of the spoken message
Caller ID
Present a recognizable sender number so customers know who is calling. In the US, Branded Calling ID can add your business name, logo and call reason when you use Infobip-provided numbers
Protect your OTP traffic from fraud and unnecessary cost
Artificially inflated traffic and toll fraud drive up OTP costs for every business that verifies phone numbers. With Voice OTP you pay only for answered calls, which helps reduce the impact of spam attacks.
Infobip Signals helps detect and block fraudulent OTP traffic, and the 2FA API’s per-number send limits and attempt caps let you limit resend and brute-force abuse on your side of the integration.
- Pay only for answered OTP calls
- Infobip Signals helps block artificially inflated OTP traffic
- Configurable send and verification limits per application and per phone number
- Security and compliance certifications, including ISO 27001, ISO 27017, ISO 27018, SOC 2 Type 2, ISO 9001 and ISO 22301
Integrate Voice OTP in minutes
Choose the approach that fits your implementation:
- Use the 2FA API to manage the OTP flow. After configuring an application and message template, send the PIN over Voice with the 2FA API and verify it with the verification endpoint. Infobip generates the PIN and handles delivery; your application submits the PIN for verification.
- Use the Voice Messages API to deliver an OTP as a text-to-speech call with POST /tts/3/advanced. Your application generates and verifies the PIN, then includes it in the message text—for example, with spaces between digits so they’re read individually.
Voice Messages API request body from the Voice OTP tutorial, POST /tts/3/advanced. We also provide SDKs and Postman collections.
Voice OTP pricing: pay as you go, by destination
Voice OTPs are priced as outbound voice calls. Rates vary by destination country and network, and you are billed only for calls that are answered. Use the calculator to estimate your monthly cost from expected OTP volume, or contact us for volume-based pricing.
Pay-as-you-go
Sign up for freeVolume-based discounts
Contact usA Voice OTP service recognized by industry analysts
Infobip’s authentication and OTP delivery run on the platform that industry analysts rank as a CPaaS leader.
CPaaS Established Leader
Juniper Leaderboard 2025
Infobip is named as No. 1 CPaas provider
MetriRank CPaaS Report 2024
Infobip is named a Leader
CPaaS Universe Report 2025
Infobip is named a Leader in worldwide CPaaS
IDC MarketScape 2025
Uber sends OTPs with Infobip
Frequently asked questions about Voice OTP
A Voice OTP is a one-time code delivered by an automated phone call rather than a text message. The system calls the user’s registered phone number and reads the OTP code aloud, and the user types it into the app or website to authenticate.
With our 2FA API, your application requests a PIN, Infobip generates the code, calls the user’s number and verifies the code they enter. With the Voice Messages API, you submit the text and Infobip calls the user and reads it out. The user hears the code digit by digit using text-to-speech and can press a key to hear it again.
It depends on the user, the route and the cost. SMS OTP is usually the first choice for login verification. CF37 Choose Voice when SMS may not reach the user, such as on landlines without SMS support, feature phones or users with no mobile data. Many businesses run both and set the fallback order that suits them.
Yes. A voice call needs no mobile data or smartphone, so it reaches landlines, feature phones and users in low-connectivity areas.
You are not billed for unanswered calls. You can let the user request the code again, resend it after a set interval, or request a new PIN on SMS or another channel through the 2FA API.
Voice OTPs are billed as outbound voice calls at per-destination rates, only for answered calls. Pay-as-you-go pricing and a calculator are available on the Voice pricing page, and volume discounts are available on request.
Voice OTP delivers the code in real time to the registered phone number. Combined with PIN expiry and attempt limits, it works as an additional factor in two-factor authentication (2FA) and multi-factor authentication (MFA).
Voice OTP calls can be placed to mobile and landline numbers in 255 destinations. Text-to-speech is available in 77 languages and dialects with 960 voices.
Yes. The 2FA API can deliver PINs over SMS, Voice or Email from one integration, so you can request a Voice PIN when an SMS is not delivered without changing your verification logic. Infobip Authenticate automates the failover and extends it to WhatsApp, RCS and Viber.