> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/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-documentation/messaging-channels/whatsapp-api/getting-started-with-whatsapp-api/account-quality.md).

# Account Quality

The quality rating, based on customer feedback over the past seven days, includes reasons like blocking your number or reporting issues.

#### Where to Find: **Phone Numbers Tab** in Meta WhatsApp Manager

* **Quality Rating Column** shows:

  * **Green:** High quality
  * **Yellow:** Medium quality
  * **Red:** Low quality

  #### Improving Your Rating

  * Hover over the rating for insights into block reasons.
  * Aim to maintain a high-quality rating to unlock more features.
  * Reasons for blocking include: No longer needed, Didn't sign up, Spam, Offensive messages, or No reason.

  #### Notifications

  You will receive updates via email and Meta Business Manager notifications for status changes or messaging limits updates.

  #### Status Changes

  * **Connected:** Normal operation within messaging limits.
  * **Flagged:** Low quality; if not improved in 7 days, messaging limit decreases.
  * **Restricted:** Reach messaging limit; no outgoing messages for 24 hours, but responses to customer-initiated messages are allowed.

  **What to do** when account quality is yellow or red?
* It is suggested that you don't send any message for 7 days for quality to improve.


---

# 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-documentation/messaging-channels/whatsapp-api/getting-started-with-whatsapp-api/account-quality.md?ask=<question>&goal=<user_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.