According to TRAI’s regulation on unsolicited commercial communication, all telecoms must verify every SMS content before delivering it (Template scrubbing). For this, all the businesses using SMS must register Entities, SenderIDs, and SMS templates on a centralised DLT portal.
Below are the steps to register the SMS template in a centralised DLT portal and to add the template in the SMS country portal (Service provider).
Step 1: Visit the Airtel DLT portal (AIRTEL DLT ) and select your area of operation as Enterprise then click on next.
Step 2: Login into the portal by entering the proper credentials and OTP.
Contact the HR manager for the credentials and the OTP.
Step 3: Select the Template from the option and click on Content Templates.
Click on the Add button to go to the next section.
Step 4: Select the option mentioned in the image below.
Note: a) For placeholder text (dynamic text in message) mention {#var#} in the message. Each {#var#} can contain 0-30 characters. If dynamic text is supposed to cross 30 characters in length, then two {#var#} have to be mentioned side by side. Now the dynamic text can be up to 60 characters. Example:- Hi Citizen, &#xNAN;Click on this link to pay the bill {#var#}{#var#} &#xNAN;EGOVS b) Mentioning EGOVS at the end of every message is mandatory. c) Select the Template message Type as Regional if the message is in any other language besides English.
After clicking on the Save button, the template is added to the portal. Wait for the approval of the template. Once the template gets approved save the template ID and the message.
Step 5: Repeat the process from Step 3 to Step 4 to register the template in the DLT portal.
Note: The below steps are to add approved templates in the SMS Country web portal. These steps might vary between service providers but the data required for any service provider would be the same.
Step 6: Enter the credentials to log into the SMS Country portal.
Contact the HR manager for the credentials.
Step 7: Select the option Features, then click on the Manage button under the Template section.
Then click on the Add DLT Template button.
Step 8: Mention the template ID and message of the approved template which we saved earlier in step 4. Select the Sender ID as EGOVFS.
After adding all the above details click on Add Template button. The DLT-approved template is added to the SMS Country portal and is ready to use.
Select the ISLanguage check box if the message is in any other language besides English.
Step 9: Repeat Step 7 and Step 8 to add the approved template in the SMS Country portal.
Configuration of the notification messages for a business service based on the channel for the same event.
For a specific action of the user, he/she will get an SMS and email as an acknowledgement.
Users can get SMS, Event, and email based on different channels.
The application allows one to either send different messages across all channels based on their actions.
To have this functionality for different business services, a channel names file was created and added to the MDMS data.
It contains information about the combination of different actions and channels for a particular business service. Example below:
The different channels are
SMS: ID (Mobile Number)
Event
Email: ID (Email ID)
This feature enables the functionality that checks for the channels present in the file and sends the notifications accordingly.
For the SMS event, it would send the SMS notification and log “Sending SMS Notification” for the Event it would log, “Event Notification Sent”, and for Email, it would log, “Email Notification Sent”.
To add/delete any particular channel for a business service -
Update channelNames array in the Channel List file and add/delete the channel you want a business service’s action to have.
Restart egov-mdms-service to apply the changes.
Configure your business service - follow the steps mentioned below.
Adding details about the particular action and the channels you want that action to trigger in the Channel List file in egov-mdms-data repository.
For any record that comes into the topic first, the service should fetch all the required data like user name, property id, mobile number, tenant id, etc from the record that we fetched from the topic.
Respected localization templates should be upserted before in the required environment using the localization service. Restart the localization service to have the newly updated templates available.
Then we should fetch the message content from localization and the service replaces the placeholders with the actual data.
Then put the record in whichever channel’s Kafka topic that the sms, event or email service is listening to.
Then the respective channel services (sms, event, email) will send out the notifications.
