New SMS Template Configuration & Approval Process

Purpose

The purpose of this documentation is to clearly explain how a new SMS template request is raised by the POD team, how the Solution Enablers (SE) team processes and approves the template, and how the approved template is implemented across Rentlz systems for successful message delivery.

Step-by-Step Process :

1. Identify the requirement for a new SMS template (example: New booking flow, OTP change, cancellation update, etc.)

2. Raise an SE ticket with the following mandatory information: Sample SE for reference -  https://moveinsync.atlassian.net/browse/SE-51016 
   
   

   • Template purpose

   • Full SMS content

   • Suggested template name

   • Assign the ticket to the (SE) Team.
     
     

3. SE team will take over the process from here , It usually takes within 24–48 hours.
   If approved → SE receives a Template ID. If rejected → SE updates POD and POD fixes the issue, and resubmits to SE 

Once the SE team completes the approval process then Rentlz will again Raise a separate SE for configuring the SMS on Consul.

On the new SE Ticket you need to update the approved template , and ask SE to update the same in the Consul Configuration of the required server. 
The new template should be added in the Communicationsmsconfig folder and then based on the template number it should be also added in the details. And then the detail number of that template should be added in the flow of where that template needed ( rider message, driver message etc ).