Sensu Go is an observability pipeline that turns check results into JSON events, filters noise, and sends alerts to tools like email, Slack, PagerDuty, Opsgenie, and InfluxDB. While it supports dozens of integrations, SMS isn’t one of them, leaving DevOps teams to find another way to receive text alerts for production outages.
Sensu ships handlers for chat, incident platforms, ticketing, and time-series databases, but nothing that puts a message on the cellular network by itself. Sensu’s own documentation covers email alerts and PagerDuty alerts, and SMS is left to whatever you bolt on. TextBolt uses the email handler Sensu already supports, so the pipeline stays exactly as your team built it.
The classic free trick was pointing the Sensu email handler at a carrier address like 5551234567@vtext.com, @txt.att.net, or @tmomail.net. That path is closing. AT&T and T-Mobile have already retired their gateways, and Verizon is shutting down vtext.com by March 31, 2027. A handler pointed at a dead gateway fails quietly, which is the worst possible failure mode for an alerting pipeline.
The usual alternative is a custom pipe handler that runs a Python or Bash script. That script has to parse the event JSON, build an authenticated HTTP request, handle timeouts and retries, and store an API token somewhere safe on the backend. Someone owns that script forever. When the API version changes or the token rotates, your alerting breaks and nobody notices until an incident is already in progress.
PagerDuty, Opsgenie, Zenduty, and GoAlert all integrate cleanly with Sensu, and they do far more than send texts. They also carry per-user licensing and a second platform to administer. If your team already has on-call coverage figured out and only needs the text itself to arrive, an entire incident management suite is a heavy way to buy one SMS.
A check running every 60 seconds against a host that stays down will fire an event every 60 seconds. Pointed straight at SMS, that is a hundred texts before anyone wakes up. Sensu solves this with filters, but the filters have to be in the handler definition before the first incident, not after. Teams that skip is_incident learn this the expensive way.
The sensu-email-handler emits a full event summary built for a mail client, including entity metadata, check history, and timestamps. That body is fine in an inbox and unreadable on a lock screen. Without a trimmed template, the important part of the alert gets buried under boilerplate.
TextBolt connects Sensu to a registered 10DLC business number through the same email handler your pipeline already uses. There is no plugin to compile, no pipe script to maintain, and no incident platform to license. You change the -toEmail value and Sensu events start arriving as texts.
Every event your handler passes becomes an SMS within seconds. A host going down, a disk crossing 95%, an unreachable database, or an expiring certificate reaches the on-call engineer’s phone immediately, well before the first user files a ticket.
TextBolt registers your business with The Campaign Registry during onboarding and sends messages over carrier-approved 10DLC infrastructure. You get a real business number and exportable message history for regulated industries like healthcare, finance, and government.
When an engineer replies “On it” or “Failing over now,” TextBolt delivers that reply as an email to the sending inbox. Everyone watching the alert mailbox sees the acknowledgement, which gives you lightweight two-way communication without deploying an incident platform for it.
Add the sensu-email-handler asset, set –toEmail to +15551234567@sendemailtotext.com, and apply the handler. TextBolt converts the message into an SMS. No mutator, no custom asset, and no change to your checks, subscriptions, or filters.
There is no Python file on the backend, no API credential in your handler definition, and no per-engineer subscription. Sensu is open source, and the SMS layer stays equally simple, covering your whole rotation on one account.
Because TextBolt sits at the end of the pipeline, everything upstream is untouched. is_incident, not_silenced, occurrence-based fatigue filters, subscriptions, and contact labels all behave the same. TextBolt only sees what your filters already decided was worth waking someone up for.
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
You can start sending Sensu Go alerts as text messages in minutes. TextBolt works with Sensu’s existing email notifications, so you don’t need to install new software or modify your monitoring pipeline. During setup, TextBolt also handles your 10DLC business registration, which typically takes 1–2 business days for carrier approval.
Sign up with your work email and create your TextBolt account. The setup only takes a few minutes.
Select a dedicated 10DLC or toll-free number. This becomes the number your team sees when Sensu sends SMS alerts.
Enter your business details during onboarding. TextBolt submits your 10DLC registration with The Campaign Registry so your messages are approved by mobile carriers.
If you’re already sending email notifications from Sensu, you can use the same email handler. Otherwise, install the official email handler:
sensuctl asset add sensu/sensu-email-handler
Configure the email handler to send alerts to your TextBolt gateway address (for example, +15551234567@sendemailtotext.com). TextBolt converts every email alert into an SMS message.
Trigger a test event and verify that the SMS reaches your phone. You can also confirm delivery from the TextBolt dashboard.

Turn Sensu Go Email Alerts Into SMS
Keep your existing Sensu pipeline, filters, and handlers. TextBolt converts email alerts into reliable business text messages your on-call engineers won’t miss.
You create a single email handler and point the –toEmail flag to a single TextBolt gateway address (e.g., +15551234567@sendemailtotext.com). You then attach this single handler directly to your critical checks.
You define multiple distinct handlers—one for each engineer or team—each configured with their specific TextBolt gateway address. You then use Sensu event filters and contact labels (such as contacts: dba or contacts: netops) to dynamically route the alert to the correct person’s handler.
Instead of routing alerts to volatile, free carrier addresses (like @vtext.com) or maintaining a custom Python/Bash script that hits an SMS API (like Twilio), you simply swap out the destination address or script action for your new gateway email address.
Sensu Go is used across many IT environments to monitor infrastructure, applications, and services. TextBolt extends those alerts to SMS, helping the right people respond faster without changing existing monitoring workflows.
Send critical Sensu Go alerts as text messages to on-call engineers when servers, containers, or applications fail. SMS ensures high-priority incidents are seen immediately, even when engineers are away from their desks.
Route infrastructure, network, and connectivity alerts from Sensu Go directly to on-call technicians. Text messages help reduce response times for outages and keep critical systems available around the clock.
Monitor multiple customer environments with Sensu Go and send SMS alerts to the assigned engineer based on the client, service, or severity. Teams can respond quickly without constantly watching email or monitoring dashboards.
Receive SMS notifications for failures across Kubernetes clusters, cloud VMs, databases, and other production services monitored by Sensu Go. Engineers can take action before small issues become customer-facing incidents.
Deliver production alerts to engineers responsible for service availability and reliability. TextBolt adds SMS to existing Sensu Go email notifications without introducing another alerting platform.
Send high-severity security and compliance alerts from Sensu Go to incident responders via SMS. Critical events reach the team immediately, improving response times for potential threats or infrastructure issues.

