You know the text was sent. The other person insists they replied. Maybe it was a confirmation, an address, a pickup update, or a customer message you needed an hour ago. But your phone stays quiet, and the problem gets oddly specific. Everyone else can text you just fine. Just that one person can't seem to get through.
That kind of failure is frustrating because it feels random, but it usually isn't. Texting looks simple on the surface, yet several systems sit underneath it: your phone, their phone, iMessage or RCS, carrier routing, spam filtering, and sometimes the business platform doing the sending. When one link in that chain breaks, you end up not receiving texts from one person while everything else appears normal.
Texting is too central to modern communication for this to be a minor issue. Americans exchanged nearly 2.2 trillion SMS and MMS messages in 2024, according to CTIA's 2025 Annual Survey. At that scale, even a small delivery problem affects a huge number of conversations.
Why Is Just One Person's Texts Not Coming Through
The most confusing part of this issue is how narrow it is. If all texts stopped arriving, you'd assume your phone, SIM, or account had a broad problem. But when it's only one person, people often jump to the wrong conclusion. They think they've been blocked, the sender is mistaken, or the phone is glitching in some vague way.
Usually, the breakdown is more specific than that. A single conversation can fail because the contact entry is corrupted, the thread is stuck between iMessage and SMS, the sender's number was flagged by a carrier filter, or one side is using a messaging setup that isn't falling back correctly. The symptom feels personal. The cause usually isn't.
This tends to trip people up in two situations:
- Personal conversations with mixed devices: One person uses an iPhone, the other uses Android, and the thread gets trapped between iMessage, SMS, or RCS behavior.
- Business texting from one sender: A customer receives messages from friends and family but never gets reminders, promos, or follow-ups from a particular business number.
Missing one person's texts can look like a relationship problem, when it's really a routing problem.
The stakes can be small or serious. Sometimes it's just a missed "running late" message. Sometimes it's a one-time password, appointment reminder, delivery update, or support reply. For businesses, one broken sender-recipient path can trigger support tickets, missed appointments, and the false impression that the customer is ignoring outreach.
Practically speaking, when you're not receiving texts from one person, don't treat it as one mystery. Treat it as a short list of likely failure points. That changes the process from guesswork to diagnosis.
Your Personal Device Troubleshooting Checklist
Start with your own phone. It sounds basic, but that's usually how the fastest wins happen.
Check the obvious settings that aren't actually obvious
A lot of people only check signal bars and stop there. Go deeper.
- Blocked contacts: Confirm the number isn't blocked. This is more common than people think after spam cleanup or accidental taps. On iPhone with iOS 26, go to Settings > Privacy & Security > Blocked Contacts (Apple). On Android, check Google Messages > profile picture > Spam & blocked (Google) and the Phone app's blocked numbers.
- Message filtering: On some phones, unknown senders or filtered messages can get pushed out of the main inbox. On iPhone, tap the Filters button in Messages and check Spam and Unknown Senders (Apple). On Android, look in Spam & blocked.
- Contact number format: If the number is saved oddly, delete it and re-enter it in a clean format. Badly saved contact records can cause one-thread problems that look like network issues.
- Default messaging app: If you've switched between apps, your phone may not be using the app you think it is.
One iPhone detail matters when a single person seems blocked and you never blocked them: Apple suggests checking whether that contact shares a phone number or email address with someone you did block (Apple Personal Safety guide). A block also applies on every Apple device signed in to the same Apple Account.
If your iPhone is also acting strange with alerts in general, Apple's guide to missing Messages notifications can help you rule out broader notification behavior (Focus, Apple Watch, muted conversations) before you chase a text-specific cause.
If iPhone and Android are mixed, check iMessage fallback first
This is one of the biggest culprits in mixed iPhone and Android conversations. Apple's own first step for messaging problems is to turn iMessage off and back on (Apple Support), and in one Apple Community thread about texts missing from a single Android contact, turning iMessage and FaceTime off, restarting, and turning them back on is what fixed it.
What to do on iPhone:
- Turn iMessage off
- Power the phone off and back on
- Turn iMessage back on
- Wait briefly for it to re-register
- Ask the sender to text again
This forces the phone to re-sync with Apple's messaging registration. If the thread got stuck trying to use the wrong path, this often clears it.
Practical rule: If the missing texts are from one Android user and you have an iPhone, test iMessage before you reset anything else.
Android checks that actually matter
On Android, especially when one contact is affected, the messaging app itself is often the problem.
Try this sequence:
- Clear cache for the Messages app: This removes temporary junk without fully wiping everything.
- If needed, clear app data: This is more disruptive, so only do it if simpler steps fail.
- Update the messaging app: Old app versions can create odd thread behavior.
- Switch default app to Google Messages: If you're using a carrier-branded or manufacturer messaging app, test with Google Messages instead.
The issue can also be thread-specific. Delete the conversation after saving anything important, then have the sender message you again. If the thread database entry was damaged, a clean restart helps.
A similar pattern shows up when a phone says messages won't send at all. If you're seeing both sending and receiving oddities, this guide on message not sent troubleshooting is useful for separating app issues from network issues.
Quick device-side reset list
Use this as a fast pass before calling anyone:
| Check | Why it matters |
|---|---|
| Restart the phone | Clears temporary radio and app glitches |
| Toggle Airplane Mode briefly | Forces a fresh network handshake |
| Delete and re-add the contact | Fixes bad contact/thread records |
| Check blocked numbers | Prevents silent filtering on your own device |
| Confirm default messaging app | Avoids app conflict issues |
| Update iOS or Android apps | Removes known software bugs |
If none of that changes anything, stop repeating the same restarts. At that point, the issue is often beyond your phone.
Investigating Carrier and Network Problems
Your phone can be perfectly fine while one sender's texts still never arrive. That usually points to the path between carriers, or to filtering on the sender's side.
SMS delivery is not a simple point-to-point handoff. Carriers screen traffic, apply spam rules, and treat business messaging differently from person-to-person texting. A message can be accepted by the sender's app, then filtered or delayed before it reaches you. That is why one friend, one business, or one school alert system can fail while every other text works normally.
This matters even more when the missing sender is a business. Many companies send through application-to-person routes, not a normal handset. If that traffic is poorly configured, uses risky content, or lacks proper registration, carriers may suppress it. That is one reason business owners often ask why texts don't deliver in the first place.
What carrier filtering looks like in practice
Carrier-side problems rarely look clean or consistent. The sender may see "sent." You still receive nothing.
Common patterns include:
- A direct text from one number never arrives, but calls from that number do
- Plain text gets through, while messages with links, coupons, or appointment language do not
- The issue shows up only on certain carriers
- Personal texts from a staff member arrive, but automated reminders from the business number fail
That last pattern is a big clue. Consumer troubleshooting alone will not explain it. Sender reputation, content filtering, and business registration often do.
For business senders in the US, A2P 10DLC registration affects deliverability directly. Messaging providers can block business texts sent from unregistered local 10-digit numbers; Twilio, for example, has rejected them since September 2023 (Twilio). If a company recently started texting from a local number without proper setup, its texts may never reach you. Some organizations work around this poorly by pushing everything through one number, which raises complaint risk. Others use alternatives like ringless voicemail for reminders that do not need a live text thread, especially when SMS delivery is unreliable.
Ask better questions before calling support
Do not ask only, "Did you send it?" Ask questions that identify the sending path.
- Was the message sent from a personal phone or a business platform?
- Did the sender recently change carriers, SIMs, or phones?
- Was the message plain text, or did it include a link, image, or promo wording?
- Do their texts fail only to you, or to other recipients too?
- If they are a business, are they using a registered texting number or shared software number?
If the sender recently moved to a different device or carrier and service behavior changed at the same time, line provisioning may be part of the problem. If the phone is locked to its old carrier, the carrier that sold it handles unlocking; the FCC's cell phone unlocking guide explains the rules.
A short decision table
| Situation | Most likely issue |
|---|---|
| Only one business number fails | Carrier filtering, sender reputation, or A2P 10DLC setup issue |
| One friend's texts fail after a carrier or phone change | SIM provisioning, account routing, or sender-side line problem |
| Messages fail only when they include links | Content filtering |
| Problem appears only while traveling or roaming | Carrier routing or temporary network issue |
One clean test saves time. Ask the sender to text you from a different number, or have the same business send the message from another route. If that second message arrives, the problem is tied to the original sending path, not your phone.
A lot of one-person text failures are really sender trust failures. The carrier does not like the source, the content, or the registration status, so the message never makes it through.
Advanced Fixes and Definitive Testing Methods
Once the easy checks fail, stop making random changes. Run controlled tests.
Rebuild the contact and thread
This sounds too simple, but it solves a surprising number of one-person failures.
Do it carefully:
- Delete the existing conversation thread.
- Delete the contact card.
- Recreate the contact with the number entered cleanly.
- Start a fresh text from the newly saved contact.
- Ask them to reply with a plain text message first. No photo, no link.
This clears out old thread data, duplicate number entries, weird country code formatting, and name-to-number mismatches.
Test the path, not just the phone
A good troubleshooter isolates variables one by one.
Try these tests:
- Use a different sender number: Ask the person to text you from another phone. If that arrives, their original number is the issue.
- Create a group text with a third person: If their message appears in the group but not in your direct thread, the one-to-one thread is likely corrupted or filtered.
- Send plain text only: No links, no images, no signatures. This helps reveal content filtering.
- Swap apps on Android: If the sender or receiver uses a nonstandard SMS app, move temporarily to Google Messages.
- Check another device on the same account: If you use tablet syncing or desktop messaging, confirm the text isn't landing somewhere else.
Change one variable at a time. If you change five things together, you won't know what actually fixed it.
Watch for app conflicts and sync confusion
Third-party apps don't usually block SMS directly, but they do create confusion. People reply in WhatsApp, Messenger, Signal, or a synced desktop client and assume they're using the same channel. Meanwhile, the actual SMS thread remains broken.
A common false alarm is a "missing text" that was really a notification problem. The message arrived, but it didn't alert, didn't badge, or got buried in filters. Search the sender's name and number inside the messaging app, and check the Spam and Unknown Senders folders, before deciding the text never landed.
If you're still stuck, collect facts before calling support:
- exact sender number
- approximate time of the missing message
- whether the sender saw "sent" or "delivered"
- whether a message from another number works
- whether the issue follows you across apps or devices
That gives carrier support or device support something actionable. "I'm not receiving texts from one person" is the symptom. The tests above tell them where to look.
A Guide for Businesses on Ensuring Text Deliverability
A customer says, "I get texts from everyone else. Just not from your business." At that point, the problem may have nothing to do with their phone. It often starts with how your messages are sent, registered, and filtered before they ever reach the handset.
Consumer troubleshooting only gets you so far. A business sender has to account for carrier rules, message classification, consent records, and reputation. That is the gap many guides miss. A customer can receive every personal text on time and still never see your reminder, follow-up, or order update because business traffic is screened differently.
The sender often owns the problem
When a business sends from an unregistered number, carriers and messaging providers can throttle, filter or reject the traffic outright. Twilio, for example, rejects texts from unregistered US 10DLC numbers with a specific error code (Twilio). The customer sees nothing at all, which looks exactly like "I never got your text."
The business side of SMS has changed. If you send any meaningful volume over a local long code, registration is not optional busywork. It affects throughput, trust, and whether your messages get passed along or held back. For teams using U.S. long-code texting, 10DLC compliance requirements directly affect deliverability.
What improves business delivery
Start with the sending setup before blaming the recipient's device.
- Register the correct traffic type: Promotional campaigns, appointment reminders, support updates, and review requests should go through a properly registered A2P path, not a personal-looking line used like a regular phone.
- Clean your contact data: Bad numbers create false troubleshooting trails and increase failure rates that can hurt sender reputation over time.
- Keep clear opt-in records: If someone opted out, the issue is consent, not deliverability. Treat those as separate problems.
- Reduce filtering triggers: Repetitive copy, link-heavy messages, URL shorteners, aggressive sales language, and sudden volume spikes can all raise carrier suspicion.
- Match content to the campaign: Transactional traffic usually performs better when it stays transactional. Mixing promos into reminders is a common mistake.
- Watch results by carrier: If Verizon performs well and T-Mobile does not, that is useful diagnostic evidence. It often points to registration, content, or routing issues.
In other words, deliverability is an operational discipline, not just a send button.
Test like an operator, not just a marketer
The fastest way to diagnose this problem is controlled testing. Send the same plain-text message to a small set of numbers across different carriers. Then change one variable at a time: the number type, the copy, the link, the sending volume, or the platform route. If failures cluster around one carrier or one message format, you have a real lead.
Keep test cases simple at first. No image. No shortened link. No promo language. Once a plain appointment-style message gets through reliably, add complexity back in carefully. That saves hours of guessing.
Where ringless voicemail fits
SMS should not be your only path for time-sensitive outreach. If a customer is not receiving business texts reliably, ringless voicemail can work as a backup for reminders, callbacks, overdue payment notices, event updates, and similar messages where timing matters.
It is not right for every use case. Some customers prefer text, and some issues require a live call. But from an operations standpoint, having a second channel matters. When carrier filtering or registration problems interrupt SMS, ringless voicemail gives the business another way to reach the customer without depending on a single message path.
For healthcare, finance, and other regulated use cases, compliance and deliverability need to be managed together. Use a messaging setup that fits the rules for your industry, keep content appropriate to the channel, and review delivery failures as both a technical issue and a policy issue.
Frequently Asked Questions About Missing Texts
A few edge cases come up all the time, especially after you've tried the common fixes.
If the sender sees Delivered, why didn't I get it
"Delivered" doesn't always mean "displayed on your screen." It can mean the message reached a service layer, device queue, or carrier handoff point. Notification issues, filtering, thread corruption, or sync problems can still prevent you from seeing it normally. Our guide to delivery status notifications explains what each status means.
Could the sender's phone type be the problem
Yes. Mixed-device conversations are a common trouble spot, especially when iPhone messaging has to fall back to SMS or RCS for Android users. Older phones, flip phones, or unusual default apps can also complicate delivery behavior. If the missing texts are photos, see how to send a picture by text message for MMS limits.
Can low battery or a powered-off phone cause permanent message loss
Usually it causes delay, not permanent loss. But if there are account issues, storage problems, expired retries, or filtering in the chain, a message may never show up later. That's why a resend test matters.
What should I say to my carrier
Keep it concrete. Give them the sender's number, the date and approximate time of missing texts, whether it happens only with that sender, and whether test messages from a different number succeed. Ask them to check for blocking, spam filtering, or line provisioning issues.
Should I just switch to another app
Only after you identify whether the issue is SMS-specific. If this one relationship already relies on WhatsApp, Signal, or Messenger, using that app may be the fastest workaround. But if the problem involves business messages, verification codes, or appointment reminders, you still need the SMS path fixed.
Why am I not receiving text messages at all?
When no texts arrive from anyone, check the basics first: signal, Airplane Mode, that your phone line is on, and free storage (Apple, Google). Then check whether you recently switched between iPhone and Android, because an old iMessage registration (Apple) or RCS registration (Google) can capture your texts.
Why can I text everyone but one person?
The problem is usually on their side of the conversation: they blocked the number by accident, your texts land in their Spam or Unknown Senders folder, or their phone still has an old iMessage or RCS registration. On iPhone, a blocked sender gets no notification, so you can't tell for sure from your side (Apple). Ask them to check the places in the infographic above, or reach them another way.
Why am I not getting texts from one person on iPhone if they're not blocked?
Check three places in Messages: the Filters button > Spam, Filters > Unknown Senders, and whether the conversation has Hide Alerts turned on. If they text from a number that isn't in your contacts and Screen Unknown Senders is on, every new text from them goes to Unknown Senders until you tap Mark as Known (Apple). If they recently left iPhone, they need to deregister iMessage.
Why can I send texts but not receive them?
On iPhone, open Settings > Apps > Messages > Send & Receive and make sure your phone number is selected, not only your email (Apple). If you moved from iPhone to another phone, deregister iMessage. On Android, make sure Google Messages is your default texting app and that your storage isn't full (Google).
Does blocking someone on iPhone also block them on my iPad and Mac?
Yes. Apple says a block applies on all Apple devices signed in to the same Apple Account, and a contact blocked in Messages is also blocked in Phone, FaceTime and Mail (Apple). If someone's texts are missing on every device, check the blocked list once in Settings > Privacy & Security.
If your team depends on text messaging, voice, and ringless voicemail to reach customers consistently, Broadcast gives you one place to manage compliant outreach across channels, improve deliverability, and build follow-up sequences that don't rely on SMS alone.
