# Partner-led Business Verification (PLBV)
### Prerequisites
* [x] Business details in the documents match the details of the legal business entity (legal name, address).
**Required documents**:
* [x] Proof the company **exists** (e.g., registration/incorporation certificate).
* [x] Proof the company is **active** (e.g., utility bill issued within the last 2 months).
**Time to complete**: Submit in minutes; review typically can take **up to 48 hours**.
{% hint style="warning" %}
#### Important notes
* **PLBV is NOT available for** [**Government Agencies/ Accounts**](/docs/resources/government-agencies.md)**.**
* **Don’t upload personal documents or IDs** — we only accept **business documents** for validation.
* Business details in the documents match the details of the legal business entity (legal name, address). If they don’t, we won’t be able to approve your submission.
* Ensure the account is new and has not gone through any previous verification process. If your account has already submitted a verification, please try using the [Standard Business Verification](/docs/resources/meta-business-verification/standard-business-verification.md)
* Up to 3 PLBV attempts are allowed per Business; after that, the Standard Business Verification process is required.
{% endhint %}
#### Avoid Concurrent Verifications
Running PLVB and Classic Verification simultaneously causes delays.
1. Check Before Starting: Confirm that Classic Verification is **not** active before requesting PLVB.
2. The 3-Day Rule: If a Classic Verification request is pending, a three-day waiting period is required before PLVB can be triggered.
Classic Business Verification must **not** be initiated if PLVB is the intended verification method.
## PLBV Paths
There are two paths available to use PLBV:
1. [PLBV using Embedded Signup](#plbv-using-embedded-signup-new-accounts)
2. [PLBV using Chat Support](#plbv-using-chat-support-existing-accounts)
***
## PLBV using Embedded Signup
Business admins can verify a Business Portfolio **using the Embedded Signup** after the number registration flow.
{% stepper %}
{% step %}
#### Launch the Embedded Signup Flow
Launch the Embedded Signup flow as usual to create a WABA and register a phone number.
{% endstep %}
{% step %}
#### Click 'Finish and upload the documents'
After phone number (OTP) verification, you’ll see an option to upload business documents: click "Finish and upload documents"
{% endstep %}
{% step %}
#### Upload documents
Drag and drop the required documents or choose the files on your device.
{% endstep %}
{% step %}
#### Inform our support team
After uploading the documents via Embedded Signup, speak with human support on chat support to request a PLBV documentation review.
{% endstep %}
{% step %}
#### 360dialog Review
When we receive the chat we will re-assign it to our PLBV specialist who will validate the uploaded documents and submit them to Meta for verification and approval.
{% endstep %}
{% step %}
#### Outcome
Meta will review the documents and provide an outcome, usually within 48 hours.
{% endstep %}
{% endstepper %}
{% hint style="danger" %}
Accounts submitted **without a website** may be **automatically restricted** until 360Dialog Business Legitimacy and Meta's Business Verification is completed.
⇒ To avoid delays, please include a website when submitting your account.
{% endhint %}
#### What will you see on the screen?
After verifying the phone number, a screen will appear showing the option to upload documents. It looks like this:
**🎥 *****Video preview:***
{% embed url="" %}
***
## PLBV using Support
This path can be used at any time. \
WABAs that are disabled/blocked are not eligible.
### Steps
{% stepper %}
{% step %}
#### Contact Support
There are two options:
1. Start a new support chat: Login to the 360Dialog Hub, initiate a new support chat and ask for PLBV support.
2. Contact our PLBV support team on this email:
{% endstep %}
{% step %}
#### **Send documents and business IDs**
* Attach the required documents
* Share the relevant IDs: WABA ID or phone number and Meta business portfolio ID.
* Provide a screenshot of the Meta Business Suite > **Business Info** section, which shows the business's legal entity name.
{% endstep %}
{% step %}
#### 360Dialog Review
When we receive the chat, we will assign it to our PLBV specialist who will validate the uploaded documents and submit them to Meta for verification and approval.
{% endstep %}
{% step %}
#### Outcome
Meta will review the documents and provide an outcome, usually within 48 hours.
{% endstep %}
{% endstepper %}
### Successful outcome
* Our support team will communicate the outcome in the open support case.
* Your endpoint should receive the `phone_number_quality_changed` webhook indicating:
* **Messaging limit increased to 1,000/day**, and
* **Display name** becomes visible after review.
* See [Webhook events and notifications](/docs/messaging/webhook/webhook-reference.md) documentation for details.
{% hint style="warning" %}
**Meta makes the final decision**; 360dialog approval does **not** guarantee verification.
{% endhint %}
## Troubleshooting
* **Mismatch detected / request declined**: Ensure BM/WABA data **exactly** matches the documents (legal name, address, registration/VAT).
* **WABA blocked**: Resolve the block first; **blocked WABAs are not eligible**.
* **Insufficient proof of activity**: Provide a **recent** document (issued within the last **60 days**).
* **No webhook received**: Check if your webhook endpoint is reachable/subscribed and review recent delivery logs.
* If you still cannot identify the reason using the points above, start a chat support request and ask for our PLBV specialist.
---
# Agent Instructions: 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:
```
GET https://docs.360dialog.com/docs/resources/meta-business-verification/partner-led-business-verification-plbv.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.