Why approved templates still fail: the scrubbing gotchas

Once your template is approved, every message you send is compared against it by the operator at delivery time. The comparison is stricter than most senders expect. The failures we see repeatedly:

• Variable content that looks like new text. A {#var#} field is meant for values such as a name, an amount or an OTP. Pushing a whole sentence, a URL, or an emoji into a variable can trip scrubbing.
• Punctuation and spacing drift. A double space, a changed dash, or a full stop the approved template does not carry is enough to cause a mismatch. Generate messages from the approved text, never retype them.
• Category mismatch. A promotional message sent on a transactional header is blocked. If the intent of a message changes, it needs a template — and often a header — in the matching category.
• Unregistered URLs and callback numbers. Links, shortener domains and call-back numbers used in message content have to be whitelisted on the DLT platform alongside the template.

If your delivery reports show template or header failures, send us the exact message text and the header used and we will compare it against what is registered.