HiFi Desk

You tap Send OTP, the screen starts a thirty-second countdown, and the message never lands — an OTP not received at the exact moment a payment, login or account recovery depends on it. The frustrating part is that the fix is almost never where help pages tell you to look, because each service blames its own corner of the system: the app says contact your bank, the bank says contact your operator, the operator says restart your phone. The truth is that a one-time password passes through several hands between the server and your inbox, and it can fail at any of them. This breakdown walks the full chain in order of likelihood, so you stop guessing and start eliminating causes one at a time.

How an OTP Travels, and Where It Dies

When you request a code, the service generates it, hands it to a bulk-SMS gateway, the gateway routes it to your mobile operator, the operator pushes it to the tower your SIM is registered on, and finally your handset accepts, stores and displays it. That is five hand-offs, and a failure at any one of them looks identical from your side: a blank inbox. Understanding that chain turns an OTP not received complaint from a mystery into a checklist you can work through in a fixed order.

The good news is that the failure points are not equally likely. Problems on your own handset — weak signal, an aggressive spam filter, a blocked sender thread, full message storage — account for the overwhelming majority of cases and are the ones you can fix in minutes. Operator-side routing problems and sender-side gateway congestion are rarer, slower to resolve, and only worth suspecting after the local checks are exhausted. The table below maps each stage to its typical symptom, and the sections that follow work through them from most to least likely. Codes that protect money deserve the most urgency: if a payment confirmation code vanished mid-transaction, read the separate step-ordered breakdown of a failed UPI payment where money was still debited alongside this one.

The First 60 Seconds: Signal, Airplane Mode, Restart

Start with the dullest explanation, because it is the most common one. An SMS needs an active registration between your SIM and a tower. One bar of signal is often enough for a call to ring but not enough for a queued SMS to push through promptly, and a phone that shows full bars indoors may actually be clinging to a congested or distant tower. Delivery can lag by several minutes in basements, lifts, metro coaches and buildings with metal cladding.

• Check the signal indicator for the SIM that receives OTPs — on a dual-SIM phone, codes go to the number registered with the service, which is not always the SIM you use for data.
• Toggle airplane mode on, wait ten seconds, and toggle it off. This forces the phone to re-register with the network, and queued messages often flood in immediately.
• Confirm SMS is not being sent over Wi-Fi calling on a flaky connection; switching Wi-Fi off briefly rules this out.
• If nothing changes, restart the handset once. A reboot clears a stalled modem process, which is a known cause of silently dropped messages.
• Move near a window or step outside before requesting the next code, so the retry happens under better conditions.

If the code arrives after the airplane-mode toggle, the problem was registration, not the sender, and there is nothing further to fix. If the inbox stays empty, move down the ladder — and resist tapping Resend repeatedly, for reasons covered in step five.

Spam Folders and Blocked Senders: Where OTPs Hide

Modern SMS apps filter messages the way email services filter mail, and transactional short-codes are frequent false positives. The message arrives at your phone, the app classifies it as junk, and it lands in a folder you have never opened — delivered, but invisible. A filter decision like this is among the most common reasons for an OTP not received report, precisely because nothing looks wrong: no error, no notification, no trace in the main inbox.

1. Open your SMS app and look for a Spam and blocked, Junk or Filtered messages section — usually behind the three-dot menu or the profile icon.
2. Scroll that folder for the sender. OTP senders use alphanumeric headers (such as a six-character sender ID) rather than normal phone numbers, so sort by date, not name.
3. If the code is there, long-press the message and choose Not spam or Move to inbox so future codes from that header arrive normally.
4. Separately, open the app’s Blocked numbers list. A short-code blocked months ago — often by accident while clearing promotional texts — silently swallows every later OTP from that sender.
5. If you use a third-party SMS or caller-ID app, check its own filter too; it can quarantine messages before the stock app ever sees them, and its block list is independent.

One habit prevents a repeat: when you clear promotional SMS in bulk, delete the messages rather than blocking the senders. Banks and apps often share gateway routes with marketing traffic, and a block aimed at an advert can take a login code down with it.

Full SMS Storage and SIM Memory: The Silent Blocker

An inbox that has quietly filled up can refuse new messages without showing any warning you would notice. This is rarer on recent flagships, but very real on budget handsets, older phones, and any device where thousands of transactional and promotional texts have accumulated for years. The phone’s messaging database bloats, writes start failing, and incoming SMS are rejected at the final step of their journey — after the operator has already marked them delivered.

Two separate stores matter. The first is the phone’s own message storage, which lives with the rest of your data; if the whole device is nearly full, SMS writes are among the first casualties. The second is the SIM card’s own tiny message memory, a legacy store that holds only a few dozen texts; if your messaging app is set to save to SIM, it can fill within weeks. Open your SMS app’s settings and confirm messages save to the phone, then delete old one-time codes in bulk — they have no value once used.

