Get Transmitter Fault Alerts by Text

At 3:40 AM a transmitter drops carrier. The remote control emails the alarm exactly as programmed, and no engineer’s phone makes a sound.
Broadcast transmitter fault text alerts via email for engineers close that gap. If your remote control, silence sensor or site monitor already emails off-air, carrier loss, modulation loss, STL or exciter alarms, TextBolt turns each alarm email into a text on your on-call engineers’ phones.
TextBolt is an email-to-SMS gateway. It replaces the carrier gateways that station alarms used to rely on (@tmomail.net, @txt.att.net and @vtext.com), which have stopped converting email or are being shut down.
A broadcast transmitter fault alert is any alarm that a system sender at the site detects and emails. Typical alarms are off-air, carrier loss, modulation loss, exciter fault, STL loss, dead air or silence, high VSWR, AC mains failure, and tower light failure.
The alarm usually comes from one of three system senders:
You will learn below how to turn that existing email into a text with.out rewiring anything at the site.
Transmitter alarm emails fail overnight for two reasons. An email alarm only works if someone is reading mail. And the free carrier gateways that once turned that email into a text are shut down or being sunset.
| Carrier Gateway | Domain | Status | Date |
|---|---|---|---|
| AT&T | txt.att.net, mms.att.net | Shut down: Alarm emails sent here no longer arrive as texts | June 17, 2025 |
| T-Mobile | tmomail.net | Quietly stopped: Alarm emails sent here no longer arrive as texts | Late 2024 |
| Verizon | vtext.com | Sunsetting: Alarm emails sent here will stop arriving as texts | By March 31, 2027 |
Older setup guides and forum answers still list these addresses as working, so treat them as history. A site configured from one of them may already be paging nobody. Often the first sign is an overnight outage that no engineer heard about until the morning log review.
Your transmitter’s remote control, silence sensor or site monitor already emails an alarm when a fault occurs. Keep that email and change only its recipient to an email-to-SMS address, and the service delivers the alarm as an SMS to each engineer’s phone.
The transmitter’s alarm logic stays exactly as it is; only the address the email goes to changes. Changing the recipient on one unit takes a few minutes. Plan the full cutover around account setup, about 30 minutes, plus business registration approval, which can take up to 48 hours before the first text goes out.
Any system sender that can email an alarm works. These broadcast units can send their alarms by email.
| System sender | What it can send |
|---|---|
| Burk ARC Plus | Alarm notifications by email, or SMS directly |
| Broadcast Tools Site Sentinel | Email alarms to up to eight recipients |
| Davicom | Email alarms |
| DEVA DB2003 | Email, SMS and SNMP alerts |
| Inovonics | Email alarms |
The email-to-SMS service never connects to the transmitter itself. It does not matter whether the rig is a Nautel or a GatesAir unit. What matters is which box at the site emails the fault. Menu names for the recipient field differ by model and firmware, so check the unit’s manual for where the email recipient is set.
The email-to-SMS service receives alarms from any system that can send an email. SNMP-only gear needs a unit that converts its alarms into email first. Burk’s Plus-X SNMP and the Broadcast Tools Site Sentinel are two units that can turn SNMP alarms into email. The same rule applies to HMI and PLC alarm setups. If the panel can send an email, the recipient swap above works. If it can only send SNMP traps, put an email-capable unit between the panel and the email-to-SMS service.
TextBolt is built for the chief or contract engineer who covers several unstaffed transmitter sites and needs every site’s alarm on one phone. Nothing at the site needs new code or an integration project. Each site’s system sender keeps emailing, and TextBolt handles the hop to SMS.
More than 3,000 teams use TextBolt, including broadcast engineers who route off-air and transmitter alarms through it.
Any business texting US phones has to register that traffic with the carriers, and a station paging its own engineers is no exception. TextBolt files the registration for each US account, so the engineering team never handles the paperwork.
Carriers review the business details covered in TextBolt’s A2P 10DLC registration guide before approving, which can take up to 48 hours. Keep the old alarm recipients in place until the first test text arrives.
Get Every Site’s Transmitter Alarm on Your Phone
TextBolt turns the alarm emails your remote controls already send into texts for each engineer on call. Move one site over during the free trial.
There are several ways to get a transmitter alarm onto a phone. The right one depends on whether the site’s email path is reliable and how much hardware you want to maintain.
| Option | How the alarm reaches the phone | Where it fits | Tradeoff |
|---|---|---|---|
| TextBolt | The existing alarm email goes to an email-to-SMS address | Sites whose system senders already email alarms | Depends on the unit reaching its mail server; no automatic retry |
| Cellular hardware gateway (such as SMSEagle) | An appliance at the site sends SMS over the cellular network | Sites with an unreliable internet link, since the text goes out over the cellular network | Another device to install and maintain |
| Remote control unit with built-in SMS (such as Burk units) | The remote control sends SMS itself | Stations already standardized on that hardware | Tied to that unit’s features |
| GSM remote unit | A standalone cellular unit texts on dry-contact alarms | Simple sites with contact closures | Limited alarm detail in the text |
| Other email-to-SMS services (such as Text.email, Notifyre) | An email-to-SMS address, as with TextBolt | Teams that need extras such as MMS, fax or healthcare compliance options alongside email-to-SMS | Setup and registration terms vary by provider |
If your remote control or monitor already emails its alarms, an email-to-SMS address works with what the site sends today. A hardware gateway only earns its place where the site’s internet link cannot be trusted.
A daily check-in is a scheduled email from your system sender that arrives as a text on every engineer’s phone at a known time. If the text does not show up, the alert chain is broken, and you find out before a real outage does.
A failed fault text does not announce itself. TextBolt sends each message once, and it does not page anyone when an engineer’s number is blocked or unreachable.
Every send does leave a record. TextBolt’s SMS Activity / History page lists each text as Delivered or Undelivered, with a reason such as “Unreachable destination handset” when it fails. A daily check-in makes sure someone reads that record before a real outage does it for them.

