How to send bulk sms notifications to the customers??????

[Divya K1]

How to send bulk SMS notifications to the customers informing them about the arrival time of Field Technician from servicenow?

Guide me

[SN_Learn]

Hi @Divya K1 ,

Please check the below references:

How to setup a SMS Email Notification in ServiceNow 

ServiceNow Notify | How to send SMS 

How to send SMS Notifications 

Mark this as Helpful / Accept the Solution if this helps

[Its_Azar]

Hi there @Divya K1 

You can integrate with an SMS service provider. First, set up an outbound REST message to your SMS service provider. Then, create a business rule or a scheduled job that triggers when the field technician's arrival time is updated. Use the outbound REST message to send SMS notifications in bulk. make sure you have all the necessary customer contact information and permissions to send SMS notifications. This will automate the process of informing customers efficiently.

If this helps kindly accept the response thanks much.

[Vaishnavi Lathk]

Hi @Divya K1  ,

To have SMS messages come directly to your phone you have two choices:

1) Leverage a notification -> SMS gateway like Notify

2) Leverage the carrier's email -> SMS gateway, and use email notifications

If you register a mobile device in your profile in ServiceNow, then ServiceNow will attempt to do #2.

More information on enabling SMS Channels for Notifications can be found here:

https://docs.servicenow.com/bundle/rome-servicenow-platform/page/administer/notification/task/create...

The above is done by the USER to activate their own device for notifications via this channel.

If you want to proactively perform those notifications, then you'd have to determine the appropriate Email gateway for the carrier and then use that email address in your notification.  Best practice would be to allow users to do this on their own, so the platform doesn't have to be hard-coded.

Here is the implementation:

1. Create an email notification
   
   • It's necessary to create a normal email notification on the instance.
   • SMS messages are normally limited to 140 characters so make sure the message length in the email notification is under this limit otherwise it may be truncated.
   • Note: There is an "SMS alternate" field on the [What it will contain] tab in the Advanced view of any email notification.
   • Users can create a brief short message dedicated for SMS when this email notification could be used for multiple purposes, both email and SMS device, at the same time.
2. Create an SMS service provider
   
   • Please consult the documentation: Create a service provider
   • All the created notification service provider records are stored in the table cmn_notif_service_provider.list on the instance.
   • Note 2.1: Make sure the Active box is checked for the service provider used to send the SMS notification.
   • Note 2.2: When troubleshooting any SMS notification issue it is necessary to narrow down the scope to check whether the SMS notification or the SMS service provider have any issues. In that case, you can test SMS notifications by switching to any OOB service provider.
   • If the email notification can be triggered successfully then the system will always create an SMS notification record in the sys_email table, just like an email record. This will prove email notification has no wrong configuration and the issue is related to the SMS service provider. If not, then it is easy to know something wrong must be in the email notification configuration.
3. Create and select an SMS device for a specific user
   
   • When any specific user is chosen to receive the SMS notification then it is necessary to create an SMS device for this user if there is no one on the instance.
   • Steps can be referred from the below docs link. Select a service provider
   • Note 3.1: When creating a new SMS device, please make sure you use the following values:
     
     • • Type: SMS
       • User: sys_user record which is being selected as the recipient for the SMS notification
       • Phone number: the phone number to receive the SMS notification, SMS will be sent to address with format <phone number>@<SMS Provider Email Suffix>. The latter part after @ is the email suffix configured on the SMS service provider record in step 2. In the below screenshot, the address would be "123-456-7890@example.com".
       • Service provider: service provider record created in step 2
       • Primary email: false (because this device is used for SMS only)
       • Active: true
   • Note 3.2: In ServiceNow, all the notification-related devices are stored in the cmn_notif_device.list table. This includes standard email, SMS, and Push notification devices.
   • When troubleshooting SMS notification issues it is necessary to look up the customer's SMS notification device record in this table to see if any misconfigurations.
4. Enable the SMS device and the SMS Notification in User Notification Preference
   
   • Note 4.1: Make sure the SMS device is enabled in the Notification Preference for the recipient user. In this screenshot, the "Mobile" SMS device is enabled.
   • Note 4.2: Make sure SMS email notification is enabled for this SMS device in user Notification Preference as well.
   • In this screenshot, the email notification "Incident commented_1" is enabled for the "Mobile" SMS device.

Set up an SMS Email Notification Subscription

Sometimes users may only want to subscribe to an SMS email notification without being selected as a recipient in the SMS email notification.

The configuration steps are nearly the same with only two differences.

1. Create an email notification
   
   • Same as the previous step 1. The only difference is to make the notification subscribable by checking the [Subscribable] check box on the [Who will receive] tab in the email notification.
2. Create a Notification Subscription record

   For notification subscription, ServiceNow stores all user subscription records in sys_notif_subscription.list table for all notifications.

   The user needs to create a new one if there is no subscription record in this table. Please make sure these values are used:

   • User: sys_user record which subscribed to the SMS notification
   • Notification: SMS notification name. In the below screenshot, the notification name is "Incident commented_1"
   • Send to: SMS device name. In the below screenshot, the SMS device name is "Mobile"
   • Table: Table name on which the SMS notification is created. In the below screenshot, the table name is "incident"
   • Active: true

