> 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/how-to-complete-business-verification-directly-from-panel-using-partner-led-business-verification.md).

# How to Complete Business Verification Directly from Panel using Partner LED Business Verification

Steps:

1. Go to **Channels** from the left-side menu.
2. Click on the **WhatsApp icon** of the channel.
3. Click on **Complete Business Verification**.
4. Select the required **document type** and upload the verification document.
5. Click on **Submit Documents**.
6. After submitting documents, the verification process may take up to **3 days**.
7. To check the verification status:
   * Go to **WhatsApp icon**
   * Click on **Check Business Verification Status**
8. You will be redirected to WhatsApp Business Manager where you can check whether your Business Manager is **Verified or Rejected**.

In case of rejection, you can make up to **3 attempts** using Partner LED Business Verification.

{% embed url="<https://youtu.be/0eLQE-TQApE>" %}


---

# 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/how-to-complete-business-verification-directly-from-panel-using-partner-led-business-verification.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.