This guide explains, step-by-step, how Indian businesses can complete DLT (Distributed Ledger Technology) registration and PEM chain mining, and then use the approved DLT Template ID while creating an SMS campaign in NotifyVisitors.

The article covers the process in three parts:

• DLT Registration
• PEM chain mining (PE-TM binding)
• Sending broadcast SMS campaign via NotifyVisitors

What is DLT and who needs it?

DLT is the operator-run system in India that verifies organizations (Principal Entities), Sender IDs (Headers), end-user consent, and pre-approved SMS content templates to curb spam. Registration is mandatory for any business sending SMS to Indian numbers.

Quick overview of the DLT steps:

1. Choose an operator portal and register your organization (Principal Entity)

Popular portals: Airtel (Trubloq), Jio (Trueconnect), Vodafone-Idea – Vi (VILPOWER), BSNL. You only need to register on one operator; your records are recognized across networks.

• Airtel: signup at dltconnect.airtel.in → Enterprise  (Click here for step-by-step tutorial)
• Jio: trueconnect.jio.com → Register now (Click here for step-by-step tutorial)
• Vi: vilpower.in → Signup/Login → Enterprise
• BSNL: ucc-bsnl.co.in → Signup

2. Prepare KYC documents

Typical requirements include:

• Business PAN
• Proof of business entity (GST certificate / Certificate of Incorporation / Shop & Establishment, etc.),
• Letter of Authorization
• Authorized signatory ID.

Check your chosen portal’s checklist.

3. Register your Sender ID (Header)

Sender ID (a.k.a. “Header”) is the “From” name that shows on the recipient’s phone for your SMS. In India’s DLT system, every SMS must be sent under a registered Header that belongs to your business (your “Principal Entity”).

Types of Headers

A. Alphabetic Header (for Transactional & Service messages)

• 3–6 letters only, usually 6 and UPPERCASE (e.g., NVCRO, ACERCO).
• Should look like your brand/trade name (not a generic like OFFERS).
• This is what people will see as the sender for OTPs, alerts, updates, etc.

B. Promotional Header (for marketing/promotions)

• Numeric, assigned by the operator (you don’t get to brand it).
• Recipients typically see a short numeric code (e.g., 55246); put your brand in the SMS body.

Click here for header registration process on Airtel.

Click here for header registration process on Jio.

4. Register a Consent Template

(needed for Service Explicit and Promotional traffic)

A consent template is the terms & conditions your customer agrees to (on your site/app/form) that says you may send them SMS.

For Service Explicit and Promotional messages, you have to get your consent template approved before applying for content templates. For Transactional or Service Implicit, you can skip this step as user consent is not required for these categories.

Click here for Consent Template registration process on Airtel.

Click here for Consent Template registration process on Jio.

5. Register your Content Templates.

Content templates are the exact SMS wording (with variables) you’ll send. Every message you send in India must match an approved DLT content template and carry its DLT Template ID. You are also required to choose the right category for each content template:

Transactional – Banks/regulators only (OTPs, balance/txn alerts, fraud warnings).

Service Implicit – One-to-one updates from an existing action/relationship (appointments, orders, shipping, non-marketing alerts, non-bank OTPs).

Service Explicit – Informational messages sent after opt-in (newsletters, tips, membership info; no offers).

Promotional – Marketing (offers, discounts, launches, lead-gen).

Variable rules:

