# Integrate With SMS Providers ## Overview DIGIT ships with SMSCountry as the default SMS provider. This document explains how to integrate with other SMS providers. {% hint style="info" %} **Note:** Legal and regulatory requirements for SMS notifications vary across geographies. Adding an SMS provider is a configuration task and must be set up independently for each deployment. SMS messaging should always be configured in line with the acceptable standards and compliance obligations of the respective country. {% endhint %} ## Steps {% stepper %} {% step %} ### Register the message template with the SMS provider Finalise the SMS message to be sent out to the end user. Register the template with the SMS provider on their portal, following their guidelines. Each language template needs to be localised & separately registered. {% hint style="info" %} **Note**: 1. Exact steps to do this will vary depending on the SMS provider. 2. The number of parameters per message, the number of characters and Unicode support for each local language may be limited depending on the SMS provider. Kindly check for these details on the SMS provider's website prior to registering the message templates. 3. SMS providers may also limit the messages per second that can be sent out. {% endhint %} {% endstep %} {% step %} ### Add the notification message to localisation * Add your SMS or notification message (with placeholders like `{id}`, `{date}`) to the Localisation master. * Use the Localisation Upsert API (provided in the [Postman collection](https://api.postman.com/collections/23418568-729c1e55-6010-4763-abf8-332ce0a6f590?access_key=PMAT-01K22TVBD1AHEEPQXV0KY581DP)). * Update the domain URL in API call. * **Example Entry:** ``` { "code": "PGR_CITIZEN_RESOLVE_RESOLVED_SMS_MESSAGE", "message": "Dear Citizen, Your complaint for {complaint_type} with ID {id} submitted on {date} has been resolved by {emp_name}.", "module": "rainmaker-pgr", "locale": "en_IN" } ``` {% hint style="info" %} **Tip:** To support multiple languages, add the same code with different `locale` values (e.g., `hi_IN` for Hindi, or `en_IN` for English or `pa_IN` for Punjabi. {% endhint %} {% endstep %} {% step %} ### Replace placeholders with real data in the code * The code fetches the message and replaces placeholders like `{id}` with actual complaint details. * In the backend, usually in `NotificationService.java` inside the `getFinalMessage()` function. * Use simple replace logic - refer sample below: ``` if (messageForEmployee != null) { messageForEmployee = messageForEmployee.replace("{complaint_type}", localisedComplaint); messageForEmployee = messageForEmployee.replace("{id}", serviceWrapper.getService().getServiceRequestId()); messageForEmployee = messageForEmployee.replace("{date}", date.format(formatter)); messageForEmployee = messageForEmployee.replace("{download_link}", appLink); } if (messageForEmployee.contains("{emp_name}")) { messageForEmployee = messageForEmployee.replace("{emp_name}", fetchUserByUUID( request.getWorkflow().getAssignes().get(0), request.getRequestInfo(), request.getService().getTenantId() ).getName()); } ``` * Each notification is personalised to the citizen and complaint. {% endstep %} {% step %} ### Send the notification * Send the final message to both SMS and InApp (User Events) services. * InApp: Use the user-events service (for app notifications/inbox). Sample code snippet for InApp (User Events) below: ``` if (!StringUtils.isEmpty(finalMessage)) { if (config.getIsUserEventsNotificationEnabled() != null && config.getIsUserEventsNotificationEnabled()) { for (Map.Entry> entry: finalMessage.entrySet()) { for (String msg: entry.getValue()) { EventRequest eventRequest = enrichEventRequest(request, msg); if (eventRequest != null) { notificationUtil.sendEventNotification(tenantId, eventRequest); } } } } } ``` * SMS: Use the notification-sms service. Sample code snippet for SMS - notification-sms below: ``` if (config.getIsSMSEnabled() != null && config.getIsSMSEnabled()) { // Loop through each recipient group (CITIZEN or EMPLOYEE) for (Map.Entry> entry : finalMessage.entrySet()) { if (entry.getKey().equalsIgnoreCase(CITIZEN)) { // Send SMS to CITIZEN for (String msg: entry.getValue()) { List smsRequests = new ArrayList<>(); smsRequests = enrichSmsRequest(citizenMobileNumber, msg); if (!CollectionUtils.isEmpty(smsRequests)) { notificationUtil.sendSMS(tenantId, smsRequests); } } } else { // Send SMS to EMPLOYEE or other recipients for (String msg: entry.getValue()) { List smsRequests = new ArrayList<>(); smsRequests = enrichSmsRequest(employeeMobileNumber, msg); if (!CollectionUtils.isEmpty(smsRequests)) { notificationUtil.sendSMS(tenantId, smsRequests); } } } } } ``` {% hint style="info" %} **Note:** Make sure the below is enabled in your configuration: ``` isSMSNotificationEnabled: true ``` {% endhint %} {% endstep %} {% endstepper %} ## Checklist - Summary * [x] Message added to Localisation (all required languages) * [x] Placeholders are replaced with real data in the code * [x] Notification sent to SMS and InApp (user-events) channels * [x] Relevant config flags are enabled --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.digit.org/complaints-management/complaints-resolution-v2.10/deploy/customise/backend/integrate-with-sms-providers.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.