WhatsApp Business Platform | Developer Documentation
Choose a WhatsApp integration with ChatArchitect
Start by deciding where your team will read customer messages and send replies. ChatArchitect can connect WhatsApp to supported CRM/help desk tools, while the ChatArchitect API lets a developer add messaging to a custom service. This guide helps you choose a route and define a small acceptance check. The service overview covers the connection, messaging rules and costs.
Choose the destination for conversations
| Your workflow | Where to start | What to confirm |
|---|---|---|
| Your sales team works in a CRM | Find your tool in the CRM integration guides. | The supported connection method, where incoming chats appear and which sending actions are available. |
| Your support team works in a help desk or team tool | Use the help desk integration guides. | How a customer message reaches the intended conversation and which person or team handles the reply. |
| You maintain your own application | Use the ChatArchitect API preparation guide, followed by the API quick start. | A developer responsible for server-side credentials, sending, callback handling and the application's conversation records. |
Check the guide for your exact tool and confirm the required functions before choosing the connection. Photo, document, audio, video and voice-message support depends on the integration and the receiving/sending tool. Contact cards, location and other additional functions also need a check for the chosen route. A general platform feature list cannot replace that check.
Prepare the number and the people responsible
- Identify the business number, the tool or service that will receive messages and the person who can complete the connection.
- Follow the number connection guide for the supported ChatArchitect setup.
- If the number already uses WhatsApp Business app and you want to keep using the app, review the shared-number guide and confirm the applicable connection steps with support.
- For an existing integration, record its current route and confirm how a new connection or setting change would affect incoming messages.
Use the ChatArchitect credentials issued for the intended connection. The credentials guide explains App key and Secret. Enter them through the supported setup for your tool; for a custom application, follow the credential names and server-side handling in the API quick start.
Define the first acceptance check
Use a permitted test contact and a small, distinctive message. Agree the intended business number and conversation before testing.
- Have the test contact send a message to the business number. Confirm that it reaches the intended tool or application conversation.
- Send an ordinary reply in the active service window using the first-message guide. Compare the observed result with the message received on the test phone.
- If you need business-initiated messages, create or choose an approved template using the template guide and check the recipient's permission before a small template test.
- Record the integration, number, test time with time zone and available result/reference. For a custom API application, inspect the later delivery result separately from the send response.
If an item is missing or appears in another conversation, investigate the registered connection, receiver and application route before expanding the test. For a ready-made connector, use the guide and available diagnostics for that tool; confirm uncertain behavior with support.
Plan records, costs and ongoing work
ChatArchitect does not store customer message texts or attachments. Review the message-data guide and decide how your connected tool or custom application will handle its own conversation records.
Use the ChatArchitect pricing guide to check your plan and message charges before sending a larger volume. Confirm the applicable terms for your account with support.
| Decision to record | Before customer use |
|---|---|
| Conversation destination | The chosen tool/service and expected incoming route are known. |
| Required message actions | The chosen connection has been checked for the actual text, template and any additional functions you need. |
| Access and records | The responsible people, credential handling and local record policy are agreed. |
| Change and recovery | Existing settings, the effect of changes and the supported restoration process are recorded. |
| Acceptance result | The small incoming/reply test has an observed outcome and unresolved issues are recorded. |
For Meta's broader platform catalogue, see the official overview. Use the ChatArchitect product and integration guides above to confirm the route and features for your connection.
No comments to display
No comments to display