- Where: Click a number on the WhatsApp Numbers page 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
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 |
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 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.
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 instructions.
- Must be a valid HTTPS URL — for example,
https://yourdomain.com/whatsapp/answer
- Must return valid Plivo XML
- See WhatsApp Calling 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)
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.
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.
