How to Send Text Alerts Directly From ServiceNow

Turn any ServiceNow SMS notification email into an instant, 10DLC-compliant SMS with TextBolt. Reach the on-call engineer before the P1 SLA does.

  • Checkmark Send incident, SLA, change approval, and CAB alerts into text messages
  • Checkmark Works with your 10DLC-compliant toll-free business number
  • Checkmark Replies handled inside ServiceNow proper, not through SMS
Delivery rate
Up to 98% SMS Delivery Rate
Setup time
30 min Setup Time
Team members
Up to 10 Team Members
Shield
Built for teams who can’t afford to miss critical alerts. Trusted by DevOps, IT, and Support teams worldwide.
Send Text Alerts Directly From ServiceNow

What Are the Limitations of ServiceNow’s Default
Notification Setup for SMS Alerts?

ServiceNow routes notifications to email, mobile push (Now Mobile), in-platform banner, and desktop browser, but SMS sits outside that native channel list without the separately-licensed Notify plugin. TextBolt slots in on top of your existing ServiceNow setup. Six challenges ITSM admins, on-call engineers, and platform owners hit when adding SMS to ServiceNow alerting.

No native SMS

SMS Sits Outside ServiceNow’s Native Channel List

ServiceNow supports email, mobile push, in-platform banners, and desktop browser notifications by default, but not SMS. To enable SMS, ServiceNow recommends using the Notify plugin with providers like Twilio, Plivo, or eCall. TextBolt offers a simpler alternative by converting your existing email notifications into SMS. This lets you add text messaging without changing your current notification setup.

Gateways shut down

Carrier Email-to-SMS Gateways Have Shut Down

The lightweight workaround was creating an SMS Service Provider record at cmn_notif_service_provider.list and pointing notifications at @[phone]@vtext.com or @[phone]@txt.att.net. AT&T retired txt.att.net in June 2025. T-Mobile took tmomail.net offline in December 2024. Verizon’s vtext.com shutdown completes by March 31, 2027. ServiceNow customers who relied on that pattern have broken P1 alerts.

Unreliable gateways

Notify + Twilio Requires a Plugin and Developer Time

ServiceNow’s first-party SMS solution uses the Notify plugin with Twilio, Plivo, or eCall, requiring credential setup and Business Rules or Flow Designer to call sn_notify.sendSMS(). Community implementations typically take 1–2 weeks of developer time, with additional Twilio messaging costs, ServiceNow per-fulfiller licensing, and ongoing maintenance for each major Now Platform release.

 Gmail Has No Native SMS Feature

Per-User Device Records Slow Down On-Call Scaling

In Notify-based SMS setups, every recipient requires a sys_user device record with an E.164 number, SMS preference enabled, and channel configuration. Adding rotations or contractors means creating or updating records, adjusting preferences, and revalidating notification templates. ServiceNow doesn’t offer a shortcut to route alerts via phone without admin-level changes across both user profiles and notification settings.

10DLC Compliance

No 10DLC Compliance

The Notify + Twilio path doesn’t produce a 10DLC-compliant audit trail by default unless you register the campaign separately with The Campaign Registry. The carrier-gateway path supported limited replies that landed in email-channel inboxes, but it’s deprecated. ITSM admins and on-call engineers replying “ack” via SMS need a path that closes the loop in a way that’s auditable for SOX, ITGC, and federal-contractor review without forcing a separate IRM platform.

Fragmented teams

Email and Mobile Push Aren’t Built for 2 AM Alerts

ServiceNow’s email channel delivers P1 incident notifications to the on-call engineer’s Outlook inbox, but engineers aren’t sitting in Outlook at 3 AM, and the inbox alone doesn’t make the phone ring. Email delivery delays during incident storms are also documented, especially when the outbound queue backs up behind correlation-rule-triggered notifications from ITOM Event Management.

How TextBolt Adds SMS to ServiceNow

TextBolt connects ServiceNow to a registered 10DLC business number through the same notification-recipient mechanism your records already use. No Notify license, no Twilio account, no per-fulfiller seat for SMS-only recipients.

