Welcome Message Sequences - API Guide | Developer Documentation
Welcome Message Sequences and ChatArchitect
ChatArchitect does not support the Meta Welcome Message Sequence setting for greetings and FAQs in Click-to-WhatsApp ads. There is no ChatArchitect sequence editor or supported sequence API workflow described by this service guide.
A sequence associated with an advertisement and a reply sent from your CRM after a customer writes are different stages. Connecting a WhatsApp number through ChatArchitect does not establish that its app can be selected as a Partner App for an advertising sequence.
Keep ad setup and customer replies separate
| Task | Where to check it |
|---|---|
| Configure an advertisement and its initial messaging experience | Check the options actually available in your Meta advertising account with the person responsible for the ad. ChatArchitect does not provide the Welcome Message Sequence setting. |
| Receive the customer's WhatsApp message in your connected system | Check the correct connected business number and the CRM or help desk conversation. An ad preview alone is not a receipt check. |
| Reply after the customer writes | Use the connected system's supported message action; see text replies in the customer service window. |
If you need an automatic greeting after an incoming message, first check the automation features of your CRM or help desk and the integration. An automation in that system is not confirmation that Meta Welcome Message Sequences are available through ChatArchitect.
Check the customer path
- Have the person responsible for the ad confirm its WhatsApp destination and the greeting options available in that advertising account.
- With a consenting test participant, confirm that an actual incoming WhatsApp message reaches the expected CRM conversation for the connected business number.
- Check the reply in that conversation and on the participant's phone. Use the first-message checklist if the connection has not yet been tested.
If the message does not reach the connected system, send support the business number, the integration, the test time with its time zone and the observed result. A redacted ad preview can help identify the starting point; do not send account passwords or API secrets.
Imported Meta illustrations
The following screenshots show a separate Meta Partner App sequence workflow from the former reference. They are retained for context and are not instructions for selecting ChatArchitect or creating a sequence through its API. They do not establish which controls are currently available in your advertising account.
For the supported connection route, follow connecting through ChatArchitect. Availability of ad greetings does not establish event reporting: Automatic Events API is another feature that ChatArchitect does not support.
No comments to display
No comments to display