10DLC Compliant
Carrier Approved
Complete Audit Trail
There are three practical ways to get a text out of a Sensu pipeline. You can write a custom pipe handler against an SMS API, send through an email-to-SMS gateway like TextBolt, or connect Sensu to a full incident response platform. They differ mainly in what your team has to maintain.
A script you own on the backend
A pipe handler runs a Python, Go, or Bash script that reads the event JSON and calls an SMS API. It is maximally flexible and it is also code your team maintains, tests, and secures, including the API token sitting on the Sensu backend. It fits teams that already want programmatic control over message content.
Recommended
Uses the email handler Sensu already documents
Set -toEmail to +1[phonenumber]@sendemailtotext.com on the standard sensu-email-handler. TextBolt converts the message into SMS through a registered 10DLC business number. No script, no token, and no extra asset on the backend.
On-call scheduling and escalation
These platforms have first-party Sensu integrations and add on-call schedules, escalation chains, phone calls, and mobile apps on top of SMS. GoAlert is open source, and the rest carry per-user licensing. They are the right answer for a large rotation with formal escalation policies, and more than most teams need if the text itself is the goal.
CUSTOMER REVIEWS
From DevOps to NOC teams, see how organizations use TextBolt to make sure critical Sensu Go alerts reach the right engineer by text message.

On Google Workspace Marketplace, with
263K+ installs
We were already using Sensu Go email notifications. TextBolt let us add SMS in less than an hour without changing our monitoring pipeline. Our on-call engineers now see critical alerts immediately.

Platform Engineer
SaaS Company
Replacing carrier email-to-SMS gateways was easier than expected. We simply pointed our Sensu email handler to TextBolt, and every production alert started arriving as a text message.

DevOps Manager
Financial Services
Our NOC relied on email for after-hours incidents, and important alerts were getting buried. Adding TextBolt gave us reliable SMS notifications without introducing another alerting platform.

Network Operations Lead
Managed Services Provider
The benefits that matter when adding SMS alerts to your Sensu monitoring workflow.
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)
Sensu Go has no native SMS handler, but it sends text alerts through handlers that pass events to outside services. The three practical paths are an email-to-SMS gateway like TextBolt, a custom pipe handler calling an SMS API, or an incident platform such as PagerDuty. The email path needs no code.
No custom script is required with an email-to-SMS gateway. The sensu-email-handler is an official, production-tested asset, and TextBolt is configured entirely through its existing flags in YAML. A script is only necessary if you call an SMS API such as Twilio directly.
The gateway address goes in the –toEmail flag of your sensu-email-handler command, inside the handler definition. Sensu sends the notification email to that address and TextBolt converts it into a text.
Carrier gateways are being retired and should not be used for new Sensu alerting. AT&T and T-Mobile have already shut theirs down, and Verizon ends vtext.com service on March 31, 2027. A handler pointed at a retired gateway fails silently, so alerts stop without any error in Sensu.
Sensu handlers pointed at @vtext.com need to move before March 31, 2027, when Verizon retires the gateway. The AT&T and T-Mobile gateways are already gone, so handlers still pointed at those addresses have stopped delivering. There is no error in Sensu when this happens, so the alerts simply go missing.
The best option depends on whether you need scheduling along with the text. TextBolt is the simplest path when your rotation is already settled and you only need the message delivered, since it uses the email handler with no script or per-user cost. PagerDuty, Opsgenie, and Zenduty are better when you need escalation chains and phone calls, and GoAlert covers the same ground as an open-source option you host yourself.
Yes, and the reply arrives as an email in the sending mailbox. Anyone watching that alert inbox sees the acknowledgement. The reply does not resolve or acknowledge the event inside Sensu itself, which still happens in sensuctl or the web UI.
Any event a handler receives can become a text, including keepalive failures, check results in warning or critical, resolution events, and flapping notices. If the event reaches your email handler, TextBolt delivers it as SMS.
TextBolt delivers to United States and Canada numbers only. Every gateway address uses the +1 country code. Teams with on-call engineers outside North America need a different gateway for those numbers.
TextBolt replaces the SMS delivery part, not the scheduling part. It sends texts from your existing email handler without per-user licensing. If you need on-call rotations, escalation chains, and phone calls, an incident platform still does more.
No, because TextBolt needs the backend to reach an outbound SMTP service. A fully offline deployment needs a local GSM modem or a hardware SMS gateway such as SMSEagle or Ozeki on the network instead.
Text the On-Call Engineer Without Maintaining a Script
Add SMS to your Sensu pipeline in about 30 minutes. Change one flag on the email handler and your checks, filters, and pipelines keep working exactly as written, now compliant and two-way.