Registration on DLT India
This is applicable only for India SMS traffic, international traffic submissions kindly ignore. The TRAI Regulation is intended to eliminate spam and fraud in India.
Telecom Regulatory Authority of India (TRAI) in its continuous endeavour to create a cleaner and transparent system in the Indian telecom industry has released a new regulation in July 2018 to curb Unsolicited Commercial Communication (UCC) and enhance mobile subscriber privacy, TCCCPR 18 Telecom Commercial Communications Customer Preference Regulation 2018. The Regulation is intended to eliminate spam and fraud which has been a concern for many years. The regulation has mandated the use of Blockchain technology also known as Distributed Ledger Technology (DLT) to implement the solution.
To send text messages anywhere within India, one needs to register with the telecom operator as an Enterprise. TRAI has currently directed to stop unregistered entities or enterprises and their header traffic.
To offer regulatory compliant solutions in conjunction with TRAI, to create a much wider and a transparent system, We at Saino First is taking various corrective measures. Through this guideline, we would like to inform you about the multiple phases for implementation of the regulation.
Steps to complete the process
Register your business on any operator. You don't have to register on all operators. It will get sync with all platforms automatically. Register yourself with Principal entity or Enterprise. You need to upload KYC documents like Pan Card, GST certification etc. Once you register your company it will generate one request Id. Please keep for future reference. Now, wait for the approval. It can take 1-7 working days.
Once your business approved by the operator you will receive the confirmation email by the operator. You will get your unique entity id.
Login to your account and visit the header section on the platform and upload your sender name. It has two dropdown - Others and Promotional. Select "other" for the transactional message and add sender name with 6 alpha characters. If selected promotional add numeric value of six characters. You can add as many as headers you want. Now, wait for the approval. It can take 1-7 working days.
Once header approved you will get an email confirmation, Now add the template and upload consent on DLT portal.
Update the Saino First team via email support@saino.io to add header name in your account. Once done you can send messages to your customers.
Please note while registering, Select Saino First Network Pvt Ltd as a telemarketer with telemarketer ID 1102475160000010832 (Unique Registration ID). In any case, if you have done the registration with any other Telemarketer on the operator’s platform already, then you need to update Telemarketer ID.
Operator Wise Guide
Register your business on any one operator. You don't have to register on all operators. It will get sync with all platforms automatically.
DLT Entity Registration Process for PingConnect Videocon:
1. Signup Link: https://pingconnect.in/entity/reg-as
2. KYC Documents for PingConnect: KYC docuemnts like PAN Card, GST, Proof of Identity, Proof of Address etc.
3. Authorization Letter: This is a letter on the company's letterhead, where the Director or Owner of the Company will Authorize the person doing this Registration. Authorization Letter formate can be downloaded from here
In case the Director or Owner himself is doing this Registration, he needs to upload a document that shows he is the Director (MoA or GST)
4. Payment for PingConnect: Just type 00 in the payment option. You don't have to pay anything here.
5. Verification: You will get OTP on Mobile Number and Verification Link on Registered Email Id. Please verify the same. (Check Spam folder as well for email)
6. Login Credentials: Approval will take around 2-3 days and then you will get an Entity Id and Login Credentials on the Registered Email Id by Telecom Operator. 7. Login to DLT Account: Add Header to your account. Follow the below path -
Login into your account >> on left panel >> click on the header >> Click on New Header.
Click On header type and select header: Other >> If you are using our Transactional or SendOTP Routes. Promotional >> If you are using our Promotional Route
Click on Category >> scroll down to select your working category, e.g, Education, Real Estate, Technology, Entertainment etc
Enter the Header which matches your Company Name or Brand Name (Ex- Saino will use Sender as iSAINO) and click on 'check availability'. If not available, try another. (Hint - Add Headers name with only 6 alphabet characters only. It should be alphabet only)
Available Sender Id matches the Company Name, then you will get the OTP, Verify the same. Note - If the Header Name does not match your Company Name, then upload a document to prove that brand name belongs to your Company (Header Name will be rejected by Operator id it does not satisfied with the proof).
Once the Header is approved, It will be ready to use.
Registration on the Jio platform
Jio (Website for Signup) https://trueconnect.jio.com/#/
Guide for Consent Templets and Consent Upload
Vodafone idea, MTNL, BSNL Guideline
Vodafone Idea (Website for Signup) - https://www.vilpower.in
MTNL (Website for Signup) - https://www.ucc-mtnl.in/
Airtel Guideline
https://www.airtel.in/business/commercial-communication/help
Click on Content Template Registration
Click on Consent Migration
Click on Consent Template Migration
Notification by Government
DLT Scrubbing Charges
Further, the Telecom operators have released formal communications on charging an additional charge of Rs. 0.025(2.5p) for per SMS on submission basis for all the traffic that is handed over to the DLT platform from 1st August 2020. The surge price will be charged irrespective of the message type or delivery status. This price revision will be over and above the existing commercials, agreed with Saino First.
How to add Template on Saino Platform
To comply with the new regulation you need to follow below 2 steps
1) Add Principle Entity ID
When you register on the operator you will get a unique entity ID (PE id). Update the ID into the profile. One account at Saino can add only one entity ID.
To add the ID visit the profile section of your account or click on below link
https://app.saino.io/app/profile/my-profile
In the profile, Update Profile section you will see the below screen. Add your entity id and click on save.
2) Add Templates which are registered and approved on DLT
Login to Saino account and Go to the dashboard SMS App > Manage > Templates
https://app.saino.io/app/sms/templates
You can add templates in 2 ways
Click on Add Template to add one by One.
To upload in Bulk, Click on Import and upload the file. Download the below sample file
if you using API, there will be no changes required in the message submitting process from your end. We will append these DLT parameters to the messages while submitting to the Operators. You need to upload or add all your templets in Saino Platform under SMS>Manage>Template Section, Update Principle Entity ID in profile. We will map these details in our system and once mapped, we would match your message text to the nearest matching template ID and submit your entity ID and template ID parameters to the operator DLT platforms for scrubbing. This will ongoing process as and when you add any template to your entity, you have to share/update the same in our system too.
Type of Templates
Categories of Messages/calls:
1. Transactional
2. Service-Inferred/Implicit
3. Service Explicit
4. Promotional
1. Transactional message :
Any message which contains One time Password (OTP) and requires to complete a banking transaction initiated by the bank customer will only fall under the category transactional. This will be applicable to all banks, national/Scheduled/Private/Government and even MNC banks.
Illustration of the transactional message:
OTP message required for completing a Net-banking transaction.
OTP message required for completing credit/debit card transaction at a Merchant location.
2. Service Inferred /Implicit:
Service Message (Inferred Consent): Inferred Consent has been defined in the Regulation as a the permission that can be reasonably inferred from the customer’s conduct or relationship between the Recipient and the Sender. Thus, any message, arising out of customer's actions or his relationship with the sender, that is not promotional, and is not in the interest of the customer to block such communications, will be considered as a service message with inferred consent. These messages may or may not be triggered by a subscriber-initiated transaction and will not be blocked for subscribers who have otherwise blocked service messages also.
Illustration of Service Message (Inferred Consent):
Confirmation messages of a Net-banking and credit/debit card transaction.
Product purchase confirmation, delivery status etc. from e-commerce websites.
Customer making the payment through Payment Wallet over E-Commerce website/mobile app and an OTP is sent to complete the transaction.
OTPs required for e-commerce website, apps login, social media apps, authentication/verification links, securities trading, demat account operations, KYC, e-wallet registration, etc.
Messages from own TSP
Periodic balance information, bill generation, bill dispatch, due date reminders, recharge confirmations (DTH, Cable, Prepaid Electricity recharges etc.)
Delivery notifications, feedbacks, periodic upgrades and updates
Messages from retails stores related to bill, warranty
Messages from schools - attendance/transport alerts
Messages from hospitals/clinics/pharmacies/radiologists/pathologists about registration, appointment, discharge, reports
Confirmatory messages from app-based services.
Government/DoT/TRAI mandated messages, advisories, messages from State Govt., LEAs, Local Authorities, Traffic advisories, Election Commission, Disaster Management advisories.
Service updates from car workshops, repair shops, gadgets service centres.
Directory services like JustDial, Yellow Pages.
Day-end/month-end settlement alerts to securities/demat account holders
3. Service Message (Requiring Explicit Consent):
Explicit Consent has been defined in the regulation as consent that has been verified directly from the Recipient in a robust and verifiable manner and recorded by Consent Registrar as defined under these regulations.
Thus, any service message which doesn’t fall under the category of service message (inferred consent) will be sent only against explicit, digitally verified/verifiable consent to service message blocked (having preference ‘0’ i.e. fully blocked) subscribers. There may not be any need for explicit consent to all other subscribers, who have not blocked service messages.
4. Promotional Message:
As per the Regulation, Promotional messages means commercial communication message for which the sender has not taken any explicit consent from the intended Recipient to send such messages.
Thus, any message sent with an intention to promote or sell a product, goods or service. Service content mixed with promotional content will also be treated as promotional. These messages will be sent to the customer after performing the preference and consent scrubbing function as defined in the Regulation.
Templates Validation points
DLT FAQ
What is the diff between Transactional SMS and Service Implicit?
Transactional message: Any message which contains One time Password (OTP) and requires to complete a banking transaction initiated by the bank customer will only fall under the category of transactional.
Service Implicit: Any message, arising out of customer's actions or his relationship with the sender, that is not promotional, and is not in the interest of the customer to block such communications.
What is the content template format?
While creating template, place {#var#} string as variable. Please find below example.
For promotional SMS we have to do the same procedure to whitelist the SMS?
Yes, Every message needs to be whitelisted on DLT platform. Currently, we suggest to upload promotional templates which are on going and will use in future too
What is consent template?
Consent Template: Standard message that is sent to end users of the enterprise for their consent to receive communications from respective enterprise.
Consent Template is bifurcated into 3 section
Template name: Name as per choice
Brand Name: The product/trade name or if they have multiple brand names
Scope of consent: Content they want to send to end users (We would like to send communication regarding all marketing offers and events to our registered customers. {opt-out procedure can also be given}). It should not contain any actual message contents.
Example:
1. Would Like to Send Communication Regarding All Marketing Offers and Events to Our Registered Customers
2. We will send you updates, transactions, recommendations of our services or products being a registered customer with us.
What will happen while sending promotional sms we follow the template but miss it by 2-3 characters? Do we have strictly follow the template word to word?
We recommend to use variable (ie {#var#} ) where you expect changes. Constant part of the template expected to be as it is.
Shall we have to update temp on every telecom (DLT) platform or we have to upload on any one platform?
The template can be uploaded on any one operator's DLT platform and it will internally sync with other DLT platforms.
We have to upload templete on Saino? Or directly we have to upload the temp on dlt platform?
Till DLT goes live with template scrubbing, you have to upload templates on both the platform (ie Saino & DLT)
Msgs to registered clients like offeres or information about product will be considered as Explicit or Implicit?
Service explicit
I, as a company is the principle entity and Saino would be my telemarketer?
Yes, any company who are generator of message has to register as Principle entity and need to tag their platform providers (TM) who take care of delivery of these messages.
So far we got approximately 10-15 templates whitelisted in Saino portal, which falls under Transactional message. Now, do we need to re-register all those whitelisted templates in Telecom Service Provider portal as well, or will this new format applies to newly created templates that we would like to whitelist in future?
You have to upload all existing & new templates on one of the DLT platforms. Also, templates need to be registered for all types of messages (ie Transactional, service & Promotional).
Only once we need to register the template right?
All ongoing & new templates need to be registered on DLT platform. This will be on going activity.
Template uploading is time consuming process. Is there any option to upload templates in bulk? Does the DLT have any API configurations as we have lot of templates. So one-on -one will be very difficult.
As off we have not seen any option with which templates can be uploaded in bulk or API. If operator releases any new feature in future then we will update.
How long to take whitelist the templates? What is TAT for template whitelisting?
TAT depends upon the load of template request, however you can expect response within 48 hrs.
So because of DTL , now we have to login in either vodafone reliance or BSNL to send sms to our end user? is it right? we will not go through Saino?
DLT platform will be used header, templates & consent management. For sending out the messages, you have to connect with one of service/platform provider like Saino
What is Principle entity & Telemarketers?
Principle Entity (PE):- A commercial business (individual or company) dealing with products or services, who would like to communicate with their customers through SMS or voice.
Telemarketer (TM) :-Telemarketer Aggregator: An individual or a company who collects SMS/voice traffic from enterprises, but DO NOT have direct connection with telecom operator.
Telemarketer Delivery: An individual or a company who collects SMS/voice traffic from enterprises, and has direct connection with telecom operator.
Please contact the support team or Account manager if you require any further assistance.
Last updated
