Template previews | Developer Documentation
Review a WhatsApp template before submission and sending
Check the message text and sample values in Submit template at wtargeted.com, then check the approved message as a recipient will see it. The steps below use the confirmed text, variable and button controls described in the template parts guide. A live visual preview or a separate preview API has not been confirmed for the ChatArchitect customer workflow.
Review the draft and its sample text
- Follow the template creation guide. Check that the selected language, message purpose and available category match what you intend to send.
- Read the full message with meaningful values in place of every numbered variable. Use the sample message column to provide a complete example, not just a list of placeholder numbers.
- Check the business name, request or offer, dates, amounts, conditions and intended next action. Make sure that the variable order still produces a clear sentence when the values are longer.
- Check any button text and configured action using the controls actually available in your form. If a required format or button type is missing, ask support about availability before designing the message around it.
Meta's marketing messages guide recommends providing sample content for template review. A sample helps explain the message; approval and a working send still need to be checked separately.
Use a small set of review records
For draft text such as Hello, {{1}}. Your request {{2}} is ready., review representative values before submitting and when testing the approved template:
| Record to check | Example | What to look for |
|---|---|---|
| Typical values | {{1}} = Alex; {{2}} = REQ-12345 | The intended name and reference appear in the correct positions. |
| Longer values | A longer customer name or request reference | The sentence remains clear and the important information is easy to find. |
| Language-specific text | A name with accents and dates written for the chosen language | Characters and wording display correctly; the date is unambiguous. |
| Missing value | A source record without the request reference | Correct the record or mapping before sending to that recipient. |
| Configured button | The button and action available in your account | The label matches the intended next step and the received button performs it. |
Check the approved version on a recipient's device
- After review, refresh Approved templates and check the final text, language and category. Follow the review guide if the template is missing or rejected.
- Select that approved template in the CRM, help desk or other connected tool you intend to use. Send a test with the review values to a recipient who agreed to receive it.
- Inspect the actual received message. Check line breaks, longer values, characters, the visible opening and any expanded text. Test Android and iPhone separately if both are part of your audience; do not assume a universal number of visible lines.
- Check each available button. For a link to a website or app, use the link test checklist.
- Record the template name, language, sending tool, test date and what needs correction. If the fixed wording needs a change, follow the supported review process and confirm that the version you will send is approved. Use the sending guide for variable mapping and delivery problems.
A message that looks correct in a sample or tool preview may still contain wrong recipient data, a broken button or a sending error. Complete the permitted test before a larger send. This checklist does not confirm support for Authentication templates or OTP-specific preview controls; verify that workflow with ChatArchitect support before planning it.
No comments to display
No comments to display