Technician helping troubleshoot Fire TV automation and Alexa routine issues for seniors

Steve H.

Expert ★★★★★ 27,853 satisfied customers

Specialities: SMS verification/OTP delivery diagnostics, 2FA text and short-code issues, iPhone & Android message filtering checks, carrier-level blocking and number porting troubleshooting.

When verification texts don’t arrive, check signal, SMS filters, short codes, blocked senders, and number/account details before you try “resend” loops

Technician avatar Technician
Hi! “Can’t receive SMS verification code” usually comes down to one of three buckets: the service isn’t actually sending, the carrier is filtering the code (often short-code SMS), or the phone is hiding/blocking it.

To keep this safe (no account lockouts, no “remove your number” steps), tell me:
1) Which service is failing most (Microsoft/Google/Apple/bank/social)?
2) Are you on iPhone or Android?
3) Do you receive normal texts from people, and do you receive any one-time passwords (OTP) from other apps?
Customer
iPhone. Normal texts from friends work. But I’m not getting the SMS code for Microsoft sign-in. It says “we sent a verification code,” and then nothing. It also happened with a gaming app yesterday. I’m scared to keep trying because I don’t want to get locked out.
Technician avatar Technician
You’re thinking about it the right way. Repeated “resend code” clicks can trigger cooldowns on some accounts, so we’ll diagnose first.

Quick clarifiers that help narrow it fast:
• Is your phone number a normal mobile SIM number (not a VoIP/virtual number)?
• When you request the code, does it come from a 5–6 digit short code, or a full phone number (if you’ve ever received one)?
• Did this start after anything changed: new carrier, number port, SIM/eSIM change, iOS update, or traveling/roaming?
Customer
It’s a normal SIM, not Google Voice or anything. I ported my number to a new carrier like 3 weeks ago. I can get some codes from my bank sometimes (they come from 5 digits), but Microsoft never arrives. The gaming app never arrives either.
Technician avatar Technician
That pattern is very telling: person-to-person SMS works, some OTP texts work, but specific services’ codes don’t. After a number port, short-code routing and carrier spam filtering can behave differently than regular texts for a while.

Let’s do “safe checks” that don’t mess with your account security settings:

1) Look for hidden messages: On iPhone Messages, do you use “Filter Unknown Senders”? If yes, check the “Unknown Senders” list when you request a code (OTP texts often come from unknown senders).

2) Blocked senders: In iPhone settings, check if any numbers are blocked. Even one blocked short code can make it feel like “codes never arrive.”

3) Compare conditions: Request the code once when you have strong cellular signal (not basement/parking/weak LTE). Weak signal can delay short-code SMS even when iMessage and Wi-Fi stuff seems fine.
Customer
I do have Filter Unknown Senders on. I checked Unknown Senders and I don’t see Microsoft there. I also have a spam-blocker app for calls, not sure if it touches texts. My signal is okay but sometimes I’m in a lower floor where it drops to 1 bar.
Technician avatar Technician
Perfect — we can use that to separate “delivery” from “filtering.” If it’s not in Unknown Senders, then either the message isn’t reaching the phone at all, or it’s being filtered earlier (carrier-level or app-level).

A low-risk diagnostic sequence (no password changes, no removing your phone number):

• Timing check: When your bank OTP arrives, does it arrive instantly or with a delay (like 1–3 minutes)? Delays suggest routing/signal, not necessarily a block.

• Network condition check: Do one test request with strong cellular signal and without relying on Wi-Fi calling (just for a test). If outcomes change, it hints at routing/coverage differences.

• Sender-type check: If two different services never arrive (Microsoft + gaming app), that often points to a shared short-code route or filtering rule rather than a single app glitch.

When you request the Microsoft code, does it show any “try again later” message or timer, or does it let you request over and over?
Customer
Yesterday it let me request a bunch of times. Today it sometimes shows a short timer. Bank OTP was delayed earlier, like 2 minutes. Microsoft never came. I’m worried the number on the Microsoft account is wrong but it shows the right last digits.
Technician avatar Technician
The timer/cooldown is normal after multiple attempts — it’s a security behavior, not you doing something “wrong.” Also, seeing correct last digits is good, but there are still two subtle gotchas we can check safely:

1) Country/format mismatch: Some accounts store the number with a country code. If the account is set to the wrong country/region, OTP delivery can fail even if the last digits look right.

2) Old number on file elsewhere: Some services can have multiple verification methods saved (old phone, backup phone). If you’re seeing only SMS, it may still be sending to the right one — but it’s worth confirming there isn’t a second number hidden in security info.

Not asking you to change anything — just confirm what you see. Are you signing in on the same iPhone that has the SIM, or on a laptop/browser and waiting for the SMS on the iPhone?
Customer
On a laptop, waiting for the SMS on the iPhone. Also I traveled a month ago but I’m home now. Roaming is off. The Microsoft screen only shows SMS right now. No email option.
Technician avatar Technician
Thanks — that setup is common, and it helps us keep the testing controlled. Since you’re waiting on the phone, we can focus on delivery to the iPhone line.

Here’s what I’d avoid so you don’t get stuck in a lockout loop:
• Don’t keep hitting “send code” repeatedly (cooldowns can get longer).
• Don’t remove your phone number from the account while you can’t receive codes.
• Don’t “wipe/reset network settings” as a first move — that’s disruptive and usually not necessary for diagnosis.

