As per the latest TRAI Directions, all Principal Entities (PEs) are required to disclose the entire chain involved in SMS communication,including the Telemarketer-Aggregation function and Telemarketer-Delivery Function, between the PE and OAP According to Clause 10(c) of the TRAI Directive dated 20th August 2024, effective from 1st November 2024, all messages must be traceable. Any message where the telemarketer chain is undefined or incomplete will be rejected by Telecom Service Providers (TSPs). Please find the step in all operators you have to update in your DLT Account. " SMART PING " Go to PE-TM CHAIN CLICK ON NEW REQUEST TELEMARKETER ID Moryaas Digital Pvt Ltd :- 1002400102389177319 CLICK ON VIEW DETAILS YOU CAN FIND :- Moryaas Digital Pvt Ltd CLICK ON SUBMIT REQUEST " VIL POWER " Click on Chain Click on New Chain Name :- Moryaas Digital Pvt Ltd Copy our Telemarket Id : 1002400102389177319 Click on Submit " Airtel " CLICK ON DLT MANAGE SMS WORKFLOW CLICK HERE TO REGISTERED PE/TM RELATIONSHIP MAPPING Come to TELEMARKET FLOW START CREATING SEARCH DLT ID-- 1002400102389177319 SELECT Moryaas Digital Pvt Ltd CLICK ON PROCEED " JIO " TELEMARKET MY TELEMARKETER CREATE NEW CHAIN SEARCH DLT ID -- 1002400102389177319 SELECT TELEMARKET ID Moryaas Digital Pvt Ltd CLICK ON CREATE BUTTON
We would like seek your immediate attention to the Headers & Templates being registered with Airtel . This is agreed within the industry and TRAI to start cleaning up the Templates and Headers which are not as per compliance or not in use as per below directives. 1.Not more than 25 headers to be registered for a single entity , Please share justification in case we need beyond this threshold . 2.In case there are some headers/templates which are no longer in use, PE can self-suspend or share Header/Template on DLT.CARE@airtel.com for suspension. 3.Ensure no Promotion Template content shall be registered under Service Implicit. On such observation we may go ahead and blacklist the template without prior intimation. 4.In case the Header registered name is mismatch with Principal entity name ,We request you to share valid justification to establish the relation between the respective header(s) and the business name. 5.We have observed that templates registered with multiple/consecutive variables and/or vague content, which may be manipulated/misused for sending inappropriate/fraudulent messages also need to get cleaned-up and re-registered as per the industry agreed formats. 6. As per TCCCPR guidelines, any principle entity cannot send messages on behalf of their clients, they should get register themselves as a telemarketer for any such activity. Please reach out to us in case any such Telemarketer activity being done as a PE, in case of non-compliance we may take necessary action on the Principal entity. In absence of any justification not received from your end, we shall take necessary action on the non - compliant registered headers and templates as per established regulations. Note -: Please feel free to connect us at DLT.CARE@airtel.com for any queries.
We are writing to inform you of an urgent update mandated by TRAI w.r.t TCCCPR 2018. This directive requires immediate action to prevent the use of fraudulent CTAs - URLs/ APKs/ OTT Links/ Call back numbers - in customer communications. Action Required: Ensure that all CTAs - URLs/ APKs/ OTT Links/ used in your customer messages are whitelisted on the DLT portal before sending them Whitelisting Deadline: 30th September 2024 Any message containing non-whitelisted or unapproved CTAs will be BLOCKED by all Access Service Providers during DLT scrubbing Under 1st phase of whitelisting Call back number & Email are exempted for scrubbing hence there is no impact if not updated. Types of URLs for Whitelisting: URLs to be whitelisted are categorized as - Static URLs Dynamic URLs Short URLs Social (OTT) Links APK/IPA Links Please follow the key guidelines regarding the whitelisting of URLs, APKs, and OTT links: Static URLs: A static URL must start with 'http://' or 'https://' or 'www' Example: https://www.company.com/products Note: If the entered static URL is redirecting to another URL, it will be rejected during the approval process. Messages will fail during scrubbing if the whitelisted URL does not exactly match. Dynamic URLs: Long Dynamic URL must start with 'http://' or 'https://' or 'www' Enter only the fixed part of the dynamic URL and end with query parameter ('?') Example: https://www.company.com/products?src=web | In this example, 'https://www.company.com/products?' must be whitelisted. Note: If the entered dynamic URL is redirecting to another URL, it will be rejected during the approval process. Messages will fail during scrubbing if the fixed part of the whitelisted long URL does not match. Short URLs: According to TRAI guidelines dated 18.06.2024, short URLs must clearly indicate an association with the sender. The following format must be followed to fulfil TRAI's requirements. Short URL must start with 'http://' or 'https://' Enter only the fixed part of the short URL, followed by the header, and end with '/'. Example: Short URL: https://bit.ly/ABCDBK/xxxxxx | In this example, ‘https://bit.ly/ABCDBK/’ must be whitelisted Only Alpha/Alphanumeric headers will be allowed for short URLs Note: If any of the headers, linked to whitelisted short URLs, are moved to free pool, all associated short URLs will be blacklisted, and any SMS using those short URLs will fail. Social (OTT) Links: Enter a valid social media URL starting with 'http://' or 'https://' or 'www' Example: https://instagram.com/company Note If the entered social URL is redirecting to another URL, it will be rejected during the approval process. Note: Messages will fail during scrubbing if the whitelisted URL does not exactly match. APK/IPA Links: A valid APK/IPA URL should start with 'http://' or 'https://' or 'www' It must end with '.apk' for Android apps or '.ipa' for iOS apps. Examples: Android: https://www.company.com/app/appname.apk iOS: https://www.company.com/app/appname.ipa Note: If the entered apk/ipa URL is redirecting to another URL, it will be rejected during the approval process. Note:Messages will fail during scrubbing if the whitelisted URL does not exactly match IMPORTANT: Responsibility of PEs/Senders: PEs/Senders are solely responsible for ensuring the authenticity of all URLs, APKs, OTT links, and short URLs they whitelist on the TSPs portal. Liability for any issues arising from these whitelisted links rests with the PEs. All URLs included in the SMS content, whether fixed or variable, must be pre-whitelisted in the URL whitelisting module. Any URL that redirects to another URL must be registered and whitelisted as a short URL. Please ensure compliance with these guidelines by 30th September 2024 to avoid any disruption in SMS delivery.
Please gather all your templates/ message content and start uploading them under different categories i.e. Transactional /Service Implicit/Service Explicit /Promotional. Aside for Service explicit and Promotional Messages a special template named as consent template needs to be uploaded and approved. Please refer to the attached Template creation handbook to have clarity over the type of Content templates and consent templates. Similar to the Sender ID upload process, you need to upload these templates with any one operator DLT portal and templates will get synced across all other DLT portals/platforms. You can find the detailed step by step guide for Templates addition as well as definition documents Click here
DLT platforms have incorporated a new set of error codes for messages that are rejected due to failure of various compliance checks. Please ensure your applications have the updated Error Codes mapped. Please find the updated list of error codes click here
Facebook