A message can be sent without being delivered. For personal WhatsApp, check connectivity and the app before changing account settings. For business API messages, use the returned status and error code to choose the fix. Template approval, business verification and a badge do not guarantee delivery to every recipient.

Read the status before trying a fix

• Clock: the app has not sent the message yet. Start with your connection.
• One grey tick: sent, but not delivered. It does not prove that the recipient blocked you.
• Two grey ticks: delivered, not necessarily read.
• Blue ticks: read status where read receipts apply. Missing blue ticks are not proof of failed delivery.

Muting a chat or disabling notifications does not itself block delivery. For API campaigns, do not translate a dashboard label into a diagnosis without checking the underlying event. Meta’s message-sending documentation and Meta’s message webhook examples explain why an accepted send request is not the same as a delivered message.

If you are using the WhatsApp app

1. Check whether other apps can access the internet. Try another trusted network if needed.
2. Update WhatsApp from the official app store, then close and reopen it.
3. Restart the device and check that it has enough storage.
4. Check the recipient number and whether the issue affects one contact or everyone.
5. If it persists on a managed network, ask the network administrator to check access. Do not bypass workplace security controls.

A recipient can be offline or unavailable. WhatsApp deliberately limits what you can infer about blocking from profile details, last-seen information or a single tick. Do not keep contacting someone through new numbers to test whether they blocked you.

Before clearing app data or reinstalling, confirm that your chats have a recoverable backup. Those steps can lose local information and are not the first response to one undelivered message. The older WhatsApp Web help reference in this guide is not a current instruction to bypass network filtering. For customer entry points, see our click-to-chat guide.

If a business campaign is failing

Choose a failed message and collect its message ID, timestamp, template name, language, category and returned error details. Check whether failures cluster around one template, recipient group or sending number. Then use the Meta error-code reference rather than applying the same retry to every failure.

• Template or parameter error: confirm the exact approved template name, language and required variables. Fix the request before resending.
• Outside the service window: use an eligible approved template rather than a free-form message. The window runs for 24 hours after the latest user message.
• Paused or disabled template: inspect its current status in WhatsApp Manager and follow the documented recovery process. Do not assume a fixed pause duration from an old blog.
• Account, number, payment or permission error: inspect the setting named by the error and have the account owner resolve it.
• Rate or throughput error: follow the applicable documented limit and retry guidance for that code. Do not invent a universal batch size.
• 131049: treat it as healthy ecosystem engagement protection. Use the 131049 recovery guide instead of an immediate retry loop.
• 131050: Meta says the recipient has stopped marketing messages from your business. Do not retry that marketing message.

A business verification process, phone-number registration and a visible account badge are different things. None overrides recipient choices or guarantees delivery. Do not use an old universal “250 messages” cap as your account’s current allowance. Check the limits and account status shown for your own setup.

Review the WhatsApp Business API setup checklist for India for account, number and webhook prerequisites. This page diagnoses failures; the setup guide owns the implementation checklist. Our business account guide and Business App and Platform overview explain the surrounding account concepts.

Make retries deliberate

Keep temporary transport failures separate from recipient opt-outs, policy restrictions and invalid requests. For a retryable error, use the current code-specific guidance, a maximum retry count and a stop condition. Record each attempt so a delayed event cannot trigger duplicate sends.

There is no official universal “delaySendMessagesMilliseconds” setting that fixes Cloud API delivery. Nor is there a universal per-message delay, file-size delay or batch of 100–200 contacts that makes every campaign safe. Infrastructure throughput and marketing eligibility are separate constraints.

Before any retry, recheck whether the customer purchased, paid, opted out or no longer needs the update. Follow the WhatsApp Business Messaging Policy and your channel-specific permissions. For cross-channel requirements, see WhatsApp and email compliance.

When email fallback helps

A failed order notification may need another permitted route. Email can carry the details if the address is valid, the customer is eligible and your suppression rules allow it. Do not automatically copy a promotion to every available channel after a WhatsApp failure.

CampaignHQ is a Meta Tech Partner for Email + WhatsApp retention automation, with AWS supporting the infrastructure. Its CampaignHQ’s WhatsApp product page describes journeys, templates, a shared inbox and reporting. Ask for a demonstration using your actual failure event and consent rules; no provider can promise to bypass Meta’s restrictions. See customer-journey design and the API overview for implementation context.

What to send support

Include a redacted request, returned error code and details, message ID, timestamp and time zone, template name and language, number ID, and whether the failure is isolated or widespread. State which checks you already completed. Never paste access tokens or an unredacted customer list into a public forum.

After the fix, compare attempted, sent, delivered, read and failed messages separately. Then check replies, opt-outs and verified customer outcomes. Better delivery alone does not prove better retention. If the platform cannot expose the evidence you need, use the WhatsApp platform shortlist for Indian teams to evaluate alternatives, not as a substitute for diagnosing the error.

FAQs

Does one tick mean I am blocked?

No. It means sent but not delivered. Recipient availability and connection issues can produce the same status; do not infer blocking from that signal alone.

Can an approved template still fail?

Yes. Approval does not override account restrictions, recipient choices, limits or an invalid send request. Read the status event and error details.

Does a business badge improve delivery guarantees?

A badge is not a delivery guarantee. Verify your account prerequisites and applicable limits separately from any visible verification badge.

Should I resend every failed message?

No. Correct invalid requests, respect opt-outs, and apply code-specific retry guidance only to eligible failures. Stop when the message is no longer useful.

Can CampaignHQ guarantee delivery?

No platform can override Meta or recipient restrictions. CampaignHQ can support an operational workflow for templates, journeys and reporting; validate the exact recovery branch in a demo.

Last updated: September 15, 2026

Written by CampaignHQ Team