Step 1:
Signup here: https://pingconnect.in/entity/register-with (V-con Telecom Operator) ( Please check before paying the fee as operator providing FREE registration; If free click OK on Rs 5900 popup and don't pay Rs 5900 add "00" in place of the payment details).
Payment: Type 00 in the payment option.
Documents:
Like PAN, GST, Proof of Identity, Proof of Address, Authorization Letter (sample- Download)
Verification:
Entity will get OTP on Mobile Number and Verification Link on Registered Email Id.
Login Credentials:
Approval will take around 4-5 days and then Entity will get an Entity ID and Login Credentials on the Registered Email Id by Telecom Operator.
Post Login:
Entity needs to click on "TeleMarketer Request" in the left menu and add TeleMarketer's Id.
Help Doc:
User Manual for Entity/Company Registration- http://9m.io/4BrW
Step 2:
Header (Sender Id):
Once Entity Registration is Approved by DLT Platform, kindly login to that platform, search for Header option and apply the Header (Sender Id).
Step 3: Test Header (Sender Id)
Once the Header is approved on any one of the DLT platforms, it will be automatically synced with the Common Operator Platform in around 24-36 hrs. Once synced, you can use the DLT Approved Headers to send your SMS. If after 36 hrs, your SMS is not getting delivered from the DLT Approved Header, kindly let us know.
Step 4: Add Telemarketer
Once you are registered on DLT Platform (Telecom Operator), got Entity ID and also applied for the Header (Sender Id), then kindly login to DLT Platform and add your SMS service provider as your TeleMarketer.
Our Pingconnect Telemarketer id - 1302158280700499978 AH Web Solutions
Signup here: https://pingconnect.in/entity/register-with (V-con Telecom Operator) ( Please check before paying the fee as operator providing FREE registration; If free click OK on Rs 5900 popup and don't pay Rs 5900 add "00" in place of the payment details).
Payment: Type 00 in the payment option.
Documents:
Like PAN, GST, Proof of Identity, Proof of Address, Authorization Letter (sample- Download)
Verification:
Entity will get OTP on Mobile Number and Verification Link on Registered Email Id.
Login Credentials:
Approval will take around 4-5 days and then Entity will get an Entity ID and Login Credentials on the Registered Email Id by Telecom Operator.
Post Login:
Entity needs to click on "TeleMarketer Request" in the left menu and add TeleMarketer's Id.
Help Doc:
User Manual for Entity/Company Registration- http://9m.io/4BrW
Step 2:
Header (Sender Id):
Once Entity Registration is Approved by DLT Platform, kindly login to that platform, search for Header option and apply the Header (Sender Id).
Step 3: Test Header (Sender Id)
Once the Header is approved on any one of the DLT platforms, it will be automatically synced with the Common Operator Platform in around 24-36 hrs. Once synced, you can use the DLT Approved Headers to send your SMS. If after 36 hrs, your SMS is not getting delivered from the DLT Approved Header, kindly let us know.
Step 4: Add Telemarketer
Once you are registered on DLT Platform (Telecom Operator), got Entity ID and also applied for the Header (Sender Id), then kindly login to DLT Platform and add your SMS service provider as your TeleMarketer.
Our Pingconnect Telemarketer id - 1302158280700499978 AH Web Solutions
As per new DLT guidelines, Registration/Entity/PE Id will be a mandatory SMS parameter. From 19th November 2020, SMS will not be delivered in absence of PE (Entity) Id.
We have come up with an option to add Registration/Entity/PE Id on your SMS panel itself and does not need your developers intervention. So, we recommend you to add the Registration/Entity/PE Id immediately, just a simple 2 min task :)
Kindly login to your registered DLT platform and copy your Registration/Entity/PE Id -http://9m.io/6mol/
Then, login to your SMS panel and map each of your Header (Sender Id) with your unique 19 digit DLT Registration/Entity/PE Id , issued by the Telecom Operator upon DLT registration.
1. To Edit existing Header (Sender Id)
Kindly login to your SMS panel and go to settings section >> Sender Id >> Action >> Add your Registration/Entity/PE Id against each of your Header (Sender Id).
2. To Add a new Header (Sender Id)
Kindly login to your SMS panel and go to settings section >> Add Sender Id >> Select Country >> Add Registration/Entity/PE Id (in case you want to send SMS to India) >> Add DLT approved Sender Id >> Click on Submit.
We have come up with an option to add Registration/Entity/PE Id on your SMS panel itself and does not need your developers intervention. So, we recommend you to add the Registration/Entity/PE Id immediately, just a simple 2 min task :)
Kindly login to your registered DLT platform and copy your Registration/Entity/PE Id -http://9m.io/6mol/
Then, login to your SMS panel and map each of your Header (Sender Id) with your unique 19 digit DLT Registration/Entity/PE Id , issued by the Telecom Operator upon DLT registration.
1. To Edit existing Header (Sender Id)
Kindly login to your SMS panel and go to settings section >> Sender Id >> Action >> Add your Registration/Entity/PE Id against each of your Header (Sender Id).
2. To Add a new Header (Sender Id)
Kindly login to your SMS panel and go to settings section >> Add Sender Id >> Select Country >> Add Registration/Entity/PE Id (in case you want to send SMS to India) >> Add DLT approved Sender Id >> Click on Submit.
SMS Content Template Registration is the next process for DLT and soon SMS will only be delivered if that SMS Content Template is approved on DLT. Kindly ensure to apply the SMS Content Templates separately for each kind of SMS that you are sending.
Step 1: Make a list of SMS Contents that you are sending
You have to identify the SMS that you are sending. To help you identify and find your SMS contents, we suggest you to check these 2 suggestions:
A). If you are using API, you can go to the Flow section in the left menu of your SMS panel and then download the recently used SMS Contents by clicking on the "Download Templates" button (there might be few more SMS which are not here, so check within your team for more such SMSs).
B). You can also export the last 15-30 days' report from your SMS account and check for SMS contents there.
Step 2: Login to DLT Platform
Kindly login to the DLT Platform where you have registered your Organisation or Entity.
Step 3: Go to Content Template Section
Kindly go to the Content Template Section (and not the Consent Template Section) of the respective DLT Platform.
Step 4: Apply for New Content Template
First check the FAQ Doc and then check the below Template Guidelines Docs and Videos specific to the DLT Platform on which you have registered. Then apply for Template Registration.
1. PingConnect (Videocon)- Guidelines Doc | Video
While applying Template on DLT Platform, kindly understand the below categories:
1. Service Implicit: All kinds of purely transactional SMS content should be registered here, like OTPs, Order Placement, Order Tracking, Passwords, etc.
2. Service Explicit: All kinds of promotional content should be registered here, like Discounts, Offers, New Launches, etc.
3. Transactional: All kinds of OTPs that banks will require to complete the banking transactions should be registered here. This category shall be used only by Banks.
Step 5: Changes in SMS API:
Once your SMS Templates are registered on DLT Platform, you have to follow this help doc to make the necessary changes on SMS API or Panel
Download PingConnect Template-Guidelines
Step 1: Make a list of SMS Contents that you are sending
You have to identify the SMS that you are sending. To help you identify and find your SMS contents, we suggest you to check these 2 suggestions:
A). If you are using API, you can go to the Flow section in the left menu of your SMS panel and then download the recently used SMS Contents by clicking on the "Download Templates" button (there might be few more SMS which are not here, so check within your team for more such SMSs).
B). You can also export the last 15-30 days' report from your SMS account and check for SMS contents there.
Step 2: Login to DLT Platform
Kindly login to the DLT Platform where you have registered your Organisation or Entity.
Step 3: Go to Content Template Section
Kindly go to the Content Template Section (and not the Consent Template Section) of the respective DLT Platform.
Step 4: Apply for New Content Template
First check the FAQ Doc and then check the below Template Guidelines Docs and Videos specific to the DLT Platform on which you have registered. Then apply for Template Registration.
1. PingConnect (Videocon)- Guidelines Doc | Video
While applying Template on DLT Platform, kindly understand the below categories:
1. Service Implicit: All kinds of purely transactional SMS content should be registered here, like OTPs, Order Placement, Order Tracking, Passwords, etc.
2. Service Explicit: All kinds of promotional content should be registered here, like Discounts, Offers, New Launches, etc.
3. Transactional: All kinds of OTPs that banks will require to complete the banking transactions should be registered here. This category shall be used only by Banks.
Step 5: Changes in SMS API:
Once your SMS Templates are registered on DLT Platform, you have to follow this help doc to make the necessary changes on SMS API or Panel
Download PingConnect Template-Guidelines
As per the latest DLT guidelines, to send an SMS, first you have to register your SMS Content Templates on the DLT platform and once your SMS Templates are registered on the DLT Platform, the next step will be to pass the DLT Template Id parameter along with the SMS.
For this, you have to follow below steps to make the necessary changes in API or Panel-
Transactional SMS
1. If you are using Flow API (Send SMS via Flow), check this help doc.
2. If you are not using Flow API and using the Send SMS API, check this help doc.
OTP SMS
1. If you are using the latest OTP V5 API, check this help doc.
2. If you are not using the latest OTP V5 API, check this help doc.
For this, you have to follow below steps to make the necessary changes in API or Panel-
Transactional SMS
1. If you are using Flow API (Send SMS via Flow), check this help doc.
2. If you are not using Flow API and using the Send SMS API, check this help doc.
OTP SMS
1. If you are using the latest OTP V5 API, check this help doc.
2. If you are not using the latest OTP V5 API, check this help doc.
Q. Content Template Registration is mandatory on DLT platform?
Ans) Yes, Content Template Registration is mandatory, and passing an approved Template Id along with the SMS will soon be a mandatory parameter. Also, all kinds of SMS content i.e. OTPs, Transactional, and Promotional have to be registered on your respective DLT platform.
Q. What is the format of Variable while applying Content Template on DLT platform?
Ans) On every DLT platform, each Variable should be written as {#var#}. If you use any other format of Variable, it will not be considered as Variable and your SMS delivery will be impacted.
Q. What is the character limit in Variable {#var#} while sending SMS?
Ans) The actual value of the variable while sending an SMS will be maximum 20 characters.
Q. Any limit on the number of variables allowed in a single Content Template?
Ans) 4-5 variables are allowed in one Content Template.
Q. How many Headers (Sender Id) can be associated with a Content Template?
Ans) Multiple Headers can be mapped against the same Content Template during registration. This might be different on different DLT platforms.
Q. How much time does it take to get the approval of the Content Template from the DLT platform?
Ans) Due to a large number of requests you may face some delay in approval, however, a minimum of 2-4 business days wait is expected.
Q. Is adding a Brand Name compulsory for all kind of content template
Ans) Yes, Brand Name is compulsory in all kinds of SMS content: Promotional, Transactional, and OTPs.
Q. Getting rejection on a template with an error "wrong content type selected"?
Ans) Please note, your SMS content should be applied under service implicit or explicit category only. Do not apply under promotional or transactional categories.
Q. Getting rejection on a template with an error "Brand name not added"
Ans) Adding Brand name in an SMS content template is mandatory and should be explicitly mentioned in the SMS body itself.
Ex: Hello {#Var#} Your order with Id {#Var#} has been dispatched for delivery. Team XYZ
Q. Getting rejection on a template with an error "No header associated with the brand name" ?
Ans) This implies that you do not have a Header/ Sender Id of the brand name, you wish to have a template of and hence no- correlation can be built. Ex: If I want to add a template with the brand name Apple, I should have a header related to Apple in my DLT account first, say, iApple.
Note: You cannot apply for a template with your customer's brand name in your DLT account, a new entity registration should be carried out for your customers first.
Q. Have confusion while applying content in service implicit and explicit?
Ans) If you are confused in deciding the SMS content category as Service Implicit or Explicit while applying on the DLT platform, then it is highly recommended to apply the Content Template twice, once with Implicit and once with Explicit. Later, if your Content Template is approved from both of the categories, then kindly use the Template Id of Service Implicit only.
Ans) Yes, Content Template Registration is mandatory, and passing an approved Template Id along with the SMS will soon be a mandatory parameter. Also, all kinds of SMS content i.e. OTPs, Transactional, and Promotional have to be registered on your respective DLT platform.
Q. What is the format of Variable while applying Content Template on DLT platform?
Ans) On every DLT platform, each Variable should be written as {#var#}. If you use any other format of Variable, it will not be considered as Variable and your SMS delivery will be impacted.
Q. What is the character limit in Variable {#var#} while sending SMS?
Ans) The actual value of the variable while sending an SMS will be maximum 20 characters.
Q. Any limit on the number of variables allowed in a single Content Template?
Ans) 4-5 variables are allowed in one Content Template.
Q. How many Headers (Sender Id) can be associated with a Content Template?
Ans) Multiple Headers can be mapped against the same Content Template during registration. This might be different on different DLT platforms.
Q. How much time does it take to get the approval of the Content Template from the DLT platform?
Ans) Due to a large number of requests you may face some delay in approval, however, a minimum of 2-4 business days wait is expected.
Q. Is adding a Brand Name compulsory for all kind of content template
Ans) Yes, Brand Name is compulsory in all kinds of SMS content: Promotional, Transactional, and OTPs.
Q. Getting rejection on a template with an error "wrong content type selected"?
Ans) Please note, your SMS content should be applied under service implicit or explicit category only. Do not apply under promotional or transactional categories.
Q. Getting rejection on a template with an error "Brand name not added"
Ans) Adding Brand name in an SMS content template is mandatory and should be explicitly mentioned in the SMS body itself.
Ex: Hello {#Var#} Your order with Id {#Var#} has been dispatched for delivery. Team XYZ
Q. Getting rejection on a template with an error "No header associated with the brand name" ?
Ans) This implies that you do not have a Header/ Sender Id of the brand name, you wish to have a template of and hence no- correlation can be built. Ex: If I want to add a template with the brand name Apple, I should have a header related to Apple in my DLT account first, say, iApple.
Note: You cannot apply for a template with your customer's brand name in your DLT account, a new entity registration should be carried out for your customers first.
Q. Have confusion while applying content in service implicit and explicit?
Ans) If you are confused in deciding the SMS content category as Service Implicit or Explicit while applying on the DLT platform, then it is highly recommended to apply the Content Template twice, once with Implicit and once with Explicit. Later, if your Content Template is approved from both of the categories, then kindly use the Template Id of Service Implicit only.
DLT Template scrubbing is LIVE, this means your SMS will FAIL in absence of Template Id.
Hence, we are not submitting your SMS to Operator where your have not mapped Template Id (Error 211) and not deducting your SMS BALANCE as well.
Kindly check the below points regarding DLT compliance:
A. If your templates are approved by DLT, check these points:
-- Map your SMS Content Template in API/Panel
-- Make sure you pass the correct combination of Template Id, Header, and SMS Content (Even special characters in your SMS content should be passed exactly).
-- Make sure you pass less than 30 characters in place of a variable; if you need to pass more than 30 characters apply 2 variables {#var#} {#var#}.
-- Make sure that on DLT you have applied variable only in this format {#var#} and not as ##var##; if applied wrongly, kindly apply the template again.
B. If you have still not applied your Templates on DLT, check these points:
-- Apply under Service Implicit or Explicit option only.
Service Implicit: All kinds of purely Transactional SMS contents like OTPs, Orders, Passwords, etc.
Service Explicit: All kinds of Notification and Promotional contents like Offers, New Launches, etc.
-- Kindly ensure to mention your Brand Name in your SMS Template.
-- Make sure that on DLT you have applied variable only in this format {#var#} and not as ##var##.
These key points should be kept in mind before applying Templates on DLT and before integrating Templates in the SMS API:
1. On DLT, standard format of a VARIABLE is {#var#} and not ##var##; in case you have applied wrongly, kindly apply the Template again.
2. Characters passed in a single VARIABLE should be strictly less than equal to 30 characters; in case you need to pass more than 30 characters apply multiple VARIABLES; ex- {#var#} {#var#} {#var#}.
3. To pass a URL of more than 30 characters in your message content, you should apply multiple VARIABLES without space, to allow more characters; ex- {#var#}{#var#}{#var#}.
For any concerns, just reply to this mail and trust us to help you with the solution.
Hence, we are not submitting your SMS to Operator where your have not mapped Template Id (Error 211) and not deducting your SMS BALANCE as well.
Kindly check the below points regarding DLT compliance:
A. If your templates are approved by DLT, check these points:
-- Map your SMS Content Template in API/Panel
-- Make sure you pass the correct combination of Template Id, Header, and SMS Content (Even special characters in your SMS content should be passed exactly).
-- Make sure you pass less than 30 characters in place of a variable; if you need to pass more than 30 characters apply 2 variables {#var#} {#var#}.
-- Make sure that on DLT you have applied variable only in this format {#var#} and not as ##var##; if applied wrongly, kindly apply the template again.
B. If you have still not applied your Templates on DLT, check these points:
-- Apply under Service Implicit or Explicit option only.
Service Implicit: All kinds of purely Transactional SMS contents like OTPs, Orders, Passwords, etc.
Service Explicit: All kinds of Notification and Promotional contents like Offers, New Launches, etc.
-- Kindly ensure to mention your Brand Name in your SMS Template.
-- Make sure that on DLT you have applied variable only in this format {#var#} and not as ##var##.
These key points should be kept in mind before applying Templates on DLT and before integrating Templates in the SMS API:
1. On DLT, standard format of a VARIABLE is {#var#} and not ##var##; in case you have applied wrongly, kindly apply the Template again.
2. Characters passed in a single VARIABLE should be strictly less than equal to 30 characters; in case you need to pass more than 30 characters apply multiple VARIABLES; ex- {#var#} {#var#} {#var#}.
3. To pass a URL of more than 30 characters in your message content, you should apply multiple VARIABLES without space, to allow more characters; ex- {#var#}{#var#}{#var#}.
For any concerns, just reply to this mail and trust us to help you with the solution.