Partner-initiated WABA creation | Developer Documentation

Check what the invitation is asking you to authorize

An invitation to create or share a WhatsApp business account needs its own decision. Before accepting, match the sender and requested business assets to the connection you agreed with ChatArchitect. An invitation by itself does not establish that you need a new account or a different provider arrangement.

Collect the details of the actual request

• Record who sent the request, which company they represent and the setup or change it relates to.
• Read the business name, account or application named in the request. Record any visible identifiers, the date and the requested access or creation action.
• Compare the request with your intended business account and phone number. Use the account-selection guide if the choice between an existing and a new account is unresolved.
• Ask the business administrator to confirm that the assets and requester belong to the agreed work. The account-control checklist helps separate business ownership from someone's ability to sign in.

Resolve a mismatch before continuing

If the company, application or intended account differs from your agreement, ask the person responsible for the setup to explain the difference. Send support the request's name, visible identifiers, date and a redacted screenshot. A screenshot should show the decision you are being asked to make, without passwords, API Secret, verification codes or PINs.

If an existing account or number is already working, record its current connection. Agree any replacement or move through the number-change plan before creating an alternative account or removing access.

Use the confirmed connection route

ChatArchitect customers complete its prepared connection flow. Continue only with the business assets and request that have been identified for that flow. After setup, check the connected number and sending tool; accepting an invitation is not a delivery test.

Keep a decision record

Record the business/account, requester, purpose, accepted scope and person who approved it. If the request is unresolved, record the question and responsible contact rather than treating it as a completed connection.

The former Meta partner-initiated WABA procedure did not define a ChatArchitect customer invitation service, ownership transfer or payment method. Any separate provider arrangement requires its own confirmation.