Message templates: reusable communication with accurate context

A message template provides a reusable structure for a recurring communication. It can improve consistency, but the final message still needs the right recipient, document and purpose. A polished template with the wrong amount or reference is worse than a simple accurate message.

Variables allow a template to use context from a record, such as a document reference or recipient name. Their usefulness depends on the relevant value being available and meaningful in the sending context.

Templates in DNA

DNA's Message Templates page validates a draft and saves it through a template service. WhatsApp templates also require an account selection in the reviewed save flow. The interface distinguishes a successful save from an environment where the template store is not provisioned.

Saving and submitting for approval are separate operations. If submission fails after saving, DNA can report that the template was saved but not submitted. The returned approval status matters when the sending flow requires an approved template.

A useful template

A fictional invoice-review message should identify the document and explain the requested response. It should not state that payment has been received merely because an invoice link is available. The words must match the actual business event.

Arabic templates should read naturally and preserve the same intent as English. Names and document references need to remain recognisable, while sentence structure should suit the language rather than follow a literal translation.

Check the rendered result

Review the message after variables are filled, including any document link and recipient details. A template preview is not evidence that a message was sent, delivered or read.

Keep ownership of reusable wording clear. Changes to commercial promises, payment instructions or required actions should be reviewed for their actual business meaning before the template is reused widely.