{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":39769,"path":"platform-administration/t_CreateAServiceProvider.md","title":"Create a service provider","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create a service provider\n\nAdministrators can configure service providers for devices that use SMS.\n\n## Before you begin\n\nRole required: admin\n\n## About this task\n\n**Important:** Service providers such as AT&T and Verizon may soon be deprecating the **email-to-text** functionality. See [Using Notify with SMS](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/c_NotifySMS.md) for SMS delivery.\n\nAdministrators also have the option of configuring how a device's service provider affects the construction of the device's email address.\n\n## Procedure\n\n1. Navigate to the Notification Service Provider \\[cmn\\_notif\\_service\\_provider\\] table by entering `cmn_notif_service_provider.list` in the application navigator filter.\n\n2. Fill out or change the fields on the form \\(see table\\).\n\n3. Select **Update**.\n\n4. Select **Save** on the Notification Preferences page.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nName\n\n\n\nConfigured name of the service provider.\n\n
\n\nType\n\n\n\nType of device, in this case **SMS**.\n\n
\n\nActive\n\n\n\nEnables or disables this notification device.\n\n
\n\nAdvanced notification\n\n\n\nRemoves all the previous options and displays the **Advanced script** field.\n\n
\n\nAdvanced script\n\n\n\nUsed 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.\n\n
\n\nConstruct address manually\n\n\n\nRemoves the prefix and suffix options and displays the **Construction script** field.\n\n
\n\nConstruction script\n\n\n\nEnables 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.\n\n
\n\nSMS Provider Email Prefix\n\n\n\nPlaces the provided text before the device's specified phone number; for example: `PREFIX2223334444@text.att.net`\n\n
\n\nSMS Provider Email Suffix\n\n\n\nPlaces the provided text after '@' sign; for example: `2223334444@SUFFIX`\n\n
\n\nNotification Device Variables\n\n\n\nOptional 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.\n\n
\n- **[Select a service provider](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/t_SelectingAServiceProvider.md)** \nYou can configure how a device's service provider affects the construction of the device's email address.\n- **[SMS notification advanced scripting](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/r_SMSNotificationAdvancedScripting.md)** \nYou can use these objects and their attributes in your advanced notification scripts on the SMS Notification Service Provider form.\n\n**Parent Topic:**[Subscription-based notifications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/c_SubscriptionBasedNotifications.md)\n\n"}}