Send SMS instantly

SMS to On-Call Engineers in Seconds

Each ServiceNow notification email becomes an SMS within seconds of leaving the platform. Critical events (P1 incident assignment, Major Incident promotion, SLA Definition breach, CAB emergency approval) reach the on-call engineer immediately, before the SLA clock runs out or the bridge call starts without them.

10DLC compliant

10DLC-Compliant Business Number

TextBolt registers your sender identity with The Campaign Registry during onboarding. SMS routes through carrier-approved 10DLC infrastructure with up to 98% delivery rate, a professional toll-free business number, and an exportable audit trail for SOX, ITGC, and federal-contractor cloud-engineering teams running ServiceNow.

Two-way replies

Replies Thread Back to the Admin Inbox

When an on-call engineer replies “ack,” “investigating,” or “rerouting to Sam” by SMS, the reply lands as an email in the inbox of the alert sender, threaded under the original notification subject. The whole rotation sees acknowledgments without paying for Notify’s SMS-to-acknowledge flow or a separate IRM seat.

Gateway

Add the Gateway Address to the Notification’s Who Will Receive Tab

In any ServiceNow Incident, Change Request, Problem, or Major Incident notification record, add +1[phone]@sendemailtotext.com to the Who Will Receive tab. ServiceNow’s standard email channel routes the notification to TextBolt’s gateway, which converts the email to SMS. Same notification record, same SMS Alternate body, same conditions and recipients. One-line addition.

Notifications

No Notify License, No Twilio Account, No Extra Fulfiller Seats

Skip the Notify subscription, the Twilio API credential rotation, the per-fulfiller ITSM Pro seat for SMS-only recipients, and the one-to-two-week Business Rule build that platform owners running ServiceNow otherwise have to absorb. TextBolt is one flat monthly fee covering up to 10 team members.

No code required

Works Across Change, Major Incident, and SLA Notifications

The notification-recipient pattern is consistent across ServiceNow notifications, including Incident assignments, Major Incidents, Change Request approvals, CAB tasks, Problem assignments, SLA alerts, Request Item approvals, and any email-enabled sys_notification record. One TextBolt account covers your entire ServiceNow environment with no per-module configuration.

Performance Metrics

Up to 98%

SMS Delivery Rate

Two-Way-f9cf1b

Two-Way

SMS Replies to Your Inbox

Carrier-Grade-1f829c

Carrier-Grade

Routes & Infrastructure

Up to 10-604a83

Up to 10

Team Members on Shared Account

How Do You Set Up SMS Email Notifications in
ServiceNow?

Hands-on setup of ServiceNow email-to-SMS integration with TextBolt takes around 30 minutes. TextBolt handles 10DLC business verification with The Campaign Registry on your behalf in parallel. No Notify license to procure, no Twilio account to wire, no per-fulfiller seat to provision.

Sign Up for TextBolt

Create your TextBolt account using your work email. Account creation takes about 2 minutes. The account ties to your domain so you can add coworkers later.

Choose a Toll-Free Business Number

Pick a dedicated toll-free number for outbound SMS. The number is the sender ID on every SMS ServiceNow sends through TextBolt.

TextBolt Handles 10DLC Business Verification

Provide your business details during TextBolt onboarding. TextBolt handles 10DLC business and campaign registration with The Campaign Registry on your behalf, so you don’t manage the registration process yourself. Once approved, your number is enabled for compliant business SMS.

Add the Gateway Address to Your ServiceNow Notification Recipients

Open the notification record you want SMS for (System Notification → Email → Notifications → Incident, Major Incident, Change Request, or SLA). On the Who Will Receive tab, add +15551234567@sendemailtotext.com using the on-call engineer’s actual phone. Save the record. ServiceNow’s email channel routes the notification through to TextBolt automatically.

Trigger a Test Incident

Create a test P1 incident in a sub-prod instance with the on-call engineer as the assignee, or use the notification record’s Preview button. The SMS should land within seconds. Check the TextBolt delivery log to confirm.

