Implementation | Developer Documentation

Confirm the account and number you intend to use

• Identify the intended business portfolio and WhatsApp account with the person responsible for them.
• Have access to the phone number and the verification method you intend to use: SMS or voice call.
• Keep the requested business information ready for the form.
• Choose the CRM, help desk or application that will use this connection.

For an existing WhatsApp number, confirm the applicable migration or coexistence route before making account changes. Keep the current working account while its connection route is being clarified. The phone-number guide explains number preparation and verification.

Open the supplied connection flow

In the WhatsApp setup supplied by ChatArchitect, select Continue with Facebook and continue in the Meta window. The illustrated connection guide shows the customer screens.

If the window does not open or the process stops before account selection, record the visible message and the point where it stopped. Return to the supplied setup route or ask support to check the connection. Creating a developer app, changing OAuth domains or adding a JavaScript SDK to your website is not a customer recovery step.

Select the business assets and verify the phone number

Select the intended business portfolio and WhatsApp account, creating an account only if that is the agreed setup. Enter the requested business details, add the intended number and follow the form's SMS or voice verification step.

If the expected portfolio is absent, ask the person responsible to confirm your access and selection. If a code does not arrive, check the number, country code and selected receiving method using the phone-number guide. If the number is already in use or the business details are rejected, record the exact message and clarify that condition before starting another account setup.

The SMS or voice code and the two-step verification PIN are different credentials. Enter a verification code only in the step that requested it. Manage the number's security PIN through WhatsApp Manager.

Check the connection after returning to ChatArchitect

After completing the Meta form, return to ChatArchitect and check whether the intended number is available in the intended connection. Compare it with the portfolio, account and number recorded before setup.

If the form completed but the number is absent, give ChatArchitect support the selected business assets, affected step, completion time and visible result. Treat the Meta form result and the ChatArchitect connection check as separate observations. Do not start a second setup solely because a number is not immediately visible.

Locate the stage that did not finish

If you closed the flow before completing it, identify the last step you completed and check the current connection state before continuing. This guide does not prescribe deleting an account, removing a working number or running Meta registration requests as a retry.

Configure the supported sending tool

Once the intended number is confirmed in ChatArchitect, use that connection's App key and Secret following the credentials guide and your integration's instructions. Confirm the connection associated with the credentials before saving the setup.

For a custom application, use the ChatArchitect API preparation guide for the current request format and reply-handling checks. A browser signup callback in Meta's developer reference does not define the incoming ChatArchitect message callback.

Check one permitted send and its result

Use the intended tool and an agreed test recipient. Review the message type and service-window or template requirements before sending. Check the tool's actual result and the receiving conversation; if your workflow receives replies, verify the intended reply path separately.

If the test fails, retain the operation, connection, time, available reference and redacted error. Keep the problem attached to the stage where it occurred. Completing the connection flow alone does not show that a CRM campaign or custom application has been tested.

Close the setup checklist

• The selected business assets match the intended setup.
• The intended number is present in the ChatArchitect connection.
• The selected integration uses the credentials for that connection.
• The permitted test and any required reply check have a recorded result.
• Any unresolved step has a clear owner and the details needed for support.

Meta's technical implementation reference covers developer-app and SDK setup for organizations implementing platform onboarding. This customer checklist uses the connection supplied by ChatArchitect.