Tip & Trick
When you block someone, your device's native messaging system (like iMessage on iPhone or SMS on Android) simply won't deliver their messages to you. 🔥 However, third-party apps operate independently of these systems, which is why you might still get messages through WhatsApp, Messenger, or Telegram.
The key difference lies in how these apps handle blocking—some platforms respect device-level restrictions, while others don't, creating a gray area for users who want full control over their communications.
This behavior can be confusing, especially if you're expecting complete silence. For example, if someone blocks you on iMessage but keeps using WhatsApp, their texts will still appear in your app—just not in your standard Messages app.
The same applies to Android users, though some carriers offer additional blocking tools that can help filter out unwanted messages across platforms.
💡 In This Article
- How Blocking Affects Messaging on iPhone vs Android
- Alternatives to Blocking for Controlling Messages
How blocking affects messaging on iPhone vs Android
On iPhones, blocking someone triggers a system-level restriction that prevents iMessage and SMS from delivering to your device. Apple's iMessage protocol uses end-to-end encryption tied to your Apple ID, while SMS messages route through your carrier.
When you block a contact, both systems silently discard incoming messages before they reach your inbox—no delivery receipts or notifications appear. The blocked contact won't even know their message failed to send, creating a seamless "disappearance" of communication.
Android's approach differs slightly. Google's Messages app (for SMS/MMS) blocks messages at the carrier level, but some carriers (like Verizon or T-Mobile) offer additional filtering tools that can block messages even from unblocked contacts.
The key difference is Android's blocked contacts list appears in Settings, while iOS silently suppresses blocked interactions without a visible record. 🔥 For example, if you block someone on Android but they text via WhatsApp (which uses internet data), their message will still arrive—proving third-party apps operate outside native blocking systems.
Read receipts and delivery indicators behave differently post-block. On iPhone, the blue checkmarks (read receipts) disappear entirely for blocked contacts in iMessage, while Android's double ticks (delivery confirmation) remain visible to senders—though messages won't deliver.
This creates a false sense of connection: the sender sees their message as "delivered," but it never reaches you. The technical reason? iMessage's encryption ties receipts to your Apple ID, while Android's SMS protocol lacks this integration.
Third-party apps like WhatsApp or Telegram bypass native blocking because they use separate servers and encryption. When you block someone on your device, these apps don't receive the instruction—only your native messaging system does.
For instance, if you block a contact on iPhone but they message you via WhatsApp, their message will appear in your WhatsApp inbox, complete with read receipts. This happens because WhatsApp's servers don't communicate with Apple's blocking system.
Android adds another layer: some manufacturers (like Samsung) include Samsung Messages, which can block messages independently of Google's Messages app. This creates confusion—blocking in one app might not affect another.
For example, blocking a contact in Samsung Messages won't stop WhatsApp texts, but it might filter SMS from that number. iPhones avoid this fragmentation by using a unified Messages app for both iMessage and SMS.
Here's what most users don't realize: blocking doesn't prevent calls or FaceTime/iMessage requests—only messages. On iPhone, blocked contacts can still leave you a voicemail (which you'll hear), while Android's behavior varies by carrier.
Some carriers (like AT&T) allow blocked callers to leave voicemails, while others (like Sprint) may block calls entirely. The inconsistency stems from how carriers handle blocking at the network level versus device level.
