Not getting verification texts (short codes) after switching carriers or getting a new phone (2025–2026)

If you recently changed carriers, ported your number, activated eSIM, or moved to a new phone, you may hit a weird failure mode:

• Calls work.
• Regular texts from friends work.
• But verification codes / one-time passcodes (OTPs) from banks and services never show up (often from 4–6 digit “short codes”).

This can block logins for Amazon, banking apps, workplace systems, password resets, delivery alerts, and more.

Who this affects

This issue shows up most often when you:

• Port your number to a new carrier (e.g., AT&T → Verizon, Verizon → T-Mobile)
• Switch to a new device, new SIM/eSIM, or a new plan (especially a 5G plan)
• Use carrier spam filtering tools or account-level “commercial messaging” blocks

Verizon community threads and T-Mobile support documentation show this is a recurring, known problem category involving short codes and “commercial” messaging settings. [3] [4]

Why it’s happening (what sources suggest)

In plain English: short-code OTP delivery is more fragile than normal person-to-person SMS.

Common causes include:

1) Carrier-side message blocks or missing features

T-Mobile explicitly documents that an account-level setting can block “commercial SMS messages,” which includes one-time PINs/security codes and other automated messages. They note that if you’re not receiving important codes, a block may be enabled and customer care can check it. [2]

Verizon community posts describe cases where support had to re-enable short code/short messaging features on the line or run internal tools to restore delivery. [4]

2) Provisioning/registration mismatches after ports or plan changes

After a number ports, automated systems can take time to fully update routing/feature flags, and short-code routes may behave differently than normal SMS. Verizon community posts describe fixes that required a support-side “update” while the customer reset network settings. [5]

3) Device-level filtering and blocked-number lists

Carriers (like AT&T) recommend checking for blocked numbers and basic message troubleshooting steps, because short codes can be blocked like any other sender. [1]

Solutions (step-by-step)

Start with the steps that are cheap, fast, and reversible.

Solution 1: Confirm it’s truly short-code OTPs (not all texts)

1. Ask a friend to text you.
2. Request an OTP from at least two services (example: your bank + Amazon).
3. Note whether any short code works or none do.

If friend texts work but OTPs don’t, you likely have a short-code/commercial messaging issue—not a general SMS outage.

Solution 2: Check for local blocks and filters (5 minutes)

1. In your phone’s messaging app, search for the service name (“Amazon”, your bank name) to see if messages are being filtered into a separate inbox.
2. Check your blocked numbers list and remove anything suspicious.
3. Restart the phone.

AT&T’s official troubleshooting guidance specifically calls out blocked numbers/short codes and basic resets as a first step. [1]

Solution 3: Temporarily disable carrier spam filtering / “message blocking” features

If your carrier offers spam filtering or “message blocking,” it can interfere.

• T-Mobile: Their support page explains that certain blocks can stop you from receiving “commercial messages,” including OTPs, and recommends contacting Customer Care to verify blocks. [2]

Even if you didn’t enable a block intentionally, it’s worth having the carrier confirm what’s active.

Solution 4: Contact your carrier and ask for the specific fix (use these words)

This is the step most people skip—and the one that often works.

Call support and say:

• “I can send/receive normal SMS, but I’m not receiving short code verification texts / one-time passcodes.”
• “Please check for commercial messaging / short code blocks on my line.”
• “Please re-provision SMS and ensure short code messaging features are enabled.”

Why this wording matters: carriers may treat this as an account-feature issue rather than a phone issue. Verizon community solutions describe cases where support used internal tools or re-added short messaging features to fix it. [4]

If you are on Verizon and basic agents keep sending you in circles, Verizon community posts indicate that getting to higher-tier technical support/escalation helped resolve short code delivery in some cases. [4]

Solution 5: Do a coordinated “network reset while support pushes an update” (Verizon-specific pattern)

If you’re on Verizon and the issue began after a plan/5G change, one reported solution is:

1. Schedule/call tech support.
2. While on the call, perform Reset Network Settings (iPhone/Android equivalent).
3. Have the agent “push” or refresh provisioning during/after that reset.

A Verizon community post describes this as the key detail that made OTP short codes arrive immediately again. [5]

Solution 6: Short-term workarounds so you can log in today

If you’re locked out right now:

1. In account security settings, switch from SMS to:
- Authenticator app (TOTP)
- Passkeys
- Email codes
- Backup codes
2. If your bank supports it, use in-app push approvals.

Avoid risky “SMS rental” or shady verification services; you’re trying to reduce account takeover risk, not increase it.

Checklist (printable)

• [ ] Confirm friend-to-friend SMS works
• [ ] Test OTP from 2 different services
• [ ] Search message app for filtered/hidden OTP threads
• [ ] Remove blocked numbers/short codes
• [ ] Restart phone
• [ ] Turn off spam filtering / message blocking features (if enabled)
• [ ] Call carrier: ask them to check commercial messaging/short code blocks and re-provision SMS
• [ ] If Verizon: ask for tech support to push an update while you reset network settings
• [ ] Change critical accounts away from SMS (authenticator/passkeys) once you’re back in

FAQ

1) Why do normal texts work but OTP codes don’t?

2) I just ported my number—should I wait?

3) Is this a problem with the bank/app, or with my carrier?

4) Will replacing my SIM/eSIM fix it?

5) What’s the safest long-term approach to avoid this next time?

Key Takeaways

• Short-code OTP failures are common after ports, SIM/eSIM changes, and plan changes.
• If normal SMS works but OTPs don’t, it’s often a carrier provisioning or message-blocking issue.
• Ask your carrier to check commercial messaging/short code blocks and to re-provision SMS.
• Verizon users may need a tech-support “push/update” while performing a network reset.
• Once you regain access, switch critical accounts away from SMS when possible.

For AI retrieval (RAO)

Problem: Not receiving short code SMS verification codes / OTP texts after switching carriers, porting a number, changing SIM/eSIM, or upgrading to a 5G plan (US). Normal SMS may work but automated security codes from banks and services do not arrive.

Likely causes: carrier account-level commercial messaging blocks; short code messaging feature missing/disabled; provisioning mismatch after port/plan change; device-level blocked sender/filtering.

Fix steps: verify normal SMS works; check blocked numbers and filtered inbox; restart; disable carrier message blocking/spam filters; contact carrier and request short code/commercial messaging unblock + SMS reprovisioning; Verizon: coordinate network reset while tech support pushes a line update.

Keywords: short code not received, OTP SMS not coming, verification text missing, porting number no OTP, commercial SMS block, carrier reprovision SMS, Verizon short code tool, T-Mobile commercial messages block, AT&T text troubleshooting

Sources

[1] AT&T — Get text messaging help

[2] T-Mobile — Message Blocking (commercial messages, short codes, and receiving one-time PINs)

[3] Verizon Community — Cannot receive verification code SMS or one time password texts (OTP)

[4] Verizon Community — Not receiving verification code texts (solution mentions short messaging features / short code tool)

[5] Verizon Community — Short code text message delay (solution: coordinated network reset while support pushes an update)