Users cannot complete the login flow because the code never arrives. That creates a direct availability problem for remote workers, travellers, and anyone in poor coverage areas. Passkeys avoid this dependency because they work offline on the device, while WhatsApp OTP still requires internet access but not cellular signal. Channel choice affects both access and resilience.
Why SMS OTP Fails When There Is No Signal
SMS OTP is a channel-dependent authenticator, so if the user has no cellular coverage the message may never reach the device. The practical issue is not just inconvenience, it is a hard availability dependency: the login flow stops at the factor delivery step. In remote areas or during travel, that can make SMS a brittle choice for primary access.
That fragility matters because the authentication channel becomes part of the service’s uptime profile. If the channel is unavailable, the identity proof never arrives, even when the user is legitimate. The result is a predictable access failure rather than a security exception, which is why channel resilience belongs in authentication design.
When a product team treats SMS as the default second factor, it should assume intermittent delivery, delayed delivery and complete non-delivery as normal operating conditions. Users then experience a failed sign-in, repeated resend attempts and help-desk pressure, especially when they are on roaming networks, underground, at sea or in low-coverage regions.
What This Means for Login Resilience
Authentication design should separate the security property from the transport property. A code sent over SMS depends on the mobile network, while a passkey depends on the device’s local cryptographic capability and can work offline for the user interaction itself. WhatsApp OTP removes the need for a cellular signal, but it still depends on internet connectivity and the messaging platform being reachable.
The operational question is therefore not whether OTP “works”, but which delivery path is most resilient for the user population. If the business serves travellers, field staff, cross-border users or low-connectivity environments, then channel fallback becomes part of access design, not a convenience feature. A resilient login flow should make expected channel failure recoverable without forcing account lockout or manual intervention.
Channel selection also affects assurance. A factor can be more available yet still introduce different trust dependencies, such as internet access, app presence or device binding. The right choice is the one that best balances usability, availability and resistance to abuse for the actual environment, rather than the one that is easiest to deploy.
What To Check Before You Blame the User
Before assuming a user mistyped a code, confirm whether the failure is transport-related: no signal, roaming delay, blocked short codes, carrier filtering or a lost handset. If the organisation uses SMS for step-up or recovery, check whether the fallback path is also dependent on the same unavailable channel, because that can turn a temporary connectivity issue into a full access outage.
It is also worth checking whether the login journey has a genuine alternate path for users who cannot receive SMS at all. A second factor that relies on the same network condition does not increase resilience. In practice, resilient authentication needs a different recovery route, not just another resend button.
Where organisations still rely on SMS for a significant user group, they should validate what happens under no-signal conditions, delayed delivery and device replacement. Those cases show whether the authentication design fails closed in a controlled way or simply strands legitimate users.
Risk and Threat Considerations
The main risk is availability: a user who cannot receive the OTP cannot complete authentication, which can block work, recovery and support workflows. The same dependency can also amplify account recovery risk if users are pushed into weaker fallback paths when the primary channel is unavailable.
Failure mechanism: The login flow depends on a message being delivered through a network the user may not control. If cellular service is absent or unstable, the OTP never arrives, and repeated resend attempts do not fix the underlying transport failure.
Impact: Legitimate users lose access at the exact moment they need it most, while support teams absorb the exception handling. In higher-risk environments, repeated failure can also push organisations toward insecure recovery shortcuts or weaker channel substitution.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, NIST SP 800-63 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | SMS OTP delivery and fallback affect authenticator lifecycle and usability. |
| IA-2 — Identification and Authentication (Organizational Users) | The question is about user login failure when an authenticator cannot be delivered. | |
| Recommendation — Use alternative authenticators when SMS delivery cannot reliably support access. Design login flows so users can still authenticate when one delivery channel is unavailable. | ||
| NIST SP 800-63 | AAL2 — Authenticator Assurance Level 2 | Channel choice affects whether the authenticator provides practical, usable assurance. |
| AAL3 — Authenticator Assurance Level 3 | Passkeys and stronger authenticators are relevant when SMS is too fragile for access needs. | |
| Recommendation — Prefer phishing-resistant or more resilient authenticators where SMS availability is unreliable. Use stronger authenticators when the user population needs reliable access without SMS dependence. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | Authentication channel failures directly affect access continuity and recovery paths. |
| Recommendation — Provide alternate access paths that do not depend on a single transport channel. | ||
Practitioner Guidance
What to prioritise: Treat channel availability as part of authentication design. If the user base includes travellers, frontline workers or low-coverage regions, make sure there is a non-SMS path that is genuinely available when cellular service is not.
What to verify: Test the full sign-in and recovery journey with no signal, poor signal and roaming conditions. Confirm that the alternate factor or recovery method is reachable without relying on the same transport failure mode.
Decision rule: If the business cannot tolerate authentication outages, move away from SMS as the only usable path and prefer a method that does not depend on real-time message delivery for the primary login experience.
Practitioner takeaway: The key design question is not whether SMS OTP is familiar, but whether the organisation can accept that a missed message becomes a denied login, and potentially a support incident, whenever the user has no signal.
Related resources from NHI Mgmt Group
- Guide: MFA Guide
- What happens when acquired users and applications are granted access before they are properly vetted?
- What happens when software manufacturers cannot prove they handled vulnerabilities and AI-generated code with sufficient controls?
- What happens when users try to authenticate on smart TVs using a traditional OTP flow?
- What happens when security leaders deploy AI tools that cannot explain how they reached a decision?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org