Send the code by SMS first, and offer a voice call only as a fallback after a short wait or a user request. Voice helps people with landlines, poor signal for data or accessibility needs. It also costs more to abuse, so rate-limit it harder than SMS.

SMS is the default for one-time codes because it's fast and familiar. But some users never get the text: a landline, a blocked sender, a phone in airplane mode on wifi. A second path keeps them from being locked out. How you add that path decides whether it's a safety net or a hole.

SMS and voice compared

FeatureSMSVoice call
SpeedSecondsSeconds, plus listening time
Works on landlinesNoYes
AccessibilityNeeds readingSpoken digits help low-vision users
EntryAutofill possibleTyped by hand
Fraud riskPumping and SIM swapToll fraud, harder to detect
Cost per attemptPer segmentPer minute

A sane flow

  1. Send the code by SMS and show a "Resend" option after about 30 seconds.
  2. After a second failed attempt, offer "Call me with the code."
  3. Cap attempts per number, per account and per IP. Voice gets a tighter cap than SMS.
  4. Never let a user choose any destination number unless they've already proven they own it.
  5. Log every attempt and watch for spikes to unusual prefixes. SMS pumping fraud protection shows the pattern, and voice fraud follows the same shape.

Make the code safe in either channel

Keep it short, random and single-use, with a short life of a few minutes. Don't reuse a code across channels, and invalidate old codes when a new one is issued. SMS OTP and verification API and two-factor authentication go deeper.

What Ready offers

We make Ready, and it's an SMS and iMessage API plus the Ready Dialer for people-placed calls from a dial pad. It doesn't offer an automated voice-code call. If voice OTP is a requirement, use a voice provider for that leg, and keep SMS on Ready. For the SMS leg, register a "Login and verification codes" campaign once your brand is approved, from Registration, Add campaign, or with use_case TWO_FACTOR_AUTH over the API. Most approvals take 2 to 7 days.

An SMS code costs $0.0075 plus the $0.0045 carrier fee per segment. Keep the text to one segment. Separate verification traffic from marketing numbers, as in separating MFA and marketing numbers.

Alternatives to both

For high-risk accounts, an authenticator app or a passkey beats any phone channel. Offer SMS and voice as recovery paths, not the strongest option. See Twilio Verify alternative for building the check yourself.

Frequently asked questions

Do I need voice at all? Only if a real share of your users can't receive SMS. Check your own failure data first.

Will users read digits correctly? Repeat the code twice and slow the pace, since listeners can't re-read a digit they missed.

Is voice OTP less secure? It has the same weaknesses as SMS, plus voicemail interception if a call is missed.

Next step

Count how many verification attempts failed to get a code in the last month. If it's a rounding error, polish SMS delivery first.

Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.