New Relic alerting already routes alerts across your observability stack via Workflows. TextBolt adds 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.
New Relic Workflows ships with a strong destination set, but SMS lives outside it. SREs and application engineers configuring critical-tier alerts add a third-party path, and TextBolt slots into the standard Email destination you already configure.
The lightweight workaround was an email destination at a carrier address. AT&T retired txt.att.net in June 2025, T-Mobile took tmomail.net offline in December 2024, and Verizon’s vtext.com shutdown by March 31, 2027. Teams on this path need a new route.
Twilio Integrated Alerts (TIA) routes New Relic payloads through Twilio’s Programmable Messaging API, built for teams that need full payload customization and branching logic. For a no-script, single-tool path, TextBolt removes the serverless deployment layer while keeping the same Workflow.
PagerDuty and OpsGenie are excellent full-stack incident response platforms, with on-call schedules, escalation policies, post-mortems, and SMS bundled inside. PagerDuty connects as a native New Relic destination; OpsGenie connects through a webhook template. Either fits when teams need the full IRM workflow.
Observability and incident-response tooling evolves continuously: products consolidate, platforms migrate. TextBolt is a decoupled SMS layer sitting in a plain email destination, so an unchanged setup keeps working through platform-level changes elsewhere.
Teams running New Relic in regulated industries need exportable audit trails on every SMS sent. TextBolt registers your sender identity with The Campaign Registry and produces a complete, timestamped audit trail per message.
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.
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 engineer immediately, before user-facing impact compounds.
TextBolt registers your sender identity with The Campaign Registry during onboarding. SMS routes through carrier-approved 10DLC infrastructure with up to 98% delivery rate and an exportable audit trail for federal-contractor and regulated New Relic deployments.
New Relic can send an email alert to any destination you configure, so pointing it at your TextBolt gateway is a one-line change. Wire the destination into a Workflow with filter conditions (priority, entity, label), and the alert converts to SMS automatically.
TextBolt is one flat monthly fee covering up to 10 team members. Standard and Professional plans both include multi-user access. Predictable monthly billing with no per-task fees, no per-message charges, and no per-user pricing.
When an SRE or application engineer replies “ack,” “rerouting,” or “investigating,” the reply lands as an email in the admin’s inbox, the person who configured the destination. The rotation can review acknowledgments there without paying for a PagerDuty seat just for the SMS-to-ack flow.
The email destination pattern is consistent across every New Relic product: APM monitors, Infrastructure monitors, Browser and RUM, Synthetics, Log query alerts, and Mobile (iOS and Android) crash alerts. One TextBolt account covers your entire New Relic footprint.
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
Hands-on setup takes around 30 minutes. TextBolt handles 10DLC business verification (up to 48 hours) with The Campaign Registry on your behalf, in parallel. No serverless function to deploy, no TIA script to maintain, no PagerDuty seat to provision.
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.
Pick a dedicated toll-free number for outbound SMS. The number is the sender ID on every SMS New Relic sends through TextBolt.
Provide your business details during onboarding. TextBolt handles registration with The Campaign Registry on your behalf, and your number is enabled once carriers approve it.
Go to Alerts, Destinations, and create a new Email destination. Set the recipient to your TextBolt gateway address, using the engineer’s actual phone.
Create or edit a Workflow, add filter conditions (priority, entity tags, account labels), and attach the TextBolt-bound Email destination. Trigger a test alert to confirm it arrives.
Invite the rest of your SRE and DevOps rotation to the shared TextBolt account. Add per-engineer email destinations in New Relic, and use Workflow filters to route alerts to the right rotation member.

Get Your On-Call Rotation Wired Up Today
Sign up, verify your business number, and connect your first Workflow. No app. No training. No new number.
Once TextBolt is wired into a Workflow, teams route SMS one of three ways depending on rotation size and how much filtering they need.
Create one Email destination addressed at your TextBolt gateway. Wire it into a Workflow with priority-equals-critical or severity-equals-high filters. Every matching alert becomes an SMS from your business number. Clean for solo on-call rotations.
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.
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, without maintaining the Lambda function or paying for the extra seat.
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.
Application engineers running New Relic APM get SMS for trace error spikes, p99 latency regressions, Apdex score drops, and downstream dependency failures. Works on APM monitors, NRQL alert conditions, and Service Levels.
SREs and DevOps engineers get SMS for host-down events, CPU, memory, and disk threshold breaches, container restarts, and Kubernetes pod failures.
Application and frontend engineers get SMS for session error spikes, JavaScript exceptions, page-load regressions, and core web vitals breaches.
SREs get SMS when API tests fail, browser tests detect regressions, or scripted checks find a broken user journey.
Application and DevOps engineers get SMS for log query alerts: error rate spikes, security event patterns, and pattern-detection anomalies.
Mobile engineers get SMS for crash rate spikes, application-not-responding events, and HTTP error rate breaches across iOS and Android.

