WhatsApp Cloud API - Phone Number API | Developer Documentation

Prepare a number change before altering a working connection

Use this checklist when you want to disconnect a tool, move a number or change its provider. These are different operations: disabling one CRM connection, changing the WhatsApp service behind a number and deleting an account have different effects. Confirm the intended result with ChatArchitect support before making changes.

Record what currently uses the number

• Identify the business number, WhatsApp account and portfolio, and the person who manages them. The connection record guide explains which details identify the business connection.
• List the CRM, help desk, custom service and sending workflows using that number. Include scheduled sends and the person responsible for incoming requests.
• List links, QR materials and other places customers use to contact the number. Use the chat-link guide to identify their destination.
• If the WhatsApp Business app is active on the same number, record that requirement. Joint operation is supported; confirm how the proposed change affects it.

Agree the change and recovery route

State which part you want to stop or replace and which functions you need afterward. Ask support and the receiving provider, when relevant, to confirm the supported route, prerequisites, responsibility and expected interruption. Specify what should happen to templates, incoming requests and the old connection.

Define how the team will verify the result and handle a failed change before scheduling it. The available migration routes, transfer of history or templates, and ability to return to the original setup require confirmation for the case. They are not established by an imported Meta deregistration endpoint.

Verify the agreed outcome

After the agreed procedure, compare the actual connection with the required number and tool. Use a permitted test conversation, inspect the outgoing result and confirm the handling of incoming requests. Check the Business app separately if keeping it active is part of the plan.

Keep the change record and the agreed recovery contact. Ordinary ChatArchitect setup uses App key and Secret; this checklist does not instruct a customer to call Meta's deregistration API or promise an automatic migration.