AtServiceTech

SMS · DLT · GUIDE

DLT SMS Content Template Approval: Registration Steps

Register each message format you plan to send in the DLT portal's Content Template section. The approved text, category, Header, and Template ID must match what you use in your SMS provider.

Steps to submit an SMS Content Template

Template syntax and category names vary by operator. Use the exact format and category in your portal; AtServiceTech's n and y values describe the types accepted by its template form and should match your approved DLT record.

Steps

  1. List the actual messages your application sends, such as account alerts, order updates, OTPs, or offers.
  2. Create a template for each message use case and include the required brand and fixed text.
  3. Mark variable positions with the portal's required syntax, commonly {#var#}. Keep the approved text and variable order consistent with what your application sends.
  4. Select the category and link the appropriate approved Header as required by the DLT portal.
  5. Submit the template and save its approved Template ID, category, exact text, and linked Header.
  • In AtServiceTech, n means Service Implicit and y means Service Explicit or Promotional. Use the type recorded for your DLT-approved template; do not infer it from the example.
  • Use {#var#} for variable positions if this is the syntax required by your DLT portal. Keep each placeholder in the same position and order in the application message.
  • Include your registered business or brand identity in the message where required, and ensure the actual message does not add unapproved text around the approved template.
  • If the portal rejects a template, read its rejection reason, correct the category, Header association, message text, or variable syntax as applicable, and submit a revised template.
  • AtServiceTech's Add Content Template guide explains how to save the approved template in your workspace.
  • Learn about the separate Consent Template workflow.

Write templates and match variable values

A template has fixed text and, where allowed, variable positions. The message sent by your application must follow the approved pattern. For example, an approved message such as Hi {#var#}, order {#var#} is ready from Example Store. has two variable positions; send the corresponding values in that same order as var1|var2 in AtServiceTech's SMS API.

  • Use the DLT portal's exact placeholder syntax. AtServiceTech recognizes {#var#} in saved template text to show the matching variable fields in the workspace composer.
  • Provide one value for each placeholder, in order. Separate multiple values with |; do not include the separator inside an individual value.
  • Keep spelling, punctuation, fixed text, brand wording, and placeholder order aligned with the approved template. Do not send additional unapproved text.
  • When a template is rejected, review the portal's reason, check the selected message category and linked Header, then correct and resubmit the template.
  • Once approved, save the exact Template ID and message text. In AtServiceTech, submit the template with the approved Entity ID, linked Sender ID, type, message text, and supporting evidence.