> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/relate/message-templates-meta/common-questions/message-templates-what-are-the-reasons-that-lead-to-a-template-being-rejected.md).
# Message Templates - What are the reasons that lead to a template being rejected?
Template rejection can occur for several reasons, including:
* The message template contains content that violates WhatsApp's Commerce Policy: when you promote the sale of goods and services, all media and messages related to your products are considered transactions. This includes descriptions, prices, fees, taxes, and/or required legal disclosures. Transactions must comply with the [WhatsApp Commerce Policy](https://www.whatsapp.com/legal/commerce-policy/).
* The message template contains content that violates the [WhatsApp Business Policy](https://www.whatsapp.com/legal/business-policy/): do not request sensitive user identifiers. For example, do not ask customers to share full individual credit or debit card numbers, financial account numbers, national identification numbers, or other confidential information. This includes not requesting documents from users that may contain sensitive identifiers. Requesting partial identifiers (for example, the last 4 digits of the CPF) is acceptable.
* The content is potentially abusive or threatening. For example, threatening the customer with legal action or public embarrassment
* The message template is a duplicate of an existing one. If a template is submitted with the same text as an existing one in the body and footer, the duplicate will be rejected.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sprinthub.com/en/topics/relate/message-templates-meta/common-questions/message-templates-what-are-the-reasons-that-lead-to-a-template-being-rejected.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.