Note: When troubleshooting SMS Notification Subscription issues, first check if there is a corresponding SMS subscription record created in the sys_notif_subscription.list table. If any, then continue to check to see if there is any misconfiguration in that SMS subscription record.

After all the above steps are completed correctly, trigger the SMS notification. A new sys_email record will be created and sent to the SMS email address.

Mark my answer correct & Helpful, if Applicable.

[Vaishnavi Lathk]

Hi @Divya K1  ,

To have SMS messages come directly to your phone you have two choices:

1) Leverage a notification -> SMS gateway like Notify

2) Leverage the carrier's email -> SMS gateway, and use email notifications

If you register a mobile device in your profile in ServiceNow, then ServiceNow will attempt to do #2.

More information on enabling SMS Channels for Notifications can be found here:

https://docs.servicenow.com/bundle/rome-servicenow-platform/page/administer/notification/task/create...

The above is done by the USER to activate their own device for notifications via this channel.

If you want to proactively perform those notifications, then you'd have to determine the appropriate Email gateway for the carrier and then use that email address in your notification.  Best practice would be to allow users to do this on their own, so the platform doesn't have to be hard-coded.

Here is the implementation:

1. Create an email notification
   
   • It's necessary to create a normal email notification on the instance.
   • SMS messages are normally limited to 140 characters so make sure the message length in the email notification is under this limit otherwise it may be truncated.
   • Note: There is an "SMS alternate" field on the [What it will contain] tab in the Advanced view of any email notification.
   • Users can create a brief short message dedicated for SMS when this email notification could be used for multiple purposes, both email and SMS device, at the same time.
2. Create an SMS service provider
   
   • Please consult the documentation: Create a service provider
   • All the created notification service provider records are stored in the table cmn_notif_service_provider.list on the instance.
   • Note 2.1: Make sure the Active box is checked for the service provider used to send the SMS notification.
   • Note 2.2: When troubleshooting any SMS notification issue it is necessary to narrow down the scope to check whether the SMS notification or the SMS service provider have any issues. In that case, you can test SMS notifications by switching to any OOB service provider.
   • If the email notification can be triggered successfully then the system will always create an SMS notification record in the sys_email table, just like an email record. This will prove email notification has no wrong configuration and the issue is related to the SMS service provider. If not, then it is easy to know something wrong must be in the email notification configuration.
3. Create and select an SMS device for a specific user
   
   • When any specific user is chosen to receive the SMS notification then it is necessary to create an SMS device for this user if there is no one on the instance.
   • Steps can be referred from the below docs link. Select a service provider
   • Note 3.1: When creating a new SMS device, please make sure you use the following values:
     
     • • Type: SMS
       • User: sys_user record which is being selected as the recipient for the SMS notification
       • Phone number: the phone number to receive the SMS notification, SMS will be sent to address with format <phone number>@<SMS Provider Email Suffix>. The latter part after @ is the email suffix configured on the SMS service provider record in step 2. In the below screenshot, the address would be "123-456-7890@example.com".
       • Service provider: service provider record created in step 2
       • Primary email: false (because this device is used for SMS only)
       • Active: true
   • Note 3.2: In ServiceNow, all the notification-related devices are stored in the cmn_notif_device.list table. This includes standard email, SMS, and Push notification devices.
   • When troubleshooting SMS notification issues it is necessary to look up the customer's SMS notification device record in this table to see if any misconfigurations.
4. Enable the SMS device and the SMS Notification in User Notification Preference
   
   • Note 4.1: Make sure the SMS device is enabled in the Notification Preference for the recipient user. In this screenshot, the "Mobile" SMS device is enabled.
   • Note 4.2: Make sure SMS email notification is enabled for this SMS device in user Notification Preference as well.
   • In this screenshot, the email notification "Incident commented_1" is enabled for the "Mobile" SMS device.

Set up an SMS Email Notification Subscription

Sometimes users may only want to subscribe to an SMS email notification without being selected as a recipient in the SMS email notification.

The configuration steps are nearly the same with only two differences.

1. Create an email notification
   
   • Same as the previous step 1. The only difference is to make the notification subscribable by checking the [Subscribable] check box on the [Who will receive] tab in the email notification.
2. Create a Notification Subscription record

   For notification subscription, ServiceNow stores all user subscription records in sys_notif_subscription.list table for all notifications.

   The user needs to create a new one if there is no subscription record in this table. Please make sure these values are used:

   • User: sys_user record which subscribed to the SMS notification
   • Notification: SMS notification name. In the below screenshot, the notification name is "Incident commented_1"
   • Send to: SMS device name. In the below screenshot, the SMS device name is "Mobile"
   • Table: Table name on which the SMS notification is created. In the below screenshot, the table name is "incident"
   • Active: true

Note: When troubleshooting SMS Notification Subscription issues, first check if there is a corresponding SMS subscription record created in the sys_notif_subscription.list table. If any, then continue to check to see if there is any misconfiguration in that SMS subscription record.

After all the above steps are completed correctly, trigger the SMS notification. A new sys_email record will be created and sent to the SMS email address.

Mark my answer correct & Helpful, if Applicable.

[Divya K1]

Hi All,

Based on the below guidance, i have created ui messages in different languages then in Business rule using the below syntax but the message is not triggering in different language.

SNC.Notify.sendSMS('+twilio number xxxx', '' + current.u_contact_phone, '' + gs.getMessageLang("uimessage", 'en') + current.number, current);