Distributed ledger technology (DLT) is a digital system for keeping and managing the record of sender IDs and template. Distributed ledger technology (DLT) is a digital system for keeping and managing the record of sender IDs and template.
TRAI has introduced an advanced extension of the Block chain – Distributed Ledger Technology (DLT) to prevent spam Guidelines for Distributed Ledger Technology (DLT) for Enterprises
Enterprises need to register with the Operator’s DLT platform by submitting necessary business documents. Enterprises need to select a Registered Telemarketer (RTM) and permit them to perform functions on their behalf.
Enterprises need to acquire consent from consumers (mobile subscribers) through SMS, Web or Mobile App and upload them on the DLT platform. It is mandatory for any entity that intends to send a communication through messaging and voice gateway on the DLT platforms.
Telemarketers and end-users have to register on the DLT platforms separately. Header (Sender ID) registration: Messages are classified into promotional, transactional, service explicit and service implicit which are registered and every header gets a unique Header ID that is shared across other DLT platforms seamlessly. All headers and templates on the platform should be registered.
Content Template Registration: Entities are required to register all their templates on the DLT system. Every template gets a unique Template ID that is shared across other DLT platforms uniformly.
You can go to below Operator DLT Registration portals and select Sphere Edge Ltd
(Affiliate of MOBTEXTING): 1702157354248182157 (Unique Registration ID)
|Pre DLT||Post DLT||Remarks|
|Customer Consent||No||Yes||Verifiable digital records of all customer opt-ins are made available on the platform. Customers can also see all their consents on a single dashboard|
|Customer Preferences||Yes||Yes||Consumers can also select specific day(s) and time band to block (or) receive. Commercial communication in addition to type of category; viz only DND|
|Entity/Enterprise Registration||No||Yes||Entity need to register with originating access provider (OAP) on the platform|
|Telemarketer Registration||Yes||Yes||Telemarketer should now register with originating access provider (OAP) and no longer with TRAI|
|Header Registration||No||Yes||Entity should register all its SMS Headers and Voice CLIs on the platform|
|Type of Messages||Transactional||Transactional||Every template should be registered under one of these classifications: Promotional,Transactional or Service (Implicit or Explicit)|
|Type of Messages||Promotional||Promotional|
|Type of Messages||Govt||Service(Inferred Consent)||Government messages are classified under Service category|
|Type of Messages||Service (Explicit Consent)|
|Scrubbing||Yes (only DND Check for Promotional SMS)||Yes (Promotional & Service Explicit)||Messages will be scrubbed against multiple parameters like Consent, Preference, Header, Template; and not just DND list|
|Complaint Management||Yes||Yes||Telecom operators will now be responsible for complaint resolution|
|Interoperability between telecom Service Providers||No||Yes||Registration details of Entity, Telemarketer, Header, Template will be shared across the network to ensure seamless view|
|100% Traceability||No||Yes||Everything is recorded and shared on the network using Block chain technology|
1. Promotional Traffic
|Yes||No||Delivery status for promotional messages will not be available post DLT.|
|2. Transactional Traffic||Yes||Yes||Delivery status for transactional messages will continue to be available post DLT.|
All Entity /Senders & Telemarketers need to register with originating access provider (OAP) on their DLT platform.
Entity should register all its SMS Headers and Voice CLIs on the platform. Uniqueness check is enabled.
Entity should register all its templates (Customer consent & content) on the platform.
Type of Messages:
Note: All request will be received at Operator and post KYC request will be approve on DLT.
For any further queries kindly contact us.