If the device itself shows almost no free space even after cleaning, that is its own ladder of causes, covered in the separate checklist on why phone storage stays full even after deleting files.

A quick test confirms or clears this cause in under a minute: send yourself an ordinary SMS from another phone. If a plain text from a friend’s number does not arrive either, the problem is local and storage or registration is the prime suspect. If normal texts arrive and only OTPs are missing, the filter, block list or DND checks are the better trail.

Resend Cooldowns: Why Tapping Again Backfires

The natural instinct when a code does not land is to hammer the resend button. It is also the single most counterproductive move on this list. Services apply rate limits to OTP requests: ask too many times in a short window and the system stops sending entirely, usually for fifteen minutes to a few hours, and sometimes with no message telling you a lock has been applied. You then sit waiting for codes that were never dispatched.

There is a second trap: validity versus delivery. Most codes expire three to ten minutes after generation, but a congested gateway can deliver an SMS late — so the code that finally arrives may already be dead, while the newest code you requested invalidates every earlier one. If two codes land at once, always use the most recent, and if a code fails, check the timestamp before assuming the whole channel is broken.

The patient sequence wins: request once, wait a full three minutes without touching the button, and use that time to run the signal and spam checks above. If nothing arrives, request exactly once more. If the second attempt also vanishes, stop — further taps only push you into a lockout — and move to the DND and SIM checks below. When a service offers a voice-call OTP option, take it on the second attempt; call routing is independent of SMS routing, so it both delivers the code and tells you which channel is failing.

DND in India: When OTP Not Received Comes Down to One Setting

India has a filtering layer that most global troubleshooting pages never mention. The DND (Do Not Disturb) preference you register with your mobile operator — usually through the 1909 service or the operator’s app — is designed to stop promotional messages. Transactional messages such as OTPs travel on a separate route and are supposed to pass through regardless of your DND status. In practice, the sorting is only as good as the sender’s message classification, and misclassified or borderline traffic can get caught when a strict full-block preference is active.

The pattern that points here is selective failure: ordinary texts from friends arrive instantly, codes from banks arrive fine, but messages from one particular app or website never show up at all, on any phone, at any signal strength. That smells like filtering at the operator level rather than anything on your handset. An OTP not received only from specific senders — while everything else flows — is the classic DND fingerprint.

To check, call 1909 from the affected SIM — the dedicated DND service number every Indian operator runs — or open the DND section of your operator’s self-care app. Either route shows whether DND is active and at what level. You can switch from full blocking to category-based blocking, which keeps marketing out while giving transactional routes more room; allow a day or so for the change to settle. If you recently activated full DND and OTP trouble began around the same time, this is very likely your answer — adjust the preference, wait a day, and test again before escalating further.

The SIM-in-Another-Phone Test and Carrier Escalation

By this point you have cleared the handset-side suspects. The next step is the single most informative test in the whole ladder, and it costs nothing: put your SIM into a different phone — borrow one from family for ten minutes — and request a code. The result splits the remaining possibilities cleanly in two.

If the code arrives on the borrowed phone, your number and your operator are fine, and the fault is in your handset: a buggy messaging app update, a corrupted message database, a misbehaving caller-ID app, or a software issue a reset of the messaging app’s data will often cure. If the OTP not received pattern follows the SIM into the second phone, the handset is innocent and the problem sits with the operator or the sender’s route to it.

When the SIM test points at the network, call your operator’s customer care from another number and be specific: say that transactional SMS from short-codes are not being delivered to your number, that ordinary person-to-person SMS do or do not arrive (you now know which), and that you have already ruled out the handset with a SIM-swap test. Ask them to check whether your number has any service barring, a messaging fault, or a stuck registration on their side, and ask for a complaint reference number so the issue is trackable rather than a one-off call.

Two operator-side causes are worth asking about by name. A SIM that has been inactive or unrecharged for a long period can have incoming services restricted until it is revalidated. And a SIM registered on an older network generation in a weak-coverage area can drop SMS that a reprovisioned 4G/5G-ready SIM would receive; operators replace SIM cards free or cheaply at their stores, and a fresh SIM resolves a surprising share of stubborn delivery faults.

OTP on WhatsApp but Not on SMS: What That Tells You

Many Indian services now deliver codes over WhatsApp as well as SMS, and a lopsided result — the WhatsApp code arrives in seconds while the SMS never shows — is genuinely useful diagnostic information rather than just a quirk. The two messages travel completely different roads. WhatsApp delivery rides your data connection over the internet; the SMS rides the operator’s messaging network tied to your SIM’s tower registration. When one works and the other fails, everything the two share is cleared of suspicion: the sender generated the code, your number is correctly registered with the service, and your phone is on.

