What to check first when a message is not working
If a message is not working, start by distinguishing between iMessage, SMS, app-based chat, and email. First, confirm basic connectivity: your device can reach the internet, and the messaging service itself is not broadly down. Next verify the recipient’s contact details and account status. This overview maps likely causes, from carrier issues to account blocks, to platform outages, and gives a prioritized sequence of checks and fixes.
iMessage specific checks and status indicators
Network and account prerequisites
iMessage requires cellular data or Wi‑Fi, a working Apple ID, and activation on your device. Even when your personal hotspot or data is on, carrier restrictions or device settings can block iMessage signaling. Check that iMessage is enabled in Settings > Messages and that you see the ‘IMessage’ status in the same screen.
How to read iMessage status and resolve common failures
Colors and delivery states in Messages are reliable indicators. Blue bubbles mean iMessage; green means SMS. A lack of delivery or a ‘Not Delivered’ notice points to a block, network mismatch, or a suspended service. Key fixes include toggling iMessage off and on, signing out and back into Apple ID, and checking Send & Receive addresses. Below are common indicator combinations and probable causes.
| Indicator or symptom | Verified detail | Source type |
|---|---|---|
| Blue bubble stays on ‘Sending’ | iMessage not activated or network path blocked | Apple support diagnostics |
| ‘Not Delivered’ under a blue bubble | Recipient block, device off, or Apple ID issue | Apple support diagnostics |
| Green bubble (SMS) fails | Cellular plan, carrier block, or device registration problem | Carrier documentation |
App-based messaging: WhatsApp, Telegram, Signal, and Slack
App-based chats fail for connectivity, account, or configuration issues rather than traditional telephony blocks. Check each app’s in-app connection status, verify the contact’s active presence, and ensure time synchronized, as app servers often reject messages with large time drift. Many enterprise environments use app-specific allowlists, so confirm that your org’s policy permits the app’s traffic.
WhatsApp and Signal connectivity diagnostics
Both rely on an active internet connection and phone-number linked accounts. WhatsApp in particular binds tightly to the SIM and number used at install; swapping SIMs or changing devices without re-linking can look like ‘message not working’. Signal usually works immediately if the contact is in your address book and the app can reach its servers.
Slack and workplace app policies
Workspace tools often block external guests, require SSO, or restrict DMs entirely. If org-wide message failures started after a policy update, check admin console logs or ask IT. Internal dashboards may show blocked domains (e.g., WhatsApp, Signal) or required proxy configurations you must use to route outbound app traffic.
SMS and MMS on cellular devices
SMS and MMS failures usually trace to device settings, carrier provisioning, or shortcode blocking. Confirm mobile data is enabled for MMS, airplane mode is off, and you haven’t hit carrier messaging caps. When traveling, verify that data roaming is on even if you are not using data; some carriers disable MMS without it.
Troubleshooting SMS step-by-step
- Toggle Airplane Mode on and off to re-register on the network.
- Check that mobile data and MMS messaging are enabled in Settings.
- Confirm date and time are set automatically to avoid TLS and submission failures.
- Verify you aren’t over your plan’s SMS/MMS limits or per-message size caps.
- Test with another number to isolate recipient-side blocks.
Email and SMTP delivery failures
Email not working often reveals authentication, routing, or rate-limit issues rather than a broken message concept. Failed SPF, DKIM, or DMARC, mismatched reverse DNS, and outbound port blocking are common culprits. If you recently changed hosting, ensure MX records point to the new provider and that the sending IP is not on public blacklists.
Quick email diagnostics
Use a tool to validate DNS records, inspect SMTP logs for bounce codes, and confirm the recipient server isn’t greylisting or throttling you. For enterprise accounts, centralized transport rules and archiving policies can silently drop or quarantine messages, appearing as if the message never left your outbox.
When the problem is on the recipient or platform side
If device, app, and account settings look clean, the issue may be with the recipient or the remote service. Recipients can disable messages, set strict privacy controls, or change contact methods. Platforms may throttle, quarantine, or block content based on reputation, behavior, or compliance. If only one person can’t send or receive, suspect account-level blocks or relationship settings rather than infrastructure failures.
Action checklist: systematic steps when a message is not working
Follow this checklist to methodically isolate cause and apply fixes without unnecessary trial and error.
- Confirm device connectivity (Wi‑Fi/cellular) and run a simple speed test.
- Check the messaging service status page or a third-party outage tracker.
- Verify the specific channel: iMessage, SMS, app chat, or email.
- Review account-level blocks: do not disturb, DMs off, enterprise quarantines.
- Inspect logs or in-app error codes for precise indicators.
- Apply targeted fixes: toggle services, re-link accounts, check date/time, update apps.
- Test with a second device or number to separate user vs. platform issues.
Typical causes mapped by channel
Understanding the most common reasons by channel helps you prioritize checks and avoid repeated misdiagnosis.
| Channel | Likely cause | First action |
|---|---|---|
| iMessage | Not activated, wrong Send & Receive, Apple ID issue | Toggle iMessage and re-check Send & Receive |
| SMS/MMS | Mobile data off, carrier block, roaming settings | Enable mobile data for MMS and check device registration |
| WhatsApp/Signal | SIM/number mismatch, app permissions, network block | Re-link account or check app network permissions |
| Slack/Teams | Workspace policies, SSO, guest restrictions | Verify org admin settings and app permissions |
| SPF/DKIM/DMARC failure, rate limits, port blocks | Check authentication records and SMTP logs |
Technical background on message delivery
Messages travel through multiple layers: application software, operating system services, networks, and remote endpoints. Each layer can introduce failures: local settings (e.g., data disabled), infrastructure routing (firewalls, NAT), or remote policies (content filters, rate limits). Encryption and authentication mechanisms like TLS, SPF, and OAuth can also fail silently if certificates expire or tokens are invalidated. Recognizing where in this stack the symptom appears is the most reliable way to narrow fixes.
When to seek carrier or platform support
If diagnostics point to carrier provisioning (iMessage not activated, SMS/MMS blocked) or platform-side restrictions (app banned, content flagged), contact support with specific diagnostic details: device model, OS version, timestamps, error codes, and screenshots of status indicators. Escalate to enterprise IT when workspace policies or transport rules are involved, since admin console logs are required to identify and release blocked messages.
Status and prevention tips
Recurring message failures often trace to updates that change behavior, device changes, or policy shifts. After OS or app updates, re-check key settings (iMessage turned on, correct Send & Receive, mobile data for MMS). Use diagnostics built into Settings and the service’s status page proactively. Maintaining a simple checklist for each channel reduces future downtime and clarifies whether a problem is local, network, or provider-related.