Solution providers | Developer Documentation
Who sets up a WhatsApp connection with ChatArchitect?
Use this guide when your business wants to connect WhatsApp to a CRM, help desk or custom application through ChatArchitect. ChatArchitect supplies the ready-made connection. Customers and partner developers use that connection; they do not install their own Meta Embedded Signup implementation through ChatArchitect.
Choose the connection route first
Start with the integration-route guide. For a supported CRM or help desk, follow the instructions for that tool. For your own service, use the API preparation guide and the ChatArchitect API quick start.
The sending tool and the account connection are separate parts of setup. Completing the Meta form does not by itself show that an incoming message reaches the intended CRM conversation or that your application receives a delivery result.
Agree who is responsible for each part
| Part of setup | What to prepare or check |
|---|---|
| Business account and number | A person with access to the intended business portfolio and control of the phone number; the details requested by the connection form. |
| CRM or help desk | The supported integration, the person who configures it, and where the team will find incoming chats and outgoing results. |
| Custom application | A developer responsible for server-side API credentials, the receiver and the application's message records. |
| Incomplete connection | The stage that stopped, the selected account and number, and information ChatArchitect support can use to investigate. |
Complete the supplied account connection
Use the Embedded Signup overview, then the phone-number guide. The confirmed route starts with Continue with Facebook, selection of the business portfolio, addition of the number and verification by SMS or voice call. Follow the prompts shown for your account. If the flow is interrupted, use the completion checklist.
ChatArchitect API credentials are the App key/App ID and Secret supplied for the connection. Use their meaning in the ChatArchitect quick start. A Meta developer application's identifier or access token is a different credential.
Check the working customer workflow
Record the connected business number, selected sending tool and responsible person. Use a permitted test contact to check an incoming message, an appropriate reply and the later sending result in the intended tool. For a custom application, also check the receiver and its mapping to the connection.
The imported terms Solution Partner, Tech Provider and Tech Partner describe Meta provider documentation. They do not identify an extra registration step for a regular ChatArchitect customer or establish a particular ChatArchitect partner programme. For commercial terms, use the ChatArchitect cost guide.
Provider implementation reference
For a separate Meta provider implementation, consult the Meta developer reference for Solution providers. That reference uses its own application, account and permission context. Use the customer workflow above for ChatArchitect.
No comments to display
No comments to display