> 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.md).

# WhatsApp Accounts

This page describes the structure, limitations, and policy enforcement rules of WhatsApp Accounts on the WhatsApp Business Platform.

Current account model has two entities:

* **WhatsApp account (WAAC)**: holds the phone numbers, display names, catalogs, app subscriptions and user assignment.
* **Messaging account**: holds message templates, the payment method or credit line, billing and webhooks. Your existing WABA became a Messaging account with the same ID.

Before October 2026 it was just one account. A **WhatsApp Business account** (also known as **WABA**) was bundled with a phone number, templates and billing together, and could only be shared with one solution provider at a time. 

Since October 2026 a phone number can now have one Messaging account per provider (BSP or partner). This is how a business can use 360dialog and another provider on the same phone number at the same time. Each provider has its own templates and billing. Messaging limits are per phone number and shared across all Messaging accounts on that number. 

Meta's **conversation routing** setting decides which provider receives incoming messages and replies. To fix the common error caused by conversation routing see [this article (error 131070).](/docs/guides/messages-not-arriving-after-onboarding.md)

In Meta Business Suite > Business settings you see both **WhatsApp accounts** and **Messaging accounts**. The 360dialog Hub, the API (for example `waba_id`) and most of this documentation still say "WABA". In those places, WABA means the Messaging account.

### Access WhatsApp account (WAAC)

Can be viewed in Meta Business Manager > WhatsApp Accounts.

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FkeHekR6x6KKoXVfztdmk%2FScreenshot%202026-10-30%20at%2016.13.33.png?alt=media&amp;token=bee9755b-c199-4498-bb17-b815cb19fc6b" alt=""><figcaption></figcaption></figure>

### Limitations

* A WhatsApp account (WAAC) can have a maximum of 250 message templates.
* Meta Business Accounts are initially limited to 2 registered business phone numbers, but this limit can be increased to up to 20. See [Registered Number Limits](https://docs.360dialog.com/docs/resources/phone-numbers#registered-number-cap).
* A WABA’s time zone and currency cannot be edited once a line of credit has been attached to it.&#x20;
* Meta Business Accounts are initially limited to 20 WAACs.

### Message Limits

Phone number Messaging limits are calculated and set at the business portfolio level and are shared by all business phone numbers within a portfolio. [Read more about message limits.](https://docs.360dialog.com/docs/resources/wabas/messaging-limits)

#### **WhatsApp account (WAAC)**

Each WAAC has a unique Account ID. The ID is shown in the Messaging Accounts page under the WAAC Name.&#x20;

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FEXOt43PEMTUBcRB47Fbh%2F2026-10-30_16-19-03.png?alt=media&amp;token=b4c5a5d6-388e-4373-9705-93296a1b7160" alt=""><figcaption></figcaption></figure>

### Create a WAAC

The only method to create a WAAC with 360dialog is by using [the Embedded Signup](/docs/hub/embedded-signup.md) flow. This is required to access 360dialog's Credit Line. If the phone number is already on the WhatsApp Business Platform with another provider, Embedded Signup creates a new Messaging account for 360dialog on the existing WhatsApp account; see [Move a number to 360dialog from another provider](/docs/hub/migrations/move-a-number-to-360dialog-from-another-provider.md).


---

# 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.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.