Add Up to 10 Team Members

Invite the rest of your on-call rotation, NOC, CAB, and platform-owner group to the shared TextBolt account. Tag each engineer’s TextBolt-bound recipient address in notification records, or rotate the address through the on-call user’s Notification Preferences using the On-Call Scheduling module to route alerts to the active shift.

How Do You Set Up SMS Email Notifications in ServiceNow

Send Your First ServiceNow On-Call Alerts Directly From Email

Add a gateway address to any notification record and the alert becomes SMS. No Notify plugin, no Twilio account, no developer

What Options Does ServiceNow Offer for SMS
Notifications?

ServiceNow provides multiple options for sending SMS notifications, ranging from official plugins like Notify to integration alternatives like email-to-SMS gateways and custom REST integrations. With TextBolt as the email-to-SMS layer, three setup patterns cover most ServiceNow alerting workflows pick the one that fits your admin permissions and on-call rotation.

1. Add the Gateway Address to a Notification Record (Most Common)

Open the Incident, Major Incident, Change Request, or SLA notification record and add +1[phone]@sendemailtotext.com to the Who Will Receive tab. ServiceNow’s standard email channel routes the notification through to TextBolt and the alert becomes an SMS. Clean for instance-wide notifications where every relevant notification goes to the same on-call number.

2. Notification Preferences on the On-Call User’s sys_user Record

Paste the TextBolt gateway address into the on-call engineer’s Notification Preferences on their sys_user record. Pair with the On-Call Scheduling module so the SMS routes to whoever is on shift right now. Different engineers get different SMS based on rotation, region, or assignment group, all without editing the notification record itself.

3. Outlook or Gmail Forwarding Rule on the On-Call Inbox

Leave ServiceNow alone entirely. Set an Outlook or Gmail rule on the on-call inbox that catches messages from your ServiceNow instance domain and forwards them to the TextBolt gateway address. Useful when an admin doesn’t have permission to edit notification records or when MSPs need per-customer routing without touching domain-separated instances.

What Are ServiceNow Notification Types That Use
TextBolt SMS?

Six common ServiceNow notification categories where SMS to the on-call engineer replaces a Notify subscription, a paid PagerDuty seat, or a dead carrier gateway. The same gateway address works across every ServiceNow module. TextBolt is built for operational alerts to opted-in fulfillers and on-call rotation members, not for cold customer outreach or marketing campaigns.

Incident Management (P1/P2 Assignment)

On-call engineers and NOC analysts running ITSM get SMS for P1 and P2 incident assignments, priority escalations, and reassignments. The same Who Will Receive recipient works on default Incident notifications, custom severity-scoped notifications, and Service Operations Workspace alerts.

Major Incident Management

Major Incident Managers and incident commanders get SMS the moment an incident is promoted to Major. The Major Incident notification fires through the same email channel the rest of the rotation already uses, and the SMS carries the major incident number and short description so the commander joins the bridge call already knowing what’s burning.

Change Management (CAB Approvals)

CAB approvers and change managers get SMS for emergency change requests, expedited approvals, and CAB Workbench tasks. The notification still lands in the standard email inbox for the audit record, and the SMS adds the after-hours phone reach so emergency changes don’t stall waiting on Slack DMs.

SLA Definition Warnings and Breaches

Incident Managers and SLA owners get SMS for SLA Definition warning thresholds (50%, 75%, 90% consumed) and breach events. Route both warning and breach to the same TextBolt number so the manager sees the at-risk ticket before it breaches and the post-breach follow-up immediately after.

Problem Management Records

Problem Coordinators get SMS when a new Problem record is opened by a major-incident root-cause workflow, when a known error is reassigned, or when a Problem reaches a workflow milestone. Coordinators stay out of the Problem inbox view while the record stays in ServiceNow as the audit source.

IT Operations Management Event Correlation

ITOM Visibility, Event Management, and AIOps users get SMS for correlated event clusters, anomaly-detected alerts, and CMDB-discovered state changes. The same gateway address pattern works on ITOM-emitted notifications as on ITSM-emitted ones.

