> 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/common-error-issues/troubleshooting-whatsapp-api-errors/business-has-been-locked.md).

# Business has been locked

**Issue**: This error usually occurs if WhatsApp has temporarily stopped messaging operations for your WhatsApp Business Account.

**Solution**:

To address the issue where WhatsApp has temporarily stopped messaging operations for your WhatsApp Business Account, follow these steps:

1. **Create a New Facebook Business Manager (FB BM)**: Since there might be restrictions associated with your current FB BM, creating a new one might help bypass the limitation.
2. **Obtain a New Phone Number**: Using a new phone number is crucial since the ban may be tied to the current number used for WhatsApp Business.
3. **Register a Fresh WhatsApp Business Account**: With the new FB BM and phone number, proceed to register a new account. This effectively resets your account's status with WhatsApp, potentially resuming normal operations.


---

# 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/common-error-issues/troubleshooting-whatsapp-api-errors/business-has-been-locked.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.