What remains suspect is everything unique to the SMS path: tower registration (a phone can hold a solid Wi-Fi connection with no usable mobile signal at all), the operator’s SMS routing, a DND preference, your SMS app’s spam filter, its block list, and message storage. So a WhatsApp-yes, SMS-no result tells you to concentrate on steps one through six of this ladder and to stop wondering whether the service itself is down — it demonstrably is not.

The reverse asymmetry carries information too. If SMS codes arrive but WhatsApp ones do not, look at data connectivity, WhatsApp’s own notification and storage permissions, or an archived or muted chat with the sender’s business account. Either way, when a service offers both channels, request both during troubleshooting: the pair of outcomes localises the fault faster than any single test.

When a Missing OTP Is a Warning Sign, Not a Glitch

Almost every missing code is an innocent delivery failure, and the ladder above fixes it. But one specific pattern deserves a different, faster response: your phone suddenly shows no service for an extended period in a place where it always had coverage, calls and SMS stop entirely, and around the same time you notice login alerts, password-reset emails you did not trigger, or unfamiliar activity on payment apps. That combination can mean someone has had your number moved to a SIM in their control, so your codes are being delivered — to them. The mechanics, the early signs and the exact response sequence are laid out in the companion explainer on how a SIM swap attack redirects your calls and OTPs.

The distinction is easy to apply. A delivery problem is selective and quiet: some messages arrive, the phone otherwise works, nothing else is strange. A takeover is total and noisy: the SIM is dead, and account activity you did not initiate appears. If it is the second pattern, do not spend an hour on spam folders — contact your operator immediately to confirm whether a SIM change was processed on your number, lock or freeze your payment and banking apps from another device, and change the passwords on accounts tied to that number.

Suspicious calls or messages connected to the incident can be reported through the Department of Telecommunications’ citizen portal at Sanchar Saathi, which also lets you check which SIM connections exist in your name.

A final note on expectations. OTP delivery over SMS is reliable most of the time, but it was never engineered to be instant or guaranteed, and a small background rate of delay is normal on every network in the world. Build slack into anything time-critical: request codes before a payment deadline rather than at it, keep a second channel such as voice OTP or an authenticator app enabled where services offer one, and treat the ladder in this post as a five-minute routine rather than a crisis. Codes that never arrive are an annoyance; knowing exactly why they did not arrive is the difference between an annoyance and a locked account.

Frequently Asked Questions

Why am I not receiving OTP messages on my phone?

The most likely causes, in order: weak or stalled network registration, the SMS app’s spam filter hiding the message, a blocked short-code sender, full message storage, a resend lockout from tapping the button too often, or a strict DND preference affecting messages from specific senders. Work through them in that order — toggling airplane mode and checking the spam folder resolves the majority of cases within minutes.

How do I unblock OTP messages marked as spam?

Open your SMS app, find the Spam and blocked (or Junk) section behind the menu or profile icon, locate the message, long-press it and choose Not spam or Move to inbox. Then open the app’s blocked-numbers list and remove the sender’s short-code if it appears there. If you use a third-party SMS or caller-ID app, repeat both checks inside that app, because its filter and block list work independently.

Does DND activation block OTP SMS in India?

It is not supposed to — the DND preference registered with your operator targets promotional messages, while OTPs travel on a transactional route that should pass through. In practice, a full-block DND setting combined with misclassified sender traffic can stop codes from specific apps or websites. Call 1909 or open your operator’s self-care app to check your DND level, and switch from full blocking to category-based blocking if an otp not received problem started soon after you activated it.

Why do I get OTP on WhatsApp but not SMS?

Because the two codes travel different roads: WhatsApp uses your internet connection, while SMS uses the operator’s messaging network tied to your SIM’s tower registration. If WhatsApp codes arrive and SMS ones do not, the sender and your account are fine — the fault is in the SMS path: mobile signal, operator routing, DND, your SMS app’s spam filter or block list, or full message storage.

How long should I wait before requesting OTP again?

Wait a full three minutes after the first request, using that time to check signal and the spam folder. Then request exactly once more. Repeated rapid taps trigger rate limits that can silently stop all codes for fifteen minutes to several hours. Also note that most codes expire within three to ten minutes, and requesting a new code usually invalidates the previous one — if two arrive, use the newest.

Can a full SMS inbox stop OTPs from arriving?

Yes, especially on budget or older handsets where years of texts have accumulated. If the phone’s storage or messaging database is full, incoming SMS can be rejected at the last step with no visible error. The SIM card’s own tiny message memory can also fill if the app saves messages to SIM. Delete old one-time codes in bulk, set storage to phone rather than SIM, and test by sending yourself an ordinary SMS from another number.