# Mobile Auth — one API, every channel picked for you

> Mobile Auth reads operator health, country, and device state, then picks the channel that's actually working right now: SNA, WhatsApp, SMS, or Voice. We pick. You ship.

## How it works
You make a single `otpless.verify({ phone })` call. The decision engine reads per-session signals — country, carrier, device, channel health, WhatsApp availability, data network — and picks the channel most likely to log this user in fastest (decision in under 50ms). If a channel fails, times out, or degrades, Mobile Auth routes in-flight to the next viable channel. No priority lists, no retry logic.

## Channel pool
SNA → WhatsApp → SMS / RCS → Voice.

## Metrics
- 99%+ login success across the channel pool.
- P90 time to verified ~7 seconds or less.

## FAQ
**What is Mobile Auth?** One API that routes each login to the best-performing channel in real time, based on success rate, latency, operator health, and per-user history.
**Do I have to write fallback logic?** No — one verify() call; routing and in-flight fallback are automatic.
**What login success rate?** 99%+ across the channel pool.

Talk to our team: https://otpless.com/talk-to-sales.html