How multiple numbers fit together
A WABA is your business identity at Meta. It can hold any number of phone numbers.
A phone number belongs to exactly one WABA.
A channel is the connection between a phone number and a workspace in Octopods. Each phone number can be activated as a channel in one workspace at a time.
Each number has its own display name, quality rating, messaging tier, and health status — changes on one number don’t affect others under the same WABA.
This structure means you can run one brand or region per phone number (for example, one number for US support, a different number for EU support) while keeping all the numbers under a single WABA for easier billing and template management.
Viewing all your numbers
Open the workspace.
Go to Channels and reopen the WhatsApp Setup page (via Add Channel → WhatsApp).
Scroll the WhatsApp Phone Numbers card. Every phone number Octopods has discovered for this workspace is listed as a row.
If a number is already connected to a different workspace, its badge reads Different workspace and you’ll see a View Channel button that opens the workspace where it’s active.
Adding more numbers
When you approve a new phone number in Meta Business Portfolio and want to connect it to Octopods:
From WhatsApp Setup, scroll to the Add Another Number card.
Press Login with Facebook Business Manager.
Re-run the Meta connection flow and grant access to the new number.
Return to Octopods — the new number appears in the list. Register it on Cloud API if needed, then activate it as a channel.
Connecting a specific number to a workspace
Each phone number can be activated in one Octopods workspace at a time. To connect a number:
In the WhatsApp Phone Numbers list, find the number you want to connect.
If it’s marked Unregistered, press Register on Cloud API first.
Once the number is on Cloud API, activate it for your workspace type. For Intercom workspaces, press Activate Channel — the number becomes a WhatsApp channel and starts routing conversations to Intercom. For HubSpot workspaces, pick the destination inbox from the Select HubSpot Inbox dropdown, then press Activate — the number connects to that specific HubSpot inbox.
Note: To move a number from one workspace to another, first Deactivate it on the current workspace, then run Activate Channel from the destination workspace.
Deactivating a channel
Deactivation disconnects the phone number from this workspace in Octopods, so conversations stop being routed to your customer platform. The number itself stays registered on Cloud API under the WABA, and you can reactivate it later or activate it in a different workspace.
Open Channels in the workspace where the number is connected and reopen the WhatsApp Setup page (via Add Channel → WhatsApp).
Find the phone number row.
Press Deactivate.
Confirm the action when prompted — Octopods will ask Are you sure you want to deactivate this WhatsApp channel?
Warning: Deactivation is immediate. Conversations in flight through this channel stop being routed. If you reactivate the number later, historical conversations are not automatically reattached.
Syncing a number’s metadata
Meta pushes some changes to Octopods automatically, but others — like quality rating shifts, messaging tier bumps, and display name approvals — only appear after a manual refresh.
Find the phone number in the WhatsApp Phone Numbers list.
Press Sync.
Wait a moment for Octopods to refresh the metadata from Meta. The button shows Syncing… while the request is in flight.
After sync, the number’s badges and attributes reflect Meta’s current data.
Organizing numbers across workspaces
A common setup with multiple numbers:
One number per region — route US traffic to a US workspace, EU traffic to an EU workspace, so local teams see their own conversations.
One number per brand — if you operate multiple brands under the same legal entity, each brand can have its own number and its own workspace.
One number per team — a sales number activated in a sales workspace, a support number in a support workspace.
All of these patterns work because channels are per-workspace and phone numbers are per-WABA.
What’s next