| 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)
|
| Promotional |
Promotional |
|
| Govt |
Service (Inferred Consent) |
Government messages are classified under Service category
|
| |
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 Blockchain technology.
|
| Delivery Report |
Yes |
No |
Delivery status for promotional messages will not be available post DLT.
|
| 1. Promotional Traffic |
| 2. Transactional Traffic |
Yes |
Yes |
Delivery status for transactional messages will continue to be available post DLT.
|