IT-and-DevOps-Teams

Built for Compliance and Security

10DLC Compliant

Carrier Approved

Complete Audit Trail

Which is the Best Way to Send SMS from ServiceNow?

Three common paths for adding SMS to ServiceNow. Notify + Twilio requires a plugin license and developer time. Carrier gateways are deprecated. TextBolt slots into the notification recipients ServiceNow already supports.

Carrier Email-to-SMS Gateways

Free historic path, now ending

ServiceNow’s lightweight workaround: create an SMS Service Provider record at cmn_notif_service_provider.list and point notifications at @[phone]@vtext.com or @[phone]@txt.att.net. AT&T retired txt.att.net in June 2025. T-Mobile took tmomail.net offline in December 2024. Verizon’s vtext.com shutdown completes by March 31, 2027.

  • XAT&T and T-Mobile gateways already shut down
  • X Verizon shutdown completes March 2027
  • X No 10DLC compliance, no audit trail
  • X Need to know recipient’s carrier
  • X Replies dropped or routed to dead addresses

TextBolt

Flat monthly plan, no per-message billing

Add +1[phone]@sendemailtotext.com to your ServiceNow notifications’s Who Will Receive tab. Standard email channel, standard SMS Alternate body, standard recipient conditions. Now compliant, audit-trail, two-way.

  • Checkmark Up to 98% delivery rate
  • Checkmark 10DLC-compliant business number
  • Checkmark No Notify license, no Twilio account, no Fulfiller seats for recipients
  • Checkmark Multi-user access: up to 10 team members
  • Checkmark Replies in admin’s inbox
  • Checkmark Works across Incident, Change, Problem, Major Incident, SLA, and ITOM notifications

Notify + Twilio Plugin

Plugin license plus developer time

ServiceNow’s documented first-party SMS path. Activate the Notify plugin, configure a Twilio (or Plivo, eCall) account inside the Notify application module, and call sn_notify.sendSMS() from a Business Rule or Flow Designer action. Powerful for two-way customer SMS and voice escalations, but adds plugin licensing, Twilio account procurement, and a one-to-two-week developer build.

  • X Notify plugin license required
  • X Twilio API credentials and Auth Token rotation
  • X One-to-two-week developer build
  • X Per-user sys_user device records and notification preferences to maintain
  • X Re-validation at every Now Platform major release

CUSTOMER REVIEWS

How Teams Use TextBolt with ServiceNow

Three ways customers route SMS through ServiceNow with TextBolt: skipping the Notify subscription, replacing carrier-gateway setups, and reaching on-call without buying another IRM platform.

Frame 1686556011

On Google Workspace Marketplace, with

263K+ installs

We were paying for PagerDuty seats just to forward ServiceNow P1 incidents to phones. After adding a TextBolt gateway address to the Major Incident notification, we dropped PagerDuty entirely. P1 acknowledgment time fell from 14 minutes to under 4, and the audit log exported cleanly for our last ITGC review.

David Chen

ITSM Director

Healthcare IT

My platform team scoped a Notify plugin plus Twilio build for SMS on SLA warnings and Change Request approvals. The estimate was almost two weeks of developer time. TextBolt took 30 minutes. We added one gateway per on-call rotation, and ServiceNow’s existing email channel does the rest. No new licenses or JavaScript.

Marcus Webb

Platform Owner

FinTech SaaS

Major incident updates used to get delayed because key stakeholders didn’t see their ServiceNow email notifications after hours. We routed those notifications through TextBolt, and everyone now receives an SMS the moment an update is sent. Incident response became much faster, and critical decisions no longer wait until the next morning.

Theresa Olsen

IT Operations Director

Enterprise Software Company

Why ServiceNow Teams Pick TextBolt

The numbers that matter when wiring SMS into a ServiceNow notification stack.

Up to 98%

SMS Delivery Rate

30 min

End-to-End Setup

Up to 10

Team Members on Standard Plan

4.4★

Workspace Marketplace (483+ reviews)

