WhatsApp Business API - Phone Number Management API | Developer Documentation

Keep a routing record for each business number

Use this audit when your business or application works with several WhatsApp numbers. The objective is to find a missing, duplicated or incorrect route. It does not introduce a ChatArchitect phone-number listing API or promise that one credential pair has a fixed number-to-account relationship.

Build a small inventory

Create one row per business number you are responsible for. These are suggested columns for your own record, not ChatArchitect API fields:

• The business number, its purpose and the team that owns its conversations.
• The selected WhatsApp account and available labelled asset references.
• The connected CRM, help desk or application workspace.
• The configuration reference for its connection/credentials, without Secret values.
• The expected incoming conversation/receiver and the location of outgoing attempt results.
• Scheduled sends and the person who may approve a route change.

Use the number record and the identifier checklist to resolve similar labels. For several customers in your own service, also use the workspace separation check.

Test one route at a time

1. Choose a permitted contact and record the business number under test.
2. Send an incoming message to that number and inspect the intended conversation or receiver.
3. Send an appropriate outgoing reply through the selected tool/connection. Verify the sender seen by the contact and keep the attempt reference.
4. Check the later result against that attempt. Mark the incoming, outgoing and result paths separately in the inventory.
5. Repeat for the next number, using a distinct test marker so the attempts cannot be confused.

Investigate a wrong or missing route

Compare the observed workspace, number and receiver with the recorded configuration. Do not replace credentials or register another callback by guessing which number it covers. Use receiver management and confirm shared-connection or multi-number scope with support before a change.

For a new route use API preparation or the instructions for the supported integration. Before moving or removing an established route use change planning. A successful account listing or registration does not demonstrate that every number reaches its intended conversation.