Business customer phone numbers | Developer Documentation

Match the business number to the intended integration

Keep a clear record of the business phone number your team will use with ChatArchitect. The business number, its display name, the selected WhatsApp account and the recipient's number describe different parts of a conversation.

Prepare the number you control

ChatArchitect does not provide phone numbers. Use the number preparation and verification guide to check control of the number and the available SMS or voice verification method. The display name is what customers see for the business; it does not replace the phone number when identifying a connection.

If the number already uses the WhatsApp Business app, joint operation with ChatArchitect is supported. Confirm the appropriate entry route and the required behaviour before changing the existing account. The exact connection path and the scope of history, contact and message synchronization require checking for that case; use the connection overview and ask support when they are unclear.

Check the connection record

1. Record the intended business portfolio and WhatsApp account with the person responsible.
2. Complete the supplied account connection and return to ChatArchitect.
3. Compare the available business number with the one intended for the CRM, help desk or custom service.
4. Check a permitted test conversation and its outgoing result in that tool.

For an additional number or a change of connection, confirm the supported route for the particular account before changing a working number.

Describe a number that is missing or unexpected

Keep the business number, account name, sending tool, time and stage of the attempt together. If an identifier is visible, include it alongside the readable details. A recipient number or a test message reference alone does not identify which business connection was selected.

Use the completion checklist for an unfinished setup, and the API preparation guide for your own application. Meta's provider phone-management endpoints are a separate reference; regular ChatArchitect setup uses the supplied connection.

Provider implementation reference

For a separate Meta provider implementation, consult the Meta developer reference for Business customer phone numbers. That reference uses its own application, account and permission context. Use the customer workflow above for ChatArchitect.