If personal texts arrive but verification codes do not, your phone is not necessarily unable to receive SMS. The missing code may use a different sender, face a carrier restriction, land in a filtered folder, or never leave the service requesting verification. Start by separating these possibilities before changing phone settings.
- • Why a personal text does not prove OTP delivery
- • Look for a filtered message first
- • Ask about the right carrier restrictions
- • One service or several: narrow the fault
- • Account for a recent port, roaming or a second SIM
- • Avoid changes that do not target the problem
- • Give support a useful delivery record
- • Frequently asked questions
- ◦ Are all verification codes sent from short codes?
- ◦ Will allowing premium SMS fix incoming codes?
- ◦ Should I use a public SMS inbox instead?
- • Related troubleshooting guides
Why a personal text does not prove OTP delivery
A friend’s message and a company’s one-time password can travel through different messaging systems. Business-to-person messages are often called A2P SMS. Their sender may be a short code, a normal-length number or a name; formats and support vary by country.
First confirm your test message was actually SMS. A delivered iMessage, RCS chat or WhatsApp message tests a different channel. Even a successful ordinary SMS only confirms that particular delivery, not every business sender.
Look for a filtered message first
Search your messaging app for the service name and inspect blocked, spam and unknown-sender folders. On iPhone, check the filters available in Messages; in Google Messages, inspect the spam and blocked area. Labels depend on app version, language and region.
If you find the code, delivery occurred. Notification or filtering settings are the next issue. Restore only a sender you recognize and verify through the real service; a familiar-looking sender name alone is not proof of authenticity.
Ask about the right carrier restrictions
Ask your carrier whether the affected line has restrictions on incoming business verification messages or short-code SMS. Mention the specific sender if known. Do not ask only whether “SMS works”: personal texts may already work.
Carrier controls differ. Marketing-message preferences, paid premium services and security-code delivery are not interchangeable categories. T-Mobile documents commercial-message blocking as one example; do not assume another carrier uses the same setting.
One service or several: narrow the fault
If only one service fails while other legitimate codes arrive, contact that service about its destination number, supported number types and delivery records. If several unrelated services fail, give your carrier the examples too. This comparison is a diagnostic clue, not proof of who caused the failure.
Respect the resend countdown and request one fresh code after it ends. Repeated requests can trigger service limits or make it harder to match a message to the right attempt.
Account for a recent port, roaming or a second SIM
Tell support if you recently moved your number to another carrier or are roaming. Ask whether routing or short-code support needs investigation; there is no universal waiting period that fixes every case.
With two SIMs, confirm the number shown by the service belongs to the active target line. Selecting another SIM for mobile data or outgoing messages does not redirect an incoming code to that other number.
Avoid changes that do not target the problem
Do not erase an eSIM, reset the phone or copy SMS-centre settings from an online guide as an initial fix. Those changes can create a second problem without addressing this sender’s delivery. Android permissions for sending premium SMS also do not establish that incoming verification SMS is allowed.
Do not reply START, send a paid message or disable all spam protection unless the verified service or your carrier gives instructions relevant to your line.
Give support a useful delivery record
Record the service, target number with most digits masked, country code, carrier, request time and time zone, whether other SMS and codes arrive, and any recent port or roaming change. Include an error message with passwords and codes removed.
The carrier can examine line restrictions and routing; the service can inspect its sending records. Use their official support channels. Never give support a live OTP. If access is urgent, use an already configured alternative sign-in or the service’s official recovery process.
Frequently asked questions
Are all verification codes sent from short codes?
No. A code may come from a short code, a longer number or a named sender. Short-code availability and cross-border behavior differ, so sender appearance alone cannot identify the cause.
Will allowing premium SMS fix incoming codes?
Not necessarily. A permission about sending premium messages concerns a different operation. Ask about receipt of the affected business SMS instead of changing unrelated permissions.
Should I use a public SMS inbox instead?
Public inboxes are unsuitable for private accounts and lasting recovery access. Keep an account tied to a number you control, or follow its official number-change or recovery process.
