OTP retry and failover logic
If the primary route fails, we fail over to the next-fastest one before your user even sees a delay.
OTP sends automatically retry on failure, with a per-channel and per-carrier retry policy that respects operator capacity and your own rate limits.
The default retry ladder
- 01Send on the primary route with a 7-second timeout.
- 02On failure or timeout, failover to the second-fastest route for that operator.
- 03If both SMS routes fail, automatically fall back to WhatsApp OTP (if enabled and the user has WhatsApp).
- 04If WhatsApp also fails, fall back to voice OTP as a last resort.
- 05Return a final status to your webhook within 12 seconds.
You can tighten or relax this ladder per message by passing a retry_strategy in the send payload.
Related articles in OTP & Transactional
Browse other help categories
Getting started
Create your SMSLocal account, add INR credits to your wallet, complete DLT registration, and send your first compliant SMS, WhatsApp, or OTP in under fifteen minutes.
SMS campaigns
SMS content templates, DLT routing, sender ID setup, delivery report statuses, bulk campaign scheduling, throttle controls, and automatic retry logic for India.
WhatsApp Business API
Complete guide to WhatsApp Business API — onboarding, Meta template approval, chatbot flow setup, shared team inbox, quality rating management, and conversation analytics.
AI WhatsApp Agents
Train your AI WhatsApp agent on your own knowledge, sync your product catalogue, configure handoff triggers, and serve customers across twelve Indian languages.
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.