Configure DLT and KYC compliance for India SMS
Disclaimer: This article describes Zenoti capabilities that SUPPORT compliance with the named regulation. It is NOT legal advice. You are responsible for confirming your own regulatory obligations with your legal counsel and for determining whether Zenoti's settings are sufficient for your jurisdiction and use case.
India's Telecom Regulatory Authority (TRAI) mandates DLT (Distributed Ledger Technology) registration for all commercial SMS senders under the Telecom Commercial Communications Customer Preference Regulations (TCCCPR 2018). Messages from unregistered senders are blocked or filtered by Indian carriers. The regulation covers all commercial SMS — transactional, service, and promotional — and requires organizations to register their brand (Principal Entity), Sender ID, and every content template before sending.
If your organization sends commercial SMS to recipients in India, you must complete DLT registration and submit KYC (Know Your Customer) documents before any SMS marketing campaigns will deliver.
This article describes the DLT/KYC registration prerequisites, the documents required, and the template-approval workflow that lets your organization send SMS marketing campaigns to Indian guests.
Important: DLT registration is a prerequisite for SMS delivery in India. Without it, transactional SMS may be filtered and promotional SMS will be blocked entirely. Plan registration well before your first campaign to India — operator approval can take several business days.
On this page
- Before you begin
- Step 1: Register your organization with a DLT operator
- Step 2: Submit KYC documents
- Step 3: Register a Sender ID (Header)
- Step 4: Submit content templates for approval
- Step 5: Use approved templates in marketing campaigns
- Template categories
- Do Not Call (NDNC) registry rules
- Troubleshooting
Before you begin
- You need access to the Marketing module and SMS campaign permissions.
Permission: Edit (under Campaigns) — Required to register Sender IDs, submit templates, and configure SMS campaigns.
- Your organization must be a registered legal entity in India (Private Limited, LLP, Partnership, Sole Proprietorship, Trust, Society, or HUF).
- You need a Principal Entity ID issued by a TRAI-recognized DLT operator. India's DLT operators include Vodafone-Idea, Tata Teleservices, Jio, Airtel, and BSNL — your organization registers once with one operator, and the registration is shared across operators via the central DLT.
- You need a corporate email address and phone number that match your registered legal entity.
- You need scanned copies of all KYC documents listed in Step 2.
Step 1: Register your organization with a DLT operator
- Choose a TRAI-recognized DLT operator's registration portal (Vodafone-Idea, Tata Teleservices, Jio, Airtel, or BSNL — registrations are interoperable, so pick whichever portal your team prefers).
- Submit your organization's legal name, entity type, GSTIN, PAN (entity-level), and authorized signatory details.
- Pay the DLT registration fee directly to the operator. Fees vary by operator and registration tier.
- Wait for the operator to issue a Principal Entity ID. This ID identifies your organization across all DLT operators.
Note: Zenoti does not perform DLT registration on your behalf. Your organization registers directly with the DLT operator. Once registered, share the Principal Entity ID with your Zenoti CSM to enable SMS marketing for India.
Step 2: Submit KYC documents
DLT registration requires the following KYC documents. Format and validity rules are set by the DLT operator; check your chosen operator's portal for current requirements.
| Document | Required for | Notes |
|---|---|---|
| Certificate of Incorporation | All entity types | PDF copy from the Registrar of Companies |
| GST Certificate (GSTIN) | All entity types | Must be active and current |
| PAN card (entity-level) | All entity types | Permanent Account Number issued to the registered entity, not an individual |
| Letter of Authorization | All entity types | Signed by an authorized signatory; authorizes the signatory to act on the entity's behalf for DLT registration |
| Authorized signatory ID proof | All entity types | Aadhaar, Passport, or Driver's License of the authorized signatory |
The DLT operator validates each document against the Principal Entity ID before issuing approval.
Step 3: Register a Sender ID (Header)
A Sender ID (also called a Header in DLT terminology) is the alphanumeric identifier that appears as the SMS sender on the recipient's device. It is typically 6 characters, all uppercase, and must reflect your brand.
- In your DLT operator's portal, request a Sender ID. Sender IDs are 6 alphanumeric characters and should reflect your brand.
- Submit the Sender ID for operator approval. Approval times vary by operator and entity verification status; plan ahead and check your operator's documented turnaround.
- Once approved, share the Sender ID with your Zenoti CSM so it can be linked to your organization's SMS configuration.
Important: Sender IDs are exclusive — once registered to your entity, no other organization can use the same string. Choose carefully; renaming requires re-registration and operator re-approval.
Step 4: Submit content templates for approval
Every SMS template your organization sends to Indian numbers must be pre-approved by the DLT operator. Templates submitted with placeholder variables (e.g., {#var#}) let you personalize content while keeping the structure approved.
- In your DLT operator's portal, submit each SMS template you plan to use.
- Categorize each template (see Template categories below).
- Use the placeholder format prescribed by the operator (typically
{#var#}for guest name, appointment time, etc.). - Wait for operator approval. Each template receives a unique Template ID once approved.
- Share the approved Template IDs with your Zenoti CSM, who maps them to your campaign templates in Zenoti.
In Zenoti, each campaign that targets Indian numbers must reference a DLT-approved Template ID. The system displays the approval status of each template:
| Status | Meaning |
|---|---|
| Pending | Submitted to the DLT operator; awaiting approval |
| Approved | Operator has approved; safe to use in campaigns |
| Rejected | Operator rejected; revise and resubmit |
Note: Campaigns that reference a
PendingorRejectedtemplate cannot be sent to Indian numbers. Zenoti blocks the send and displays an error.
Step 5: Use approved templates in marketing campaigns
Once your Sender ID and templates are approved, you can use them in marketing campaigns:
- Navigate to Marketing > Campaigns and create or edit an SMS campaign.
- In the Template dropdown, select an approved template — only templates with
Approvedstatus appear in the list for SMS campaigns targeting India. - Fill in the placeholder variables with guest-specific data (Zenoti macros map to the operator's
{#var#}slots). - Schedule and send the campaign.
For general SMS campaign creation steps, see Create a campaign.
India-specific notification setting
| Setting | Description |
|---|---|
| Include business name in notifications | When enabled, the registered business name is automatically prefixed or appended to outbound SMS messages to comply with India DLT requirements. |
Template categories
DLT operators classify SMS templates into four categories. Choose the correct category at submission — the wrong category leads to rejection or, worse, delivery to NDNC-registered numbers being blocked.
| Category | Use for | NDNC-eligible? |
|---|---|---|
| Transactional | Critical, time-sensitive messages tied to a transaction (OTPs, appointment confirmations, payment receipts). | Yes — can deliver to NDNC numbers |
| Service Implicit | Messages that the recipient implicitly consents to by virtue of an existing service relationship (appointment reminders, no-show / cancellation reminders, follow-up messages). | Yes — can deliver to NDNC numbers within the implicit-consent context |
| Service Explicit | Messages requiring explicit consent (e.g., promotional offers tied to an active package or membership). | Partial — requires recorded consent on file |
| Promotional | General marketing offers, campaigns, and discount messages. | No — blocked for NDNC-registered numbers |
No-show and cancellation reminder templates
The no-show / cancellation reminder template aligns with TRAI's Service Implicit category. Submit it in that category to ensure the message reaches both NDNC-registered and non-NDNC-registered recipients without violating the NDNC regulation.
Do Not Call (NDNC) registry rules
The National Do Not Call registry restricts certain promotional content. Zenoti enforces TRAI's NDNC rules at send time:
- Promotional templates (Category: Promotional) are NOT sent to numbers registered in the NDNC registry. The system filters these recipients out at send time and reports the count in the campaign's send summary.
- Transactional, Service Implicit, and Service Explicit templates MAY be sent to NDNC-registered numbers within the constraints of their template category and your DLT-approved content.
You cannot override NDNC filtering — it is a regulatory requirement enforced by both the DLT operator and Zenoti.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| Campaign send to India fails with "Template not approved" error | The selected template's DLT approval status is Pending or Rejected |
Check the template status in your DLT operator's portal. If Rejected, revise per the operator's feedback and resubmit. If Pending, wait for operator approval. |
| SMS delivery report shows large NDNC-filtered count | The campaign uses a Promotional template; many recipients are on the NDNC registry |
Use a Service Implicit or Service Explicit template if your message qualifies (e.g., appointment reminders are Service Implicit). |
| Sender ID not appearing in the dropdown when creating an SMS campaign | The Sender ID has not been linked to your Zenoti organization yet | Share the approved Sender ID with your Zenoti CSM. Once linked, it appears in the SMS campaign Sender dropdown. |
| Template variable mismatch error at send | The variable count in the Zenoti macro list doesn't match the DLT-approved template's {#var#} placeholders |
Verify the macro mapping with your CSM. Each approved template's variable count is fixed; you cannot add or remove variables without resubmitting the template. |
| New entity registration is repeatedly rejected | KYC document mismatch (e.g., GSTIN doesn't match Certificate of Incorporation) | Cross-check all submitted documents against your Certificate of Incorporation. Most rejections are name- or address-mismatch issues. |