10DLC Compliant
Carrier Approved
Complete Audit Trail
Three different SMS paths for New Relic. TIA is programmable and serverless. PagerDuty and OpsGenie bundle SMS into a full incident-response platform. TextBolt is an email-to-SMS gateway for the SMS-to-on-call hop. Pick the one that fits.
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. It is right for teams that need full payload customization and per-alert programmability.
Recommended
Flat monthly plan, no per-node license (Standard plan)
A managed cloud email-to-SMS gateway purpose-built for the SMS-to-on-call hop. Create an Email destination addressed at your TextBolt gateway. Standard New Relic email channel, standard Workflow filters. Compliant, audit-trailed, two-way.
For full incident response
Full-stack incident response platforms with 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.
CUSTOMER REVIEWS
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.

On Google Workspace Marketplace, with
263K+ installs
We use New Relic Workflows for our entire on-call rotation. We just needed our SREs to get SMS the moment a critical alert fired. TextBolt slots straight into the Email destination we already had set up. Took maybe 20 minutes to wire up.

SRE Lead
Payments Platform
Our team needed SMS for a small set of critical-tier New Relic alerts. We didn’t need a full IRM workflow yet. TextBolt covered the SMS-to-on-call hop with one Email destination wired into our Workflow. The audit trail satisfied our compliance review the next quarter.

Engineering Manager
Healthcare SaaS
We wanted our SMS layer to be decoupled from the rest of our incident-response tooling, so platform migrations elsewhere don’t break the SMS-to-on-call hop. TextBolt sits in the standard Email destination and keeps working through whatever else changes upstream. Set it once and stop worrying about it.

DevOps Engineer
Logistics Tech
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
Up to 10
Team Members (Standard Plan)
4.4★
Workspace Marketplace (483+ reviews)
No. New Relic Workflows ships with Jira, ServiceNow, Slack, Webhook, Email, AWS EventBridge, PagerDuty, and New Relic Mobile Push (in-app push to the logged-in user, not SMS to a third party) as destinations. SMS via TextBolt covers a phone not tied to a New Relic seat.
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: TextBolt’s gateway, a TIA serverless function, or PagerDuty/OpsGenie.
Sign up for TextBolt, complete 10DLC business verification, then create an Email destination in New Relic Workflows with your TextBolt gateway address as the recipient. Wire it into a Workflow with priority filters and tests.
Yes. Replace the dead carrier gateway recipient with your TextBolt gateway address, and existing Workflow filters, priority conditions, entity tags, and label routing all continue to work unchanged.
PagerDuty and OpsGenie are full incident response platforms with on-call schedules, escalation policies, and post-mortems, with SMS bundled inside. PagerDuty is a native New Relic destination; OpsGenie connects via a webhook template. TextBolt covers just the SMS-to-on-call hop.
Yes. TextBolt registers your sender identity with The Campaign Registry so SMS routes through carrier-approved 10DLC infrastructure with an audit trail. For messaging with HIPAA considerations, we recommend consulting your compliance team to confirm TextBolt fits your requirements.
Yes. Replies to a TextBolt-sent SMS land as an email in the admin’s inbox, since New Relic’s alerts come from an automated system rather than a person. Replies don’t automatically resolve the New Relic incident; the New Relic UI or NerdGraph API is required for that.
Yes. The Email destination mechanism is consistent across every New Relic product: APM, Infrastructure, Browser and RUM, Synthetics, Logs, and Mobile. One TextBolt account covers your entire New Relic footprint.
Basic plans include 500 credits and a single user. Standard supports 1,000 credits with multi-user access for up to 10 team members, and Professional includes 2,500 credits with the same 10-member access.
About 30 minutes of hands-on configuration. TextBolt handles 10DLC business verification with The Campaign Registry in parallel, which can take up to 48 hours, and no messages can be sent until that approval clears.
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.