Onboard business customers | Developer Documentation
Hand over a ChatArchitect marketing setup to your team
Use this checklist when the people connecting the business number, preparing templates and operating the CRM or help desk are different. Agree who will confirm each part of the setup and what evidence the sending team needs. One person can cover several tasks; the responsibilities below are a suggested working arrangement, not a list of ChatArchitect account roles.
Agree who confirms each part
| Responsibility | What to confirm | Useful handover record |
|---|---|---|
| Business connection | The intended business portfolio, WhatsApp Business Account (WABA) and number are used in the connection. | Business portfolio and WABA names, sender number, and a contact who can check the existing setup. Use the number preparation guide. |
| Template preparation | The team can find the approved text, category and language in Approved templates at wtargeted.com. | Template name and language, final wording, variable order and configured buttons. |
| Sending tool | The CRM, help desk or other connected tool has the intended sender and can select the approved template. | Tool name, sender selection, test time and any attempt reference available. Follow the approved-template sending guide. |
| Campaign decision | The business agrees on the audience, permission to contact it, offer, frequency and launch conditions. | A campaign owner and a reviewed audience and message. Use the first campaign checklist. |
| Result review | The team knows which delivery results, website visits and business actions it can actually observe. | Report sources, period, time zone and a person who will review them. Use the campaign metrics guide. |
| Billing decision | The business knows its current ChatArchitect plan and who approves changes or additional charges. | Plan, applicable terms, billing contact and agreed review point. Use the pricing guide. |
Confirm the handover with a permitted test
- Review the existing number connection together. If it is already connected, check it before starting another setup. If the number also uses the WhatsApp Business app, follow the coexistence guide before changing that arrangement.
- Have the person who will operate the sending tool select the intended number, approved template and language. Send a test to a recipient who agreed to receive it and check the values and button action on the received message.
- Record what the test establishes: template selection, correct content and any delivery result exposed by the integration. Keep an unavailable result marked as unknown. A prepared dashboard or accepted request alone does not establish recipient delivery.
- Agree who checks template status and quality in wtargeted.com, reviews the available results and handles a delivery problem before a repeat send.
- Give the sending team the checklist, test record, current billing terms and support contact. Resolve an incomplete connection, missing template or incorrect values before expanding the campaign.
Use the supported customer workflow
The confirmed ChatArchitect customer workflow uses ChatArchitect App key and Secret and a ready-made connection through ChatArchitect. It does not require the customer to build a Meta developer app, obtain advanced app permissions, pass App Review or configure a direct Meta API integration. The API scope guide explains the route used by a customer.
Keep App key, Secret, PINs and one-time verification codes out of shared handover notes and screenshots. If a setup problem remains, provide support with the business and WABA names, sender number, tool, template and language, attempt time and exact error. Meta's platform onboarding guide provides general background; the steps above describe the ChatArchitect team handover.
No comments to display
No comments to display