Template components | Developer Documentation

Parts of a WhatsApp message template in ChatArchitect

A template combines message text, variables and, when useful, buttons. These are available in Submit template at wtargeted.com for a ChatArchitect integration. Sign in using your App key and Secret; the step-by-step template guide shows how to submit a message and find approved templates.

Body: the message itself

The body is required. Write one clear message that matches the reason you are contacting the recipient. For information that changes between recipients, use numbered placeholders such as {{1}} and {{2}}. Provide a realistic sample for every placeholder in the form's second column. The samples help Meta review the template; the actual values are supplied by the connected sending workflow.

For example, an appointment update could use:

Your appointment on {{1}} at {{2}} is confirmed. Reply if you need to reschedule.

The sample should show a complete message, such as “Your appointment on 12 October at 14:30 is confirmed. Reply if you need to reschedule.” Do not put an App key, Secret, verification code, or a customer's private data into a review sample.

Buttons

The Submit template form also supports buttons. Add one when it gives the recipient a useful next step. Choose from the button types shown in your account and write a label that makes the action clear. The exact types and their behavior in a connected sending tool should be checked in that tool before a campaign. The form does not provide special copy-code buttons or offer countdowns. Use the coupon guide and deadline guide to communicate those details in the text.

Keep the essential meaning in the body. Test each button on a recipient's phone; if it opens a link, check the final destination. If a button is available in the creation form but absent when sending through an integration, contact ChatArchitect support with the template name and the tool you used.

Other Meta components

Meta's template structure also describes optional headers and footers. A header can introduce a message with text or supported media; a footer adds short secondary text. Their availability in ChatArchitect's Submit template form has not been confirmed. Ask ChatArchitect support before planning a campaign that depends on a header, media file or footer.

Submit and check the result

1. In Submit template, choose the language and the category that matches the complete message.
2. Enter the body, any variables and the buttons you need. Add a sample value for each variable, then submit the template.
3. After review, refresh Approved templates. Check the final text and category before selecting the template in your connected tool. If it is absent or rejected, use the review guide.
4. Send a test through the intended integration. Check the substituted values and every button on a recipient's phone. If a component is missing in the sending tool, contact ChatArchitect support with the template name and the tool you used.

Meta documents additional formats in its template examples. Check availability of those formats in your ChatArchitect account and connected integration.