Consent Templates
TRAI DLT Consent Template Registration & Digital Consent Acquisition
Complete Guide to Customer Consent Management for Compliant Commercial Communication under TCCCPR 2018
Understanding Consent Templates
What is Consent ?
Consent means any voluntary permission given by customer to sender for receiving commercial communication related to specific purpose, product or services. As per TRAI TCCCPR 2018 regulations, consent may be explicit or inferred.
-
If You Give Consent: If you say yes to a company (like a grocery store), they can send you messages even if you told others you don’t want messages from them.
-
If You Don’t Give Consent: You won’t get certain messages unless the company is allowed to send them without asking, like if you did business with them before.
What is a Consent Template?
A Consent Template (CT) is a standardized template of consent which is presented to the customer while acquiring their consent. It clearly mentions:
-
The purpose of the consent
-
Details of the sender (business entity/brand)
-
Scope of communications the customer will receive
-
Type of messages (promotional/service)
-
How to revoke consent
Who is a Consent Acquirer?
Consent Acquirer (CA) means any sender with registered and valid header(s) who acquires consent from end customers through the prescribed process under TCCCPR 2018 regulations.
Key Components of a Consent Template
1
Template Name
A descriptive name that helps you identify the template purpose internally
2
Brand Name
Your registered product/trade name or official business entity name
3
Scope of Consent
Clear, explicit statement about types of communications customers will receive
⚠️ Is Consent Template Registration Mandatory?
Yes, as per TRAI guidelines, it is mandatory to register a Consent Template and acquire consent based on the registered template. Any messages sent without prior customer consent are liable to penalties and may attract strict action against the business enterprise or message sender.
Types of Consent
Consent Type | Description | Validity Period | Application |
|---|---|---|---|
Inferred Consent (Inquiry) | Based on product inquiry or information request | 3 months from inquiry | Follow-up communications |
Inferred Consent (Transaction) | Based on recent purchase or service subscription | 12 months from transaction | Related product/service updates |
Explicit Consent | Directly verified from customer via OTP, recorded on DL-Consent | 12 months | Promotional & Service Explicit messages |
📌 Important Note: Transactional and Service Implicit messages do not require explicit consent acquisition. However, Service Explicit and Promotional messages MUST have customer consent acquired through registered consent templates.
Digital Consent Acquisition (DCA) Process
What is DCA?
The Digital Consent Acquisition (DCA) process is a mechanism designed to request, manage, and withdraw customer consents in accordance with the procedures outlined in TCCCPR 2018. The collected consent data is shared on the Distributed Ledger Technology (DLT) Platform, enabling scrubbing by all Access Providers.
⚠️ DCA is Mandatory by TRAI
The deadline for implementing the DCA process for Telecom operators was 30th September 2023. All consents acquired through DCA are valid; others acquired through non-DCA mode are nullified.
How DCA Works: Subscriber Consent Flow
When a consent request is initiated, the subscriber receives a message from short code 127XXX from their operator. The subscriber can reply with Y (Yes) or N (No).
Initial Message
Subscriber receives consent acquisition message from 127XXX containing enterprise name, brand, and scope of consent
Reminder 1
If no response, first reminder sent after 24 hours
Reminder 2
If still no response, second reminder sent after another 24 hours
Final Window
Customer has 24 hours after last reminder to respond (Total: 72 hours from initial message)
Consent Response Outcomes
Customer Response | Outcome | Validity/Restriction |
|---|---|---|
No Response (after 72 hrs) | ⏱️ Consent Expired | Same consent message cannot be sent for next 90 days |
Replies "N" (No) | ❌ Consent Rejected | Same consent message cannot be sent for next 90 days |
Replies "Y" (Yes) | ✅ Consent Granted - Active Status | Valid for 12 months from date of consent |
✓ Special Note: Customers in Full DND can receive consent acquisition messages. This ensures they have the opportunity to opt-in for communications they're interested in.
Methods of Digital Consent Acquisition
🔌
1. Consent API
Integrate with website, applications, or POS systems for real-time consent acquisition
📱
2. QR Code
Display unique QR code for your consent template - customers scan and provide consent
🌐
3. Web Acquisition
Manually enter customer mobile number on portal to send consent request
📤
4. Bulk Upload
Upload CSV file with up to 50,000 numbers for bulk consent acquisition
Step-by-Step Consent Template Registration Process
Prerequisites - Before You Begin
✓ Active Principal Entity (PE) registration completed
✓ KYC documents verified and approved
✓ At least one header registered and active
✓ Registered mobile number for OTP authentication
01
Login to DLT Portal
Access operator's DLT platform with your PE credentials. Select "Enterprise" as area of operation.
02
Navigate to Templates
Go to TEMPLATES → CONSENT TEMPLATES from the dashboard menu.
03
Click Add Button
Click on "+Add" or "Add New Consent Template" button to initiate new template creation.
04
Enter Template Details
Fill in: Template Name, Brand Name (auto-populated), and Scope of Consent
05
Save & Submit
Review all details carefully and click "Save" to submit for operator approval.
06
Approval Process
Template shows "Pending/WIP" status. Approval typically takes 48-72 hours (excluding non-working days).
07
Template Activation
I'm a paragraph. Click here to add your own text and edit me. It's easy.
08
Link to Content Templates
Map approved consent template to relevant content templates (Promotional/Service Explicit only).
Creating Effective Scope of Consent
The scope of consent should clearly specify:
-
Type of communications (promotional offers, event notifications, product updates)
-
Purpose of messages (marketing, service updates, announcements)
-
Frequency indication (if applicable)
-
Opt-out procedure (optional but recommended)
📝 Sample Scope of Consent - Examples:
Example 1 (Retail):
"Dear Customer, thanks for visiting [Brand Name] today. We would love to stay in touch with you about our new launches and promotions. To continue receiving exciting offers from us on call/SMS, please submit your consent."
Example 2 (E-commerce):
"Dear Customer, we are pleased about your sign up with [Brand Name] today. To receive exciting promotions and offers on SMS/call, please submit your consent."
Example 3 (Real Estate):
"Dear Customer, thank you for submitting your property-related requirement on our website today. We will keep you informed on new listings suited to you. Please give your consent for receiving these listings through call/SMS. [Brand Name]"
Template Naming Best Practices
What should be the consent template name?
The Consent Template Name should ideally be a name which you (the sender) can relate with the purpose of the consent you are trying to acquire from the customer.
✅ DOs for Consent Templates
✓ Choose short, relevant name for easy identification
✓ Use meaningful template names (e.g., "Festival_Offers_2025")
✓ Ensure brand name is relevant and registered to you
✓ Make scope of consent clear, explicit, and specific
✓ Provide complete opt-out information if included
✓ Example: "To opt-out, send SMS as STOP to 56789"
❌ DON'Ts for Consent Templates
✗ Don't use generic names (Template1, ABC, etc.)
✗ Don't mention invalid or irrelevant brand names
✗ Don't enter actual message content in scope
✗ Don't use variables in scope of consent
✗ Don't use other companies' brand names
✗ Don't create very short scope like "consent; SMS to customers"
⚠️ Important Limitations:
-
No Editing: Consent templates cannot be edited once registered/approved. You must create a new template.
-
No Variables: Consent templates should not contain any variables ({#var#})
-
Brand Restriction: Use only brand names officially registered/associated with your company
-
Scope Specificity: Consent scope must be precise to specified product or service as per TRAI mandate
Consent Template to Content Template Mapping
Post approval of consent template by the registrar, enterprises can link these consent templates with their choice of content templates. This mapping is required for Promotional and Service Explicit category messages only.
📌 Note: Transactional and Service Implicit messages don't need consent template mapping.
Two Methods for Mapping
Method 1: During New Content Template Registration
-
Go to TEMPLATES → CONTENT TEMPLATES
-
Click on "+Add" to register new content template
-
While filling content template details, select approved consent template from dropdown
-
Brand name will auto-populate based on consent template
-
Complete content template registration
Method 2: Mapping to Existing Content Template
-
Go to TEMPLATES → APPROVED CONTENT TEMPLATES
-
Find the content template you want to map
-
Click on "Add Consent Template" option
-
Choose approved consent template from dropdown
-
Click Submit to complete mapping
✓ Flexibility Advantage: Same Consent Template can be tagged to multiple Content Templates. This means you don't need to create multiple consent templates for similar communication purposes.
Using Multiple Consent Templates
Can I register more than one consent template?
Yes, you can register multiple consent templates, subject to approval from the Registrar (TSP). There is no limit on the number of consent templates an entity can register.
Is acquired consent applicable to all products?
No. As per TRAI mandate, the scope of consent must be very precise to the specified product or service. Create separate consent templates for different products/services if needed.
Methods to Acquire Customer Consent
1. Consent Acquisition via API
Integrate Consent API with your website, mobile applications, or POS machines for seamless, real-time consent acquisition.
Setup Process:
-
Go to CONSENTS ACQUISITION → CONFIGURATION on DLT portal
-
Enable API access (may require one-time payment)
-
Download API documentation from portal
-
Integrate API endpoints with your systems
-
Test API calls in sandbox environment
-
Go live with production integration
Is API integration mandatory?
No, it is not mandatory. You can use other methods like Bulk Upload, Web Acquisition, or QR Code for consent acquisition.
2. Consent Acquisition via QR Code
Generate unique QR codes for your consent templates. Display these QR codes at physical locations, marketing materials, or digital platforms.
How to Generate QR Code:
-
Go to TEMPLATES → CONSENT TEMPLATES
-
Find your approved consent template
-
Click on "Get QR Code" button
-
QR code generates instantly
-
Click "Download" to save the QR code image
-
Use QR code in marketing materials, store displays, packaging
1
Customer Scans
Customer scans QR code using smartphone camera
2
Landing Page
Redirected to page showing consent template details and scope
3
Mobile Entry
Customer enters mobile number
4
OTP Verification
Customer receives and enters OTP for authentication
5
Consent Message
Customer receives consent acquisition message from 127XXX
Unique QR Codes:
Each approved consent template gets a unique QR code. The same QR code can be downloaded and used across multiple platforms and locations.
3. Consent Acquisition via Web Portal
Manually initiate consent requests through the DLT portal by entering customer mobile numbers.
Web Acquisition Steps:
-
Go to CONSENT ACQUISITION → WEB ACQUISITION
-
Select approved consent template from dropdown
-
Brand name and scope of consent display automatically
-
Enter customer's 10-digit mobile number
-
Click "Generate OTP"
-
OTP sent to customer's mobile
-
Enter OTP received by customer
-
Click "Submit"
-
Consent acquisition message sent to customer from 127XXX
4. Consent Acquisition via Bulk Upload
Upload CSV files with multiple mobile numbers for bulk consent acquisition - ideal for existing customer databases or large-scale campaigns.
Bulk Upload Process:
-
Go to CONSENT ACQUISITION → BULK UPLOAD
-
Click on "Add" button
-
Select approved consent template from dropdown
-
Download sample CSV file format
-
Fill CSV with 10-digit mobile numbers (one per row)
-
Upload completed CSV file
-
System validates file and shows confirmation
-
Verify consent credits available
-
Confirm to initiate bulk consent acquisition
⚠️ Bulk Upload Important Points:
-
Upload only CSV file format
-
Maximum file size: 2MB
-
Maximum 50,000 numbers per file
-
Use only 10-digit mobile numbers
-
No duplicate numbers in single file
-
One consent credit deducted per number
-
Ensure sufficient credits before upload
-
File will be rejected if duplicate numbers found
Consent Credits - Purchase & Management
What are Consent Credits?
To initiate consent acquisition messages to subscribers, you need consent credits. One consent credit is deducted per consent acquisition request sent to a subscriber (includes initial message + 2 reminders).
How to Purchase Consent Credits
1
2
Navigate to Credits
Go to CONSENTS ACQUISITION → CREDITS
Select Credit Pack
Choose credit pack based on your requirement
3
Make Payment
Redirected to payment gateway - complete transaction
4
Credits Added
Credits reflected in your account instantly after successful payment
Credit Usage: Credits are deducted only when consent acquisition message is sent to subscriber. If file upload fails or numbers are invalid, credits are not deducted.
Consent Revocation & Management
Can a Subscriber Revoke Consent?
Yes, subscribers can revoke their consent at any time. They can login to their respective Telecom operator's portals to manage their consents.
Customer Revocation Methods
-
Operator Portal: Login to TSP portal and manage consents
-
SMS to 1909: Send REVOKE <HEADER> to 1909
-
Call 1909: Call toll-free number and follow IVR instructions
-
Mobile Apps: Use TRAI DND app or operator's app
-
Web Portal: Access operator's web portal with OTP authentication
What Happens After Revocation?
-
Consent status changes to "Revoked" on dashboard
-
You can no longer send promotional/service explicit messages to that customer
-
Customer removed from active consent list
-
You can view revoked consents in reports section
-
Customer can provide fresh consent again if they wish
Consent Validity Management
Scenario | Validity Period | Action Required |
|---|---|---|
Revoked by Customer | Immediately invalid | Customer must initiate new consent |
No Response (Expired) | Cannot re-request for 90 days | Wait 90 days before new consent request |
Rejected Consent (N) | Cannot re-request for 90 days | Wait 90 days before new consent request |
Successful Consent (Y) | 12 months from date of consent | Re-acquire consent before expiry |
Consent Template vs Content Template: Understanding the Difference
Many businesses confuse consent templates with content templates. While both are part of the DLT framework, they serve completely different purposes.
Aspect | Consent Template | Content Template |
|---|---|---|
Linking | Can be linked to multiple content templates | Must be linked to one consent template |
Registration Authority | Consent Registrar (DL-Consent) | Content Template Registrar (DL-CT) |
Editing | Cannot be edited once approved | Cannot be edited; create new version |
Variables | No variables allowed | Max 2 non-consecutive variables |
Contains | Purpose, brand name, scope of consent | Actual message with variables |
Visibility | Shown to customer for their agreement | Backend template for message composition |
When Used | Before any communication begins | During every message delivery |
Primary Purpose | Acquire customer permission to communicate | Define actual message content structure |
📌 Key Takeaway: You need BOTH consent templates (to get permission) AND content templates (to send messages). They work together in the DLT ecosystem for compliant messaging.
Frequently Asked Questions (FAQs)
Q1: Is consent template registration mandatory?
Yes, it is mandatory as per TRAI guidelines to register a Consent Template and acquire consent based on the template registered. Any messages sent without prior customer consent are liable to penalties.
Q2: Why is my consent template showing pending status?
Till the time it gets approved by the Operator, the status will be visible as "WIP" (Work in Progress) or "Pending". Usually, the approval process takes 48 to 72 hours excluding non-working days.
Q3: Can I use a brand name not officially registered to my company?
No. Ideally, a Business Entity should use only the Brand Name for which they are registered. Using any other company's brand name is not advisable and is subject to penalty from authorities.
Q4: Can I edit my consent template once it's approved?
No, once approved or submitted, it cannot be modified. You must create a new template and send it for approval.
Q5: I registered a consent template at another operator. Do I need to register again?
No, you don't have to register it again. It will be auto-visible under the Consent Template tab across all operators as it's stored on DLT blockchain.
Q6: Can consent templates be used immediately after registration?
No. The consent templates can be used only after they are approved by the Registrar. Enterprise will be notified post approval.
Q7: Can I acquire consent without registering a consent template?
No. Consent must be tagged to a Consent template while registering consents on DLT platform. Template registration is a pre-requisite.
Q8: Why is it mandatory to register consent template for Service Explicit Messages?
As per TRAI Regulations, any Principal Entity who wishes to send Service Explicit messages to their customers needs to acquire consent. If they do not acquire consent, such messages will not be delivered.
Q9: What is the validity of acquired consent?
The validity of a successfully acquired consent is 12 months (one year) from the date customer replies "Y".
Q10: If customer replies "N", when can I resend consent request?
If a customer replies "N" to the short code, the same consent acquisition message cannot be sent to that customer for the next 90 days.
Q11: Is there a common short code for consent-seeking messages?
Yes, subscribers will receive Consent Acquisition messages from the short code 127XXX from their respective operators.
Q12: What happens to consents acquired earlier in non-DCA mode?
All consents acquired through the DCA (Digital Consent Acquisition) process are valid; others acquired through non-DCA mode are nullified as per TRAI mandate.
Q13: If customer is in Full DND, can they receive consent acquisition message?
Yes, customers in Full DND can receive the consent acquisition message. This ensures they have opportunity to opt-in for communications they're interested in.
Q14: Does DCA affect transactional and service implicit messages?
No, DCA does not affect Transactional and Service-Implicit messages. DCA affects only Service-Explicit and Promotional messages.
Q15: Is acquired consent applicable to all products of the entity?
No. As per TRAI mandate, the scope of consent must be very precise to the specified product or service. Create separate consent templates for different products if needed.
Q16: Can we change the scope of acquired consent?
No. The scope of an approved Consent Template cannot be changed. You must create a new consent template with the different scope.
Q17: Is there a limit on Bulk consent acquisition?
Yes, maximum 50,000 numbers can be uploaded in a single file for acquiring consent in bulk.
Q18: Is API integration mandatory for consent acquisition?
No, it is not mandatory. You have the option to initiate DCA by purchasing Consent Credits and using Bulk Upload, Web Acquisition, or QR Code features.
Q19: Is whitelisting of IPs chargeable?
No, whitelisting of IPs is not chargeable.
Q20: Is creating consent templates chargeable?
No, the creation of consent templates is not chargeable. However, you need to purchase consent credits to initiate consent acquisition messages.