> ## Documentation Index
> Fetch the complete documentation index at: https://plivo.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Number Modal

> UI reference for the Configure Number side panel — Alias, Configuration Type, Webhook URL, WhatsApp Calling, Answer URL, and Account Mapping

> [!NOTE]
>
> * **Where:** Click a number on the [WhatsApp Numbers page](https://cx.plivo.com/whatsapp/numbers) to open the **Configure Number** side panel
> * **Required:** **Webhook URL** (for inbound messages). If you enable WhatsApp Calling, **Answer URL** is also required
> * **Optional:** Alias, AI Agents configuration, Account Mapping
> * **Critical:** Account Mapping applies to the entire WABA — changing it for one number changes it for every number linked to that WABA

The **Configure Number** side panel is where you wire a WhatsApp number to your application — Webhook URL for inbound messages, Answer URL for voice calls, and the Plivo account that should own the traffic.

***

## Fields

### Number Type and Capabilities

Read-only summary at the top of the panel:

* **Phone number and country** of the WhatsApp number
* **Capabilities** badge — `WhatsApp` indicates the number is WhatsApp-enabled

### Alias

Optional friendly label for the number. Use it to distinguish numbers in lists when you operate multiple WhatsApp numbers — for example, `Support — APAC` or `Sales — EU`.

### Configuration Type

Choose how inbound messages and calls are handled:

| Option | When to use |
| - | - |
| **Webhook URL** | You handle inbound messages and calls with your own backend |
| **AI Agents** | You're using a Plivo AI Agent to handle the conversation — see [Voice Agents](https://plivo.com/docs/voice-agents/audio-streaming/overview.md) |

### Webhook URL

Required when Configuration Type is **Webhook URL**. The endpoint that receives inbound message events (text, media, replies, status updates) from your WhatsApp number.

* Must be a valid HTTPS URL — for example, `https://yourdomain.com/whatsapp/webhook`
* Must respond with `200 OK` to acknowledge receipt
* See [Inbound Messages](https://plivo.com/docs/messaging/use-cases/whatsapp/getting-started/inbound-message/inbound-message.md) for payload details

### Enable WhatsApp Calling

Toggle to enable voice calling on the number. When on, users see a call button next to your WhatsApp number in the WhatsApp app, and you can place outbound calls using `callType: whatsapp` in the [Dial XML element](https://plivo.com/docs/voice/xml/routing.md#dial).

When the toggle is on, the **Answer URL** field below becomes required.

### Answer URL

Required when **Enable WhatsApp Calling** is on. The endpoint that handles inbound voice calls — Plivo POSTs to this URL when a call arrives, and your endpoint must return [Plivo XML](https://plivo.com/docs/voice/xml/overview.md) instructions.

* Must be a valid HTTPS URL — for example, `https://yourdomain.com/whatsapp/answer`
* Must return valid Plivo XML
* See [WhatsApp Calling](https://plivo.com/docs/messaging/concepts/whatsapp/whatsapp-calling.md) for the full call-flow guide

### Account Mapping

Choose which Plivo account owns the WhatsApp traffic and billing:

* **Main Account** — default; the WABA reports to your main account
* **Subaccount** — route the WABA to a specific subaccount (useful for multi-team or multi-tenant setups)

> [!NOTE]
>
> Effective November 1, 2026, Plivo applies a platform fee for all WhatsApp messages, inbound and outbound, in addition to the standard carrier rates. A monthly fee also applies to each registered WhatsApp Business Account.
>
> For more pricing information, see [WhatsApp pricing](https://www.plivo.com/whatsapp/pricing/).

> [!WARNING]
>
> **Account Mapping applies to the entire WhatsApp Business Account.** It affects every number linked to this WABA, not just the number you're configuring. Changing this setting for one number changes it for all numbers under the same WABA.

***

## Actions

### Save changes

Click **Save changes** to apply your configuration. Plivo validates URLs and stores the configuration immediately — no propagation delay.

### Disconnect number

Click **Disconnect number** in the bottom left to remove the number from your Plivo account. The number stays with Meta — only the Plivo connection is severed. Disconnecting stops inbound webhook delivery and disables outbound API access for that number.

> [!WARNING]
>
> **Disconnecting is reversible but disruptive.** You can reconnect the number later, but any in-flight conversations break and you'll need to reconfigure Webhook URL, Answer URL, and Account Mapping from scratch.

***

## Related

* [WhatsApp Numbers Page](https://plivo.com/docs/whatsapp/console/numbers-page.md)
* [Connect WhatsApp Number](https://plivo.com/docs/whatsapp/console/connect-number.md)
* [WhatsApp Calling](https://plivo.com/docs/messaging/concepts/whatsapp/whatsapp-calling.md)
* [Inbound Messages tutorial](https://plivo.com/docs/messaging/use-cases/whatsapp/getting-started/inbound-message/inbound-message.md)
* [Plivo XML Reference](https://plivo.com/docs/voice/xml/overview.md)