How OTP priority routing works
We route each OTP through the fastest live carrier path for that specific destination at that specific moment.
Unlike bulk SMS where least-cost routing makes sense, OTP routing is latency-first. Saving two paise isn't worth a five-second delivery delay on a login flow.
What the router considers
- The destination's home operator, detected from the numbering prefix.
- Live latency and success rate on each eligible route in the last 5 minutes.
- Whether that route has thrown any 5xx responses in the last minute.
- DLT template availability on each route.
The decision is made in under 1ms and surfaced in the webhook response so you can see which route was chosen for each send. Median OTP latency on SMSLocal is 2.3 seconds end-to-end.
Related articles in OTP & Transactional
Browse other help categories
Getting started
Create your account, add credits, and send your first message in under fifteen minutes.
SMS campaigns
Templates, DLT routing, sender IDs, delivery reports, scheduling, and retries.
WhatsApp Business API
Onboarding, template approval, chatbot flows, team inbox, quality rating, and analytics.
AI WhatsApp Agents
Train your agent, sync your catalogue, set handoff rules, and go multilingual.
Did this article help?
If something isn't clear or the steps don't match what you're seeing, tell us and we'll fix the doc the same day.