> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user/common-error-issues/troubleshooting-whatsapp-api-errors/131026-receiver-is-incapable-of-receiving-this-message.md). # #131026 Receiver is incapable of receiving this message 1. **Per-User Marketing Template Message Limits** Meta has instituted specific limitations on the number of marketing messages a user can receive from various businesses within a single day. While the exact number isn't officially specified by Meta, understanding this limit is essential for strategizing your outreach. If a user has already received marketing messages from multiple businesses in a day, your message might not be delivered if it exceeds this undisclosed limit. **Retry Strategies and Message Delivery Insights** If your message fails to deliver, consider retrying on the next day. This approach accommodates the per-user marketing message limitations and increases your chances of successful delivery. Interestingly, if a user doesn't receive a message from you on a particular day but did receive one previously, a subsequent message sent after a brief interval may successfully reach them. This pattern underscores the dynamic nature of WhatsApp's delivery algorithms and the importance of timing your messages strategically. 2. **Policy Acceptance:** Another potential reason for non-delivery concerns the recipient's acceptance of WhatsApp's latest policies. Users who have not accepted the most recent policy updates may not receive your messages. In such cases, if you have direct contact with the recipient, encourage them to visit [WhatsApp's Terms of Service](https://wa.me/tos/20210210) and accept the latest policies to ensure message delivery. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://helpdocumentation.gitbook.io/user/common-error-issues/troubleshooting-whatsapp-api-errors/131026-receiver-is-incapable-of-receiving-this-message.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.