Frequently Asked Questions

Does ServiceNow have native SMS support?

No. ServiceNow’s default notification channels are email, mobile push (Now Mobile), in-platform banner, and desktop browser. SMS is not in the default channel list. To send SMS, you need the separately-licensed Notify plugin (with a Twilio, Plivo, or eCall account behind it), the deprecated carrier email-to-SMS gateway workaround, or an email-to-SMS gateway like TextBolt that rides on ServiceNow’s existing email notifications. TextBolt is the no-plugin path: add the gateway address to a notification record’s Who Will Receive tab and the email becomes an SMS.

How to send SMS from ServiceNow without Notify or Twilio?

Sign up for TextBolt, complete 10DLC business verification, and add +1[phone]@sendemailtotext.com to your ServiceNow notification record’s Who Will Receive tab. Save the notification. Trigger a test incident. The SMS lands in seconds. No Notify plugin license to procure, no Twilio API credentials to manage, no Business Rule scripting. ServiceNow’s standard email channel routes the notification through to TextBolt, which converts it to SMS and delivers via a 10DLC-registered business number.

Why are my ServiceNow text alerts not sending?

Common issues include incorrect notification conditions, missing or improperly formatted phone numbers, inactive Notify/SMS configurations, or deprecated carrier email-to-SMS gateways. Check System Notification logs and outbound email queues. With TextBolt, the Delivery Issues dashboard helps identify failure reasons quickly.

What’s the difference between ServiceNow Notify and an email-to-SMS gateway?

Notify is ServiceNow’s first-party telephony plugin. It requires a separate plugin license, a Twilio (or Plivo, eCall) account on the customer’s side, credentials configured inside the Notify application module, and a developer to call sn_notify.sendSMS() from a Business Rule or Flow Designer action. 

Notify supports two-way customer SMS and voice escalations. An email-to-SMS gateway like TextBolt rides on ServiceNow’s existing email notifications. You add a gateway address to the notification record’s Who Will Receive tab and the email becomes an SMS. No plugin, no developer, no Twilio account.

How do I set up SMS for high-priority incidents only?

Two patterns. (1) Edit the Incident notification record’s Conditions tab to filter for priority is 1 – Critical OR priority is 2 – High, so the notification only fires for P1 or P2. Add the TextBolt gateway address to Who Will Receive and only prioritized incidents trigger SMS. (2) Clone the default Incident assignment notification, scope the clone to P1/P2 only, and route the clone’s recipients to TextBolt while the original notification keeps going to email for lower priorities. Pattern 2 is cleaner when other notifications share the original Incident notification record.

Where to add the SMS gateway address in ServiceNow?

Open System Notification → Email → Notifications. Pick the notification record you want SMS for (Incident, Major Incident, Change Request, SLA Definition, Problem, or any sys_notification record with the Email channel enabled). On the Who Will Receive tab, add your gateway address (for TextBolt: +1[phone]@sendemailtotext.com) as a recipient. Save the record. For per-user routing, paste the gateway address into the on-call fulfiller’s Notification Preferences on their sys_user record instead.

How to broadcast SMS alerts to a ServiceNow on-call team?

Use multiple gateway addresses in the notification, assign a user group with configured SMS preferences, or integrate with on-call scheduling so alerts dynamically route to the active engineer.

Can engineers reply to ServiceNow SMS alerts?

Yes. Replies sent via TextBolt are delivered back as email threads to the original sender. However, they do not automatically update ServiceNow records unless additional integration is configured through Notify or custom workflows.

How long does it take to set up SMS in ServiceNow?

TextBolt setup takes around 30 minutes for configuration, with 10DLC verification completing in 1–2 business days. Notify-based setups typically require longer implementation due to plugin setup, scripting, and external provider configuration.

Reach On-Call Engineers Without a Notify Subscription

Send SMS from any ServiceNow notification in about 30 minutes with TextBolt. Add the gateway address to the Who Will Receive tab and your existing notification records, SMS Alternate bodies, and recipient conditions keep working, now compliant and two-way.