---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration
Release :
- xanadu
ft:locale :
- en-US
ft:publication_title :
- Xanadu ServiceNow AI Platform Administration
ft:clusterId :
- platadm
bundleId :
- platadm
workflow :
- Platform
---
# Create a service provider
# Create a service provider {#ariaid-title1}
* Release version: Xanadu
*
* Updated August 1, 2024
*
*  1 minute to read
Administrators can configure service providers for devices that use SMS.
## Before you begin
Role required: admin
## About this task
Important:
Service providers such as AT\&T and Verizon may soon be deprecating the email-to-text functionality. See [Using Notify with SMS](https://www.servicenow.com/docs/access?context=c_NotifySMS&version=xanadu&pubname=xanadu-servicenow-platform&ft:locale=en-US) for SMS delivery.
Administrators also have the option of configuring how a device's service provider
affects the construction of the device's email address.
## Procedure
1. Navigate to the Notification Service Provider \[cmn_notif_service_provider\] table by entering cmn_notif_service_provider.list in the application navigator filter.
2. Fill out or change the fields on the form (see table).
3. Select Update.
4. Select Save on the Notification Preferences page.
{#t_CreateAServiceProvider__table_fhh_d32_nr__entry__2}
| Field | Description |
|-|-|
| Name | Configured name of the service provider. |
| Type | Type of device, in this case SMS. |
| Active | Enables or disables this notification device. |
| Advanced notification | Removes all the previous options and displays the Advanced script field. |
| Advanced script | Used for custom notifications that run a script rather than construct a traditional SMS/email. This is used when all outbound SMS messages must run through a central SMS hub, as opposed to being sent directly from the instance to the SMS provider. Advanced users can construct a script in this field that will send a notification to an old style numeric pager that can't receive SMS communications. This field is rarely used and employs advanced scripts. Contact your representative to assist you with any advanced SMS scripting. |
| Construct address manually | Removes the prefix and suffix options and displays the Construction script field. |
| Construction script | Enables you to script the email address construction as you would in a business rule. For example, `abc + current.phone_number + def@text.att.net` would construct an email address of `abc2223334444def@text.att.net`. Note: `Current` is a reference to the device, not the service provider, therefore the current.phone_number variable that uses the device's `phone_number` value. |
| SMS Provider Email Prefix | Places the provided text before the device's specified phone number; for example: `PREFIX2223334444@text.att.net` |
| SMS Provider Email Suffix | Places the provided text after '@' sign; for example: `2223334444@SUFFIX` |
| Notification Device Variables | Optional attributes of an SMS device used inside an SMS service provider's Advanced script. This is used to deliver SMS notifications to an internal SMS distribution technology. This is an advanced scripting procedure and isn't necessary for configuring external SMS providers. |
[Table 1. Notification Service Provider form fields]
{#t_CreateAServiceProvider__table_fhh_d32_nr}
* **[Select a service provider](https://servicenow-prod.fluidtopics.net/mhx~X31T1JKG8KR1bNKpGw)**
You can configure how a device's service provider affects the construction of the device's email address.
* **[SMS notification advanced scripting](https://servicenow-prod.fluidtopics.net/46E8jQcuH7VaZKkR9~SlOA)**
You can use these objects and their attributes in your advanced notification scripts on the SMS Notification Service Provider form.