Send Text/SMS Alerts Directly from New Relic
Turn any New Relic Workflow into an instant text/SMS to the on-call engineer, using the email destination you already configure.
-
Add an email destination and New Relic alerts become text
-
Works with your 10DLC business number
-
Replies thread back to the admin’s inbox
Adding Compliant Text on Top of New Relic Workflows
New Relic Workflows route alerts reliably across the modern observability stack. TextBolt complements them by adding 10DLC-compliant SMS through the email destination you already configure. Six common scenarios where SREs, application engineers, DevOps engineers, and engineering team leads reach for SMS alongside New Relic.
SREs Want SMS for Critical-Tier New Relic Alerts
New Relic Workflows ships with a strong destination set: Atlassian Jira, ServiceNow, Slack, Webhook, Email, AWS EventBridge, New Relic Mobile Push, and Microsoft Teams. SMS is the one channel that lives outside that built-in set, and SREs and application engineers configuring critical-tier alerts add a third-party path for it. TextBolt slots into the standard Email destination you already configure, so SMS becomes one more destination variant on top of your existing Workflow setup.
Carrier Email-to-SMS Gateways Have Shut Down
The lightweight workaround was creating an email destination with [phone]@vtext.com, @txt.att.net, or @tmomail.net as the recipient. 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. Teams that relied on this path need a new SMS route for their New Relic alerts, with published migration guides covering the AT&T email-to-text shutdown, the T-Mobile email-to-text shutdown, and the Verizon vtext.com shutdown.
The TIA Webhook Path Is a Powerful Programmable Option
Twilio Integrated Alerts (TIA, the community-standard gspncr/twilio-integrated-alerts webhook receiver) is a fully programmable path for routing New Relic alert payloads through Twilio’s Programmable Messaging API. It’s the right fit when full payload customization and infinite branching logic are the requirement. For engineering teams looking for a no-script, single-tool path to SMS, TextBolt removes the serverless deployment layer while keeping the same Workflow flow.
PagerDuty and OpsGenie Are Full Incident-Response Platforms
PagerDuty and OpsGenie are excellent full-stack incident response platforms, with native New Relic Workflows integrations, on-call schedules, escalation policies, post-mortems, and SMS bundled inside. They are the right fit when teams need the full IRM workflow. For engineering teams that just need the SMS-to-on-call hop without the IRM platform layer, TextBolt covers that lighter-weight path through the standard Email destination.
Engineering Teams Want SMS That Outlasts Tooling Migrations
Observability and incident-response tooling evolves continuously: products consolidate, platforms migrate, schemas change. SREs and engineering team leads running New Relic appreciate having an SMS layer that’s decoupled from those broader migrations, so an unchanged email destination keeps working through any platform-level evolution. TextBolt is that decoupled SMS layer: a managed gateway that doesn’t change when other tools in the stack do.
SMS in Regulated Industries Needs an Audit Trail
SREs and engineering teams running New Relic in regulated industries (financial services, federal-contractor cloud-engineering, insurance, healthcare-adjacent SaaS) need exportable audit trails on every SMS sent on behalf of the business. Personal-phone workarounds and ad-hoc alerting tools rarely produce the timestamped delivery logs compliance teams expect. TextBolt registers your sender identity with The Campaign Registry and produces a complete audit trail per message, ready for compliance review.
How TextBolt Adds SMS to New Relic Workflows
TextBolt connects New Relic Workflows to a registered 10DLC business number through the standard Email destination you already configure. Purpose-built for the SMS-to-on-call hop, complementing TIA, IRM platforms, and the rest of your incident-response stack.
SMS to SREs and Application Engineers in Seconds
Each New Relic alert becomes an SMS within seconds. Critical incidents (APM error rate spikes, p99 latency regressions, host down, log anomalies, synthetic test failures) reach the on-call SRE, application engineer, or DevOps engineer immediately, before user-facing impact compounds.
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 federal-contractor and regulated New Relic deployments.
Configure an Email Destination With the Gateway Address
In New Relic Workflows, create a new destination with type “Email” and address +1[phone]@sendemailtotext.com. Wire the destination into a Workflow with filter conditions (priority, entity, label). The standard email channel routes the alert to TextBolt, which converts it to SMS.
Flat Pricing Built for the SMS-to-On-Call Hop
TextBolt is one flat monthly fee covering up to 10 team members. Standard plan ($49/month) and Professional plan ($99/month) both include multi-user access for up to 10 engineers. Predictable monthly billing with no per-task fees, no per-message charges, and no per-user pricing on top of your New Relic compute.
Replies Thread Back to the Admin Inbox
When an SRE or application engineer replies “ack,” “rerouting,” or “investigating” by SMS, the reply lands as an email in the inbox of the alert sender. The whole rotation sees acknowledgments without paying for a PagerDuty seat just for the SMS-to-ack flow.
Works Across APM, Infrastructure, Browser, Synthetics, Logs, and Mobile
The email destination pattern is consistent across every New Relic product: APM monitors, Infrastructure monitors, Browser/RUM, Synthetics, Log query alerts, Mobile (iOS and Android) crash alerts, and SLO burn-rate signals. One TextBolt account covers your entire New Relic footprint with no per-product configuration.
Performance Metrics
Up to 98%
SMS Delivery Rate
Two-Way
SMS Replies to Your Inbox
Carrier-Grade
Routes & Infrastructure
Up to 10
Team Members on Shared Account
Set Up New Relic SMS in About 30 Minutes
Hands-on setup takes around 30 minutes. TextBolt handles 10DLC business verification with The Campaign Registry on your behalf in parallel. No serverless function to deploy, no TIA script to maintain, no PagerDuty seat to provision.
01 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.
02 Choose a Toll-Free Business Number
Pick a dedicated toll-free number for outbound SMS. One-time $45/year setup fee. The number is the sender ID on every SMS New Relic sends through TextBolt.
03 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.
04 Create an Email Destination in New Relic Workflows
In New Relic, go to Alerts → Destinations and create a new Email destination. Set the recipient to +15551234567@sendemailtotext.com using the engineer’s actual phone. Save the destination.
05 Wire the Destination Into a Workflow
Create or edit a Workflow. Add filter conditions (priority, entity tags, account labels). Attach the TextBolt-bound email destination. Trigger a test alert via Workflow’s test button or by lowering a threshold temporarily.
06 Add Up to 10 Team Members
Invite the rest of your SRE and DevOps rotation to the shared TextBolt account. Add per-engineer email destinations in New Relic. Use Workflow filter conditions to route alerts to the right rotation member based on tags or priority.
Three Ways to Send SMS from New Relic
1. Single Email Destination in Workflows (Most Common)
Create one Email destination addressed at +1[phone]@sendemailtotext.com. Wire it into a Workflow with priority=critical or severity=high filters. Every matching alert becomes an SMS from your business number. Clean for solo on-call rotations.
2. Per-Team Destinations With Filter Conditions
Create one TextBolt-bound email destination per on-call rotation member or per team. Use Workflow filters on entity tags, account labels, and priority to route APM alerts to one engineer, Infrastructure alerts to another, Synthetics failures to a third. Each engineer gets only the SMS that matches their team.
3. Migrating From TIA, PagerDuty, or OpsGenie
Replace the existing TIA serverless deployment, PagerDuty integration, or OpsGenie integration with a TextBolt-bound email destination. Same Workflow filters, same alert flow, same engineers. Decommission the Lambda function, cancel the IRM seat, or skip the OpsGenie-to-Jira migration entirely.
New Relic Product Areas That Use TextBolt SMS
Six common New Relic product areas where SMS to the on-call engineer replaces a TIA serverless deployment, a PagerDuty seat, or a dead carrier gateway. The same email destination works across every New Relic product.
APM and Trace Tracing
Application engineers running New Relic APM get SMS for trace error spikes, p99 latency regressions, Apdex score drops, and downstream dependency failures. The same email destination works on APM monitors, NRQL alert conditions, and Service Levels.
Infrastructure Monitoring
SREs and DevOps engineers running New Relic Infrastructure get SMS for host-down events, CPU/memory/disk threshold breaches, container restarts, and Kubernetes pod failures. Standard email destination wired into any infrastructure metric alert condition.
Browser and Real User Monitoring
Application engineers and frontend engineers running New Relic Browser get SMS for session error spikes, JavaScript exceptions, page-load regressions, and core-web-vitals breaches. Critical user-facing performance issues reach engineers immediately.
Synthetic Monitoring
SREs running New Relic Synthetics get SMS when API tests fail, browser tests detect regressions, or scripted browser tests find broken user journeys. Critical synthetic failures route through the same email destination.
Log Management Alerts
Application engineers and DevOps engineers get SMS for log query alerts: error rate spikes, security event patterns, ERROR-log volume thresholds, and pattern-detection anomalies. New Relic log monitors route through the same email-destination mechanism.
Mobile Monitoring (iOS and Android)
Application engineers and mobile engineers running New Relic Mobile get SMS for crash rate spikes, ANR (Application Not Responding) events, and HTTP error rate breaches across iOS and Android apps. Critical mobile incidents reach the team without IRM-seat overhead.
Built for Compliance and Security
10DLC Compliant
Carrier Approved
Complete Audit Trail
Three SMS Paths for New Relic
Three different SMS paths for New Relic, three different mental models. TIA is a fully programmable serverless approach for custom payload routing. PagerDuty and OpsGenie are full incident-response platforms with SMS bundled in. TextBolt is a managed cloud gateway for the SMS-to-on-call hop. Pick the one that matches the job to be done.
Webhook + Twilio Integrated Alerts (TIA)
For custom payload routing
The community-standard gspncr/twilio-integrated-alerts webhook receiver running on Lambda or Cloud Functions, paired with Twilio’s Programmable Messaging API. The right fit when full payload customization, infinite branching logic, and per-alert programmability are the requirement.
-
Powerful, fully programmable path
-
Serverless infrastructure for full control
-
Twilio’s leading SMS API
-
Custom payload mapping per New Relic schema
-
Best when custom logic is the requirement
Recommended
$49/month (Standard plan)
Managed cloud email-to-SMS gateway purpose-built for the SMS-to-on-call hop. Create an Email destination in Workflows addressed at +1[phone]@sendemailtotext.com. Standard New Relic email channel, standard Workflow filters. Compliant, audit-trailed, two-way.
-
Up to 98% delivery rate
-
10DLC-compliant business number
-
Multi-user access for up to 10 team members
-
Replies thread back to the admin’s inbox
-
Slots into the Email destination you already use
-
Works across APM, Infra, Browser, Synthetics, Logs, and Mobile
PagerDuty / OpsGenie / VictorOps
For full incident response
Full-stack incident response platforms with native New Relic Workflows integrations, on-call schedules, escalation policies, post-mortems, and SMS bundled inside. The right fit when teams need the full IRM workflow, not just the SMS hop.
-
Native New Relic Workflows integrations
-
On-call schedules and escalation policies
-
Post-mortems and incident timelines
-
SMS bundled inside the platform
-
Best when full IRM is the requirement
How Teams Use TextBolt with New Relic
Three ways customers route SMS through New Relic with TextBolt: triggering Workflow alerts to the assigned on-call engineer, audit-ready SMS for regulated cloud-engineering teams, and a decoupled SMS layer that survives broader tooling migrations.
Why New Relic Teams Pick TextBolt
The numbers that matter when wiring SMS into a New Relic Workflows stack.
Up to 98%
SMS Delivery Rate
30 min
End-to-End Setup
$49/mo
Standard Plan, 10 Users
4.4★
Workspace Marketplace (493 reviews)
Frequently Asked Questions
Does New Relic have native SMS support?
No. New Relic Workflows ships with Atlassian Jira, ServiceNow, Slack, Webhook, Email, AWS EventBridge, New Relic Mobile Push, and Microsoft Teams as built-in destinations. SMS is not in the list. To send SMS from New Relic, you either point an Email destination at a third-party email-to-SMS gateway (TextBolt), build a webhook integration with Twilio Integrated Alerts (TIA), or pay for an IRM platform like PagerDuty or OpsGenie.
What replaced the email-destination carrier gateway path for New Relic?
After AT&T retired txt.att.net in June 2025, T-Mobile took tmomail.net offline in December 2024, and Verizon’s vtext.com shutdown completes by March 2027, New Relic shops have three options: replace the carrier gateway address with TextBolt’s gateway in the Email destination (closest one-line replacement), deploy the Twilio Integrated Alerts (TIA) serverless function, or pay for PagerDuty/OpsGenie. TextBolt preserves the email-destination mental model unchanged.
How do I send SMS from New Relic without TIA or webhook code?
Sign up for TextBolt, complete 10DLC business verification, and create an Email destination in New Relic Workflows with the recipient set to +1[phone]@sendemailtotext.com. Wire the destination into a Workflow with priority filters. Trigger a test alert. The SMS lands in seconds. No serverless function to deploy, no Twilio credentials to manage, no payload schema to maintain.
Can I use my existing New Relic email destination for SMS?
Yes. The integration uses New Relic Workflows’ standard Email destination type. Replace the dead carrier gateway recipient ([phone]@vtext.com) with +1[phone]@sendemailtotext.com. Existing Workflow filters, priority conditions, entity tags, and account label routing all work unchanged.
How is this different from PagerDuty or OpsGenie for New Relic SMS?
PagerDuty and OpsGenie are excellent full-stack incident response platforms with native New Relic Workflows integrations, on-call schedules, escalation policies, post-mortems, and SMS bundled inside the platform. They are the right fit when teams need the full IRM workflow. TextBolt covers a different job: just the SMS-to-on-call hop, through the standard Email destination, with replies threading back to the admin’s inbox. $49/month flat for up to 10 team members. The two tool categories complement each other depending on what the team actually needs.
Is New Relic SMS via TextBolt 10DLC compliant?
Yes. TextBolt registers your sender identity with The Campaign Registry during onboarding so SMS routes through carrier-approved 10DLC infrastructure. This satisfies FCC business SMS requirements and produces the audit trail federal-contractor and regulated cloud-engineering teams need. TextBolt is not HIPAA compliant; healthcare-adjacent monitoring with PHI requirements should contact sales for Enterprise options.
Can engineers reply to acknowledge New Relic alerts via SMS?
Yes. Replies to a TextBolt-sent SMS land as an email in the inbox of whoever sent the original alert. The whole rotation sees acknowledgments without paying for a PagerDuty seat. Note: TextBolt replies don’t automatically resolve the New Relic incident (the New Relic UI or NerdGraph API is required for that). For SMS-to-resolve automation, route the reply through New Relic’s incident-management tooling.
Does this work with New Relic APM, Infrastructure, Browser, Synthetics, Logs, and Mobile?
Yes. The Email destination mechanism is consistent across every New Relic product: APM, Infrastructure, Browser/RUM, Synthetics, Logs, Mobile (iOS/Android), and Service Levels. NRQL alert conditions, anomaly detection, and SLO burn-rate alerts all route through Workflows destinations. One TextBolt account covers your entire New Relic footprint.
How much does it cost to send SMS from New Relic with TextBolt?
Basic $29/month (500 credits, single user), Standard $49/month (1,000 credits, multi-user access up to 10 team members), Professional $99/month (2,500 credits, multi-user access up to 10 team members), Enterprise custom (5,000+ credits). One-time $45/year setup fee for the toll-free business number. Annual plans 20% off. TextBolt is purpose-built for the SMS-to-on-call hop; TIA, PagerDuty, OpsGenie, and other IRM platforms each cover different SMS jobs and tend to be picked alongside, not instead of, TextBolt depending on whether the team needs the full IRM workflow.
How long does it take to set up New Relic-to-SMS with TextBolt?
About 30 minutes of hands-on configuration: account creation, toll-free number selection, and creating the Email destination in New Relic Workflows wired into a Workflow. TextBolt handles 10DLC business verification with The Campaign Registry on your behalf in parallel; once the carriers approve your number, your team can start sending SMS.
Reach SREs and Application Engineers the Moment Critical Alerts Fire
Send SMS from any New Relic alert in about 30 minutes. Configure an Email destination in Workflows and your existing filters and routing keep working, now compliant and two-way.