How to set up DLT registration for outbound calling in India (2026 guide)

If you are running any kind of outbound calling or SMS to Indian phone numbers from a business sender, you need to register on DLT. There is no workaround, no grace period, and operators will silently drop your traffic if you skip it.

This is a step-by-step walkthrough of what DLT actually is, who needs to register, and how to get through the process without burning two weeks on rejections.

What DLT is — and what it is not

DLT stands for Distributed Ledger Technology, mandated by TRAI through a 2018 regulation (TCCCPR) and operationalised through the major telecom operators. It is essentially a blockchain-based registry that ties every commercial message and call to a verified business entity.

The three operator DLT portals are:

• Vilpower (Vi / Vodafone Idea) — vilpower.in
• Jio — trueconnect.jio.com
• Airtel — airtel.in/business/airtel-iq/dlt
• BSNL — bsnl.in (rarely used; partner with Vilpower instead)

You register once per portal. Each portal exposes the same registrations to all operators, but in practice most teams pick Vilpower (largest registered base, easiest UI) and only add the others if a customer's number range refuses traffic.

DLT is not the same as NDNC. DLT is "who can send" (the sender). NDNC is "who can receive" (the recipient opt-out). You need both.

Who needs to register

• Any business that sends commercial SMS to Indian phone numbers
• Any business that places outbound voice calls using a registered sender / caller ID
• Any service provider running a dialer or SMS broadcast on behalf of clients
• Pure peer-to-peer messaging (WhatsApp Business chats) does not need DLT

If you are using a managed BSP (MSG91, Gupshup, Karix, Twilio India), they will often onboard you onto their DLT account. That works, but it locks you into their platform — if you switch BSPs later, you have to re-register.

The five-step process

Step 1 — Entity (Principal Entity) registration

Sign up on Vilpower as a Principal Entity (PE). You will need:

• GSTIN
• PAN of the entity
• Authorised signatory's PAN + Aadhaar
• Cancelled cheque or bank verification letter
• Business address proof
• Authorisation letter on company letterhead (template available on the portal)

Cost: ₹5,900 (one-time, includes GST) for Vilpower as of 2026. Approval takes 24-72 hours if the documents are clean.

Step 2 — Header (Sender ID) registration

A Header is the 6-character sender ID that appears in SMS (e.g. DIALQE) or as the registered caller ID display name for voice calls. Register one per use case:

• Transactional headers (OTPs, alerts)
• Service-Implicit headers (delivery notifications)
• Service-Explicit headers (information shared with consent)
• Promotional headers (marketing)

Approval is usually 2-4 hours. Common rejection reasons:

• Header is too generic ("INFOSV", "ALERT") — must reflect your brand
• Conflict with an existing trademark holder's header

Step 3 — Content Template registration

This is where most teams get stuck. Every SMS body and every IVR script you intend to use must be registered as a template. Templates support variables (`{#var#}`) for dynamic content.

For example, an OTP template might be: > "Your dialque verification code is {#var#}. Valid for 10 minutes."

Each template gets a Template ID after approval. You include this ID with every send. If the actual content does not match the registered template, operators block the message.

Cost: free per template. Approval: 1-2 hours.

Step 4 — Consent (where promotional)

For promotional traffic, you also need to register consent — proof that the recipient opted in to receive marketing from you. Forms accepted:

• Web form with explicit checkbox + timestamp
• IVR-based consent capture
• Signed paper form (digitised)

Consent records must be retained for the entire active period plus 90 days.

Step 5 — Telemarketer (TM ID) — only if you call on behalf of clients

If you are an agency / BPO making calls on behalf of multiple end clients, you need a separate Telemarketer registration. The TM is then linked to each client's PE. Most direct businesses skip this step.

Common rejection reasons (and how to fix them)

| Issue | Fix | |---|---| | "Documents do not match" | All names (GSTIN, PAN, bank, address) must be identical character-for-character | | "Template content not matching registered template" | The runtime message must include the same fixed words, in the same order, as the registered template. Only `{#var#}` slots vary. | | "Header rejected — too generic" | Use a header that contains your brand abbreviation, not a category word | | "Authorisation letter does not match signatory" | The signatory's PAN must match the letter; their name must appear on the GSTIN | | "GSTIN inactive / cancelled" | GST portal status check before applying — many teams miss this |

Realistic timeline

• Day 0: PE registration submitted
• Day 1-3: PE approved
• Day 3: Headers + templates submitted
• Day 3-5: Headers + templates approved
• Day 5: Test sending allowed
• Day 7-10: Live volume after a soft ramp

If you are starting from zero, plan for 10 working days to be fully transmission-ready, not the "24 hours" some BSPs market.

DLT for voice calls (often forgotten)

Most teams associate DLT with SMS, but the 2018 TCCCPR also covers voice calls. For outbound dialing:

• The caller ID (DID number) must be registered to the PE
• The IVR script and the agent's opening lines must align with the registered Service/Promotional category
• If you use a third-party BSP, they handle the DID-to-PE linking; if self-hosted on Asterisk, your trunk provider does

dialque handles DLT template linking automatically — every campaign maps to a registered template ID, and the dialer refuses to dial if the campaign's templates are not in an "approved" state. Most teams discover this enforcement the day a template expires.

Renewal and ongoing operations

PE registration auto-renews annually (provided GSTIN is active). Headers and templates do not expire but can be deactivated by the operator if complaints exceed a threshold. Set a monthly reminder to check the Vilpower complaint dashboard — sustained 10+ complaints/lakh-messages will get headers paused.

Frequently asked questions

Can I use my BSP's DLT registration?

Yes for the short term, but you do not own the headers/templates — the BSP does. If you switch providers, you restart from scratch. For any business sending more than 10k messages/month, get your own PE.

What if my entity is foreign-incorporated but sending to India?

You need an Indian entity (subsidiary or branch) with GSTIN to register as a PE. Foreign entities cannot register directly on the DLT portals.

Are international SMS to Indian numbers covered?

Yes if the sender ID is shown. International numeric senders (random shortcodes from outside India) are technically allowed but operators rate-limit and increasingly block them as spam.

Does DLT apply to WhatsApp?

No. WhatsApp Business uses Meta's separate template approval system, not DLT. You will register templates with Meta via your BSP for WhatsApp.

DLT is a one-time setup cost and an ongoing compliance overhead, but skipping it means your traffic silently dies. Plan for two weeks, budget ₹10,000 for registration + one operator setup, and treat the templates as a content-governance discipline rather than a one-shot box-ticking.