> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/docs/resources/wabas/business-support-home.md).
# Business Support Home
This page describes Meta’s Business Support Home and how it helps monitor, manage, and resolve policy and account issues affecting WABAs and related business assets.
### Business Support Overview
Business Support Home is a centralised workspace in Meta Business tools used to monitor account health, review policy compliance issues, and take corrective actions across business assets.
Business Support Home is an important operational tool for identifying restrictions, understanding enforcement actions, and contacting Meta support when necessary.
Meta policies, including Advertising Standards, Commerce Policies, and platform terms, are designed to prevent harmful experiences and maintain trust across Meta platforms. Business Support Home provides visibility into how these policies impact business accounts and assets.
### Appeal activity issues
Businesses can request the review of a policy issue via Business Support Home which allows submitting a review request directly to Meta.
{% stepper %}
{% step %}
Go to[ Business Support Home](https://www.facebook.com/business-support-home).
{% endstep %}
{% step %}
Select the affected WABA
{% endstep %}
{% step %}
Choose from the list of violations and click **Request Review**.
For any violation, click See Details to view more info about the specificis of the violation and how to avoid it in future.
If no violations are available in the list, [contact our support team](/docs/support/get-support.md) to discuss the options.
{% endstep %}
{% step %}
Enter supporting details and click **Submit.**
{% endstep %}
{% endstepper %}
After submission, the request and the issue are moved to the **In Review** tab.
The appeal review decision will be sent via the Meta Business Suite and typically takes 24 to 48 hours. The appealed violation will either remain **Unchanged**, or be set as **Reversed**.
### Appeal Rejected Message Templates
The business can appeal rejected message templates directly from Business Support.
{% stepper %}
{% step %}
From the **Account Quality** page, click on **Rejected Message Templates**.
{% endstep %}
{% step %}
Choose from the list of rejected templates and click **Request Review**.
{% endstep %}
{% step %}
Enter **Appeal Reason** and click **Submit**.
{% endstep %}
{% step %}
After submission, the request and the issue are moved to the **In Review** tab.
{% endstep %}
{% step %}
The appeal review decision will be sent via the Meta Business Suite and typically takes 24 to 48 hours. The appealed violation will either remain **Unchanged**, or be set as **Reversed.**
{% endstep %}
{% endstepper %}
---
# 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://docs.360dialog.com/docs/resources/wabas/business-support-home.md?ask=&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.
