Resources

DLT registration

The step that blocks most new senders. Here is the whole path, and a tool that checks your template before you submit it.

Template checker

Paste a template before you register it. A template that fails here would have failed at the operator too — after the wait. Nothing you paste is stored.

Template, with {#var#} where it variesA real message, to check it matches (optional)

The path, end to end

1
Register the entity
Your business, once, with the operator DLT portal. You get a Principal Entity ID. Everything else hangs off it.
2
Bind to a telemarketer
The chain that lets a provider send on your behalf. Until this is verified nothing can go out, and it is the step most often left half-finished.
3
Register a sender ID
Six letters, recognisably related to your entity name. The operator appends the category suffix at delivery.
4
Register templates
The exact wording, with {#var#} where the message varies. Fixed text must match exactly when you send.
5
Send
Header and template must share a category, and the message must match the template. We check all of it before it reaches an operator.

Why registrations get rejected

· The header does not obviously belong to the entity. The most common one, and the least explained.
· The template is mostly variables. If almost nothing is fixed there is nothing to approve.
· Promotional content on a transactional template. Categories are enforced at delivery, not just at registration.
· Wording edited after approval. Registration approves exact text. Changing a word later means it no longer matches, and the operator refuses it — which is why we check before submitting rather than after.