When WhatsApp Business is not sending messages, the failure sits in one of three places: the phone's connection, the business account or number, or (for API and provider sends) the template, customer-service window or an error from Meta. Identify which layer fails, then fix only that one.
- Identify the product. A message typed in the phone app follows the app checklist; a message from a team inbox, CRM, bot or campaign tool follows the Platform checklist.
- Check the scope. Compare one affected contact with a second consenting contact to see whether one recipient, one template or every send is failing.
- Read the status. A clock icon means the app has not finished the send. For API sends, save the HTTP status, Meta error code and message ID.
- Fix the connection and account state. Test other apps on the same network, switch once between Wi-Fi and mobile data, update the app and read any account notice shown inside WhatsApp Business.
- Check the template and window (API only). Match the approved template name, language and variables, and confirm whether the customer-service window is open.
- Collect evidence before contacting support. Use the checklist near the end of this page.
Start by writing down four facts: which WhatsApp product sends the message, whether one contact or every contact is affected, the visible status or API error, and the time of the last successful send. Those facts determine the next check. Reinstalling the app or resubmitting a template before you know the failing layer can erase useful evidence.
Seeing "content which is not supported in Inbox"? That is a display problem, not a failed send#
The notice "This message contains content which is not supported in Inbox. It is only available to view in the WhatsApp Business app" stands in for a message someone sent that the inbox you are reading cannot display. Meta's webhook reference describes the same situation as an unsupported message: a WhatsApp user sent a message type the Cloud API does not support. Meta's error-code reference lists it as error 131051, "Unsupported message type".
- Open the conversation in the WhatsApp Business app on the phone linked to the number, as the notice says.
- Ask the customer to resend the content as plain text or a standard photo if you need it inside your inbox or CRM.
- Do not troubleshoot your sending because of this notice. Your outgoing messages are a separate check, covered below.
Meta documents the full list of unsupported types in its unsupported messages webhook reference.
WhatsApp Business app vs WhatsApp Business API: which problem are you having?#
The WhatsApp Business app runs on a phone and linked devices. The WhatsApp Business Platform sends through an API, either directly through Meta Cloud API or through a provider. The app shows clock and check icons. The Platform returns a request result, a message ID when accepted, and later delivery status through webhooks.
If you are unsure, ask where the message was composed. A message typed in the phone app follows the app checklist below. A message sent from a team inbox, campaign tool, CRM, bot, or custom integration usually follows the Platform checklist. Keep Meta's WhatsApp Business Platform documentation and the WhatsApp Help Center beside your test notes.
WhatsApp Business app: 5 reasons messages fail + fixes#
1. The message is still pending on the phone#
A clock icon means the app has not completed the send. Check whether other websites and apps load, switch once between Wi-Fi and mobile data, and confirm the phone's date and time are automatic. Reopen WhatsApp Business and send one short message to a consenting test contact. Do not delete the original message until you have recorded its time and state.
2. One recipient is unavailable#
A message can leave your phone without reaching the other device immediately. Compare one affected contact with a second consenting contact. Confirm the number includes the correct country code and ask the customer to message the business first if appropriate. If only one recipient fails, avoid changing account-wide settings. Use the broader WhatsApp delivery checklist to separate sender, recipient, and service conditions.
3. The business account or number has a restriction#
Use the notice shown inside WhatsApp Business as the source of truth. Record the exact wording, review the account's recent sends and opt-in records, and use only the appeal or support path shown in the app or official Help Center. Do not create replacement accounts to avoid a restriction, pay an unofficial recovery service, or share a verification code. Meta controls the review outcome and timing.
4. A broadcast list does not reach part of the audience#
App broadcast behavior is not the same as a Business Platform campaign. Verify the app's current broadcast eligibility, recipient relationship, and list rules in WhatsApp's own help surface. Test a small consented segment, remove stale numbers, and record who receives the test. If you need managed templates, delivery statuses, team ownership, and larger controlled sends, evaluate the Business Platform instead of trying to stretch an app list beyond its intended workflow.
5. The app or linked-device session is stale#
Update WhatsApp Business through the phone's official app store. Check available storage, background-data permissions, and whether the linked device still appears under Linked devices. Log out only the affected linked session first. Back up required business data before reinstalling the phone app, because reinstalling is a last step, not a first diagnostic.
WhatsApp Business API: 7 reasons messages fail + fixes#
1. The message type is not allowed for the current conversation state#
For each failure, record who last messaged, when they messaged, the message type, and whether an approved template was used. Customer-service-window and template rules change which payloads are eligible. Check the current Cloud API send-message guidance rather than relying on an old screenshot or a hard-coded rule in your CRM.
2. The template name, language, status, or variables do not match#
Read the live template record in WhatsApp Manager or through the API. Match the approved template name and language exactly. Check every required header, body, button, and parameter in order. Validate that example and production values use the expected format and that no variable is empty. If the template is paused, rejected, or still under review, use the status Meta shows and follow the official template guidance before resubmitting.
3. The phone number or business asset is not ready#
Confirm the sending number, WhatsApp Business Account, app, token, and business portfolio belong to the intended environment. A staging token, removed system user, expired token, incomplete registration, or wrong phone-number ID can make a valid-looking request fail. Test the number and token with the smallest read operation your setup supports before sending again.
4. The API response or webhook contains the real reason#
Save the HTTP status, Meta error code, error title, error detail, trace ID, provider request ID, message ID, and timestamp. Then match the code against Meta's current Cloud API error-code reference. An accepted request is not the same as delivered: keep the later sent, delivered, read, or failed webhook event with the original message ID.
5. Quality or messaging limits affect the sender#
Review the number's current quality and messaging state in WhatsApp Manager. Look for a recent change in recipient blocks, reports, opt-in source, audience targeting, template content, or sending pattern. Pause the segment that created the problem, fix consent and relevance, and resume with a small test. Do not describe a current account limit from memory; record the value shown for that number and date.
6. Permissions, scopes, or provider configuration changed#
Check the token owner, required permissions, webhook subscription, provider connection, and any recent app, system-user, or business-asset change. Rotate a credential only after you know which credential is failing. If a provider sits between your app and Meta, compare the provider request ID with the Meta response and ask for the unmodified error details.
7. The payload, media, or destination data is invalid#
Reduce the request to one consenting test recipient and the smallest valid text or approved-template payload. Confirm the destination number format, JSON types, media URL accessibility, supported file type, and file limits. Add fields back one at a time. This isolates malformed data from account-wide problems and produces a minimal request that support can reproduce.
A 10-minute evidence checklist before contacting support#
- Product: Business app, Cloud API, or provider.
- Affected scope: one contact, one template, one number, or every send.
- Exact UTC timestamp and timezone.
- Phone-number ID and WhatsApp Business Account ID, without exposing tokens.
- HTTP status, error code, trace or provider request ID.
- Message ID and the latest delivery webhook.
- Template name, language, and live status where relevant.
- Screenshot of the official account notice with private contact data removed.
- Last known successful send and the change made afterward.
- One minimal reproducible test using a consenting number.
Use official WhatsApp support paths and redact customer content, access tokens, verification codes, and unrelated personal data. A compact evidence packet is more useful than a long description without identifiers.
Prevent the next send failure#
Keep a dated owner for templates, tokens, phone numbers, webhooks, consent records, and delivery alerts. Monitor failed status events by number and error code. Test one template and one service reply after connection changes. For campaign planning, review the current Business Platform rules and pricing model. If your team needs one place to review messages and failures, compare the shared inbox workflow and keep automatic sending behind explicit approval rules until the setup is stable.