Many engineers already have the remote control send a daily “still online” email. Sending that same email to every engineer’s text address tests the whole path, from the site to each phone.
An off-air alarm that waits in an inbox until morning costs airtime the station cannot get back. A carrier gateway that quietly stopped working makes it worse, because the setup looks correct until the night it matters.
TextBolt keeps every remote control, silence sensor and site monitor emailing the way it does today. The alarm lands on each engineer’s phone as a text, replies come back as email, and anyone moving off an old address can follow the carrier gateway migration guides.
Start with one site. Once registration is approved (up to 48 hours), point that site’s daily check-in at one engineer’s text address. After a few days of on-time texts, add the other engineers and the other sites.
Your next step: Start your TextBolt free trial and move your first site tonight.
A TextBolt plan costs $29/month, and each account gets a dedicated US toll-free or 10DLC number for outbound SMS, registered for business use. One customer replaced a five-figure SMS API project with that plan.
No developer or integration cost applies, because only the alarm’s recipient address changes. The free trial lets you move one site first and confirm the texts arrive before you change the others.
No. Your existing remote control, silence sensor or site monitor keeps emailing the alarm, and the only change is the recipient address, so no code, SDK or integration project is involved. Check the unit’s manual for where its email recipient is set.
Not necessarily. Burk-class remote controls can send SMS directly, which suits stations already standardized on that hardware. The tradeoff is that you are tied to that unit’s features. Email-to-SMS works with any unit that sends email and keeps every alarm and reply searchable in your inbox.
You need a system sender that can email the alarm, its sending address (often a noreply@ address) and each engineer’s mobile number. US business texting also requires A2P 10DLC registration, and approval can take up to 48 hours. Start the registration before you schedule any cutover at the site.
Yes. The unit must reach its mail server to send the alarm email, and the text is created after that. If the site’s internet link drops, no email leaves and no text goes out. Sites with an unreliable link may need a cellular hardware gateway instead.
Yes. An engineer can reply to the alarm text and the reply comes back as an email. The service does not escalate if nobody answers, so that logic stays in your remote control or monitor.
Yes. Keep the existing email recipients on the alarm and add the engineers’ text addresses to the recipient list. The email copy stays in your inbox as a searchable audit trail, while the text alerts the engineer’s phone.