• Use {#var#} exactly; same case, same braces and hash.
• Each variable’s value should usually be ≤ 30 characters (keep names, codes, links short).
• Don’t make a template that’s only variables; DLT wants fixed text too.

Good example

• Works because the fixed text is present, variables are only for the changing parts (name, order no., URL).

Bad example (will be rejected)

• All variables, no fixed text/brand.

Tip for long links: If your tracking URL is long, use two variables back-to-back ({#var#}{#var#}) or use a short link (recommended) that maps to your domain.

Click here for Content Template registration process on Airtel.

Click here for Content Template registration process on Jio.

Best-practice tips for content templates

• Timing & DND: Promotional SMS are limited to operator “daytime” hours (09:00–21:00 IST). Transactional messages are allowed 24×7. Always check your operator’s current window.
• Keep spacing in your message exactly as approved; avoid double spaces and stray punctuation.
• Mention your brand in the text.
• For long dynamic links, request two variables {#var#}{#var#} or whitelist the full URL domain.

6. Whitelist your CTAs (links & numbers)

Before you send SMS that contain any call-to-action (CTA) like a web link, app/APK link, WhatsApp/OTT link, or a callback phone number, you must register (whitelist) those destinations on your DLT portal. Messages with unregistered CTAs are often blocked at operator scrubbing.

PEM chain mining

Once your header, consent, and content templates are approved, the last step is to create a PEM chain mining (also known as PE-TM binding) before beginning to send broadcast SMS. PEM chain mining is the trust chain that lets DLT route your SMS:

Client (Principal Entity) → Telemarketer Aggregator (Tagnpin) → Telemarketer Delivery (Infobip).

Here is a step-by-step process to create and get the PEM chain approved:

1. Client starts the request on their DLT portal

   • Portal examples: Airtel, Jio.
   • Action: create/initiate “PEM chain mining” (linking your entity to a telemarketer).

Click here for the step-by-step process to link your entity to a telemarketer on Airtel.

Click here for the step-by-step process to link your entity to a telemarketer on Jio.

2. Tagnpin approves & binds the delivery partner

   • Tagnpin logs in as telemarketer aggregator (ID 1202173348809103373).
   • Opens Pending for approval → selects the request → chooses role telemarketer aggregator → Accepts.
   • Binds it to the delivery telemarketer [for example, Infobip (ID 110200001152)] → Submits.

3. Delivery Telemarketer’s regulatory team approves (≈ 30–60 min)

   • Tagnpin screenshots the submitted chain request.
   • Emails regulatory (example: Infobip) with the screenshot + the DLT portal details, asking for chain activation.
   • When approved, the chain status in the portal flips to active.

4. Client does the final approval

   • The request returns to the Client (e.g., Acer) for the last confirmation.
   • Client logs back into their DLT portal → approves the pending chain.
   • On approval, the chain is fully active, and SMS can be delivered on live routes.

Sending broadcast SMS campaign via NotifyVisitors

Once your entity, header, (consent if needed), and content template are approved on DLT and you have the DLT Template ID, you can start sending broadcast SMS campaigns.

1. In NotifyVisitors, go to Campaigns → Create new campaign → SMS. Click here for a detailed tutorial. 

2. On the Content page (Page 2):

   • Sender Mobile: select the “From” number as per your SMS service provider.
   • DLT ID: Paste the approved DLT Template ID (a.k.a. Content Template ID) you received from the DLT portal. (This field is required for Indian routes.)

• Message: Type the SMS exactly as approved on DLT. Replace DLT variables {#var#} with NotifyVisitors personalization tokens (insert with @), but keep the fixed text identical to the DLT template.

Example: mapping variables

DLT template (Service Implicit):

Dear {#var#}, your order has been shipped.

NotifyVisitors message:

Dear @first_name, your order has been shipped.

As long as the fixed parts (“Dear”, “your order”, “has been shipped.”) match exactly, the message will pass DLT scrubbing.

• Service Provider: pick your configured SMS provider for delivery.

Troubleshooting DLT rejections

• Wrong category (e.g., using Transactional when you’re not a bank/OTP): fix the category.
• Variable format wrong or variable too long (>30 chars): use {#var#} and keep values short.
• Sending outside promo hours/DND blocked: schedule inside the allowed window or switch to permitted categories with consent as applicable.
• Links not whitelisted: whitelist CTAs or split long URLs into two variables.

FAQs