Safe checks that won’t change your account:
• Verify the iPhone can receive other short-code messages today (you already saw the bank one, even if delayed).
• Check whether any SMS spam filtering or “block unknown” feature is enabled in a carrier app/plan feature (it can affect automated codes more than normal texts).
• Note whether delays happen only in low-signal areas — short-code OTP is less forgiving than regular messaging.
Customer
That makes sense. I also noticed some delivery notifications (like packages) don’t always come either. So it might be short codes in general. Is there a way to confirm it’s a carrier filtering problem without calling them right away?
Technician avatar Technician
Yes — you can gather evidence without changing anything.

Carrier-filtering clue checklist (safe):
1) Some short codes arrive (bank) but certain brands never arrive (Microsoft + gaming). That split often suggests route-specific filtering, not a broken phone.
2) Messages arrive delayed more often in low signal areas. That points to delivery reliability, not just “blocked.”
3) Unknown Senders is empty during the test — meaning it’s not simply being hidden by iPhone filtering.

If you can, do one controlled test later: request one code, wait a reasonable time, and note whether you see a cooldown timer. Don’t brute force it. The result helps distinguish “service rate limit” vs “SMS delivery issue.”

One more question: do you have any second device (old phone) still logged into the account that could receive a push prompt instead of SMS, or is SMS the only option everywhere?
Customer
SMS seems like the only option right now. I might have an old phone but it’s wiped. I’ll do the controlled test and stop spamming resend. I just want the “most likely causes” list so I don’t waste time.
Technician avatar Technician
Most likely causes (based on your symptoms) — still diagnosis, not “do this and it’s fixed”:

• Short-code delivery/routing after a number port (especially when some OTP texts are delayed and others never arrive).
• Carrier spam protection or message blocking affecting automated verification SMS more than normal texts.
• Weak cellular signal at the moment of delivery (basements and 1-bar LTE can silently drop time-sensitive OTP messages).
• Service-side cooldown/security hold after many resend attempts (explains timers).
• Number/region detail mismatch (country code/region stored in the account).

If you keep notes on (1) whether bank OTP is delayed vs instant, (2) whether Microsoft never arrives across multiple days, and (3) whether Unknown Senders stays empty, you’ll have a clear picture of the bucket you’re in — without making risky account changes.

Quick answer: the accepted fix

Accepted first step when you can’t receive an SMS verification code: don’t spam “resend,” and don’t remove your phone number or change security settings while codes aren’t arriving. First, confirm strong cellular signal, then check for filtered/blocked messages (Unknown Senders, blocked list, third-party spam filtering). Next, verify the account shows the correct number and country/region. Finally, look for a pattern: if some short-code OTP texts arrive late but specific services never arrive (especially after a number port), it often points to short-code routing or carrier filtering rather than your phone being “broken.”


Why OTP / 2FA texts fail even though normal SMS still works

Verification codes often come from short codes or automated messaging routes that are treated differently than normal texts. A phone can receive messages from friends while OTP delivery fails due to carrier filtering, spam protection, weak reception at the time of delivery, cooldowns after repeated requests, or account number/region mismatches. The safest approach is to confirm which bucket you’re in before you touch account security settings.

Safe checks before you change passwords or remove your phone number

Start with reversible steps: confirm strong cellular signal, check Unknown Senders and blocked lists, and verify the number/country stored on the account. Make a single controlled test request and wait rather than repeatedly tapping “send code.” If some short-code texts arrive delayed but certain apps never deliver, it suggests routing/filtering or service-side restrictions—not something that a factory reset usually solves.

Security tip: never share your verification code

Real support won’t ask for OTPs.

If you receive a code you didn’t request, don’t read it to anyone or paste it into links sent by messages. Missing-code troubleshooting should stay focused on safe checks (signal, filters, number details) and avoid risky steps that could lock you out or expose your account.

Disclaimer: This information is AI-generated and intended for general guidance only. Steps vary by phone model, carrier, and app/service. For exact instructions for your setup, consult a verified expert or the manufacturer’s support site.

Understand what these prompts mean


Getting Started Is Easy

Low-risk diagnosis

Identify whether it’s filtering, signal, cooldowns, or number details—without risky account changes.

Stop “resend code” loops

Learn why OTP and short-code texts can fail even when normal SMS still works.

Account-safe checklist

Focus on reversible checks first so you don’t accidentally lock yourself out of 2FA.

FAQ

Why do I get normal texts but not SMS verification codes?

Verification codes often come from short codes or automated routes that can be filtered differently than regular person-to-person texts. Carrier filtering, spam protection, weak signal, or cooldowns after repeated requests can block or delay OTP messages.

Should I keep pressing “resend code” if nothing arrives?

It’s better to avoid repeated requests. Many services add cooldown timers or temporary holds after too many attempts. Use a single controlled request, wait, and compare conditions like signal and message filtering.

Can a number port or new carrier cause OTP texts to stop arriving?

Yes. After porting, short-code routing and filtering can behave differently than regular SMS for a period. If some OTP messages arrive late but certain services never arrive, routing/filtering is a common explanation.

What’s the safest first step so I don’t lock myself out?

Confirm strong cellular signal, check Unknown Senders and blocked lists, verify the number/country stored on the account, and avoid repeated “resend” attempts. Don’t remove your number or change security settings until you know whether it’s delivery, filtering, or a service cooldown.

Sources

Filed under: Account Access Help

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant