# Failed Messages

## Failed Messages Tab

This tab displays a record of all messages that could not be successfully delivered to recipients. These messages come from various sources, such as automated integrations or campaigns. 

<figure><img src="https://789614814-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvCr7uCTpZRGEF8A48OOJ%2Fuploads%2FmWCFgKJzZXFywLbBe5TJ%2FScreenshot%202025-09-08%20164456.png?alt=media&#x26;token=1b4185fe-7673-4664-8de6-0a6e1546e2a8" alt=""><figcaption></figcaption></figure>

Each entry in the log provides critical information, including:

* **Template Name:** Identifies the specific message template that failed to send.
* **Contact Name & Mobile Number:** Details about the intended recipient.
* **Sender Module:** The source of the failed message (e.g., "Integration," "Campaign").
* **Error Message:** Provides a brief reason for the failure (e.g., "This message was not delivered to help maintain a healthy engagement ecosystem. \[Meta chose not to deliver.]").

This tab is essential for troubleshooting and monitoring the health of your communication flows.

## All Failed Messages Tab

This tab is very similar to the 'Failed Messages' tab, but it likely provides a more comprehensive, centralized log of all failed messages, regardless of the source. This shows additional columns, such as **'Error Code'** and a more detailed **'Error Message'**, which gives a deeper insight into the technical reason for the failure.

<figure><img src="https://789614814-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvCr7uCTpZRGEF8A48OOJ%2Fuploads%2FSizCbjAeM0tAPXOQxitR%2FScreenshot%202025-09-08%20164517.png?alt=media&#x26;token=9cc34f5d-d4be-4879-afc7-8ac0d790e8cf" alt=""><figcaption></figcaption></figure>

The key difference is in the scope of the data. While the 'Failed Messages' tab may present a summary or a subset of recent failures, the 'All Failed Messages' tab likely offers a complete, unfiltered history of all messages that have failed over time, often including more technical details for developers or support teams to use for advanced debugging.

## Common Reasons for Failed Messages:

1. **User Opt-Out:** The recipient has opted out of receiving messages from your business.
2. **Invalid Phone Numbers:** The provided phone number is incorrect or not registered with WhatsApp.
3. **Message Template Rejection:** The template used does not comply with WhatsApp's messaging guidelines or was not approved.
4. **Quality Rating Issues:** A low quality rating on your WhatsApp Business account may limit your ability to send messages.
5. **Quota Limit Exceeded:** Sending messages beyond your broadcast or daily messaging tier limit.
6. **Recipient's Phone Unavailable:** The recipient's phone is turned off, or they are not connected to WhatsApp.
7. **Network Errors:** Temporary network issues or downtime with WhatsApp's servers.

## How to Monitor and Resolve Failed Messages:

1. **Track Analytics Dashboard:** Regularly check the "Failed Messages" section in the BizMagnets Analytics to identify patterns.
2. **Check Error Codes:** Review error codes provided by WhatsApp for failed messages to understand the exact issue.
3. **Fix Template or Content Issues:** If the failure is due to template rejection, modify the content to comply with guidelines and get it approved.
4. **Update Recipient List:** Verify and update phone numbers to ensure they are valid and registered.
5. **Improve Quality Rating:** Maintain high-quality interactions to avoid restrictions on your account.

By analyzing failed messages, businesses can proactively address delivery issues, improve communication quality, and ensure a better experience for their audience.