Alarm and Facility System Text Alerts by Email to Text

HomeBlogAlarm & Facility Text Alerts
Alarm and Facility Text Alerts

TextBolt is an email to SMS gateway that turns the email alerts your alarm panel, building automation system or facility monitor already sends into text messages on your on-call technician’s phone. Change the notification recipient to +1[PhoneNumber]@sendemailtotext.com. No SDK, no code, no new hardware. The older route uses a carrier email-to-text gateway in the [5551234567@vtext.com](mailto:5551234567@vtext.com) format, and the carriers are shutting those gateways down one at a time.

Picture a Sunday at 4:15 AM in mid-January. A freeze stat trips on the air handler that serves a school gym. The building automation system does what someone configured it to do years ago: it emails the facilities lead’s AT&T gateway address. After the AT&T email-to-text shutdown, the gateway no longer delivers. No bounce comes back and no error appears. The BAS log says the alarm went out. On Monday the custodian finds water on the gym floor.

The panel did its job. The address is what failed. If a system can send an email, it can still send a text. Below, you’ll follow an alarm from the trigger at a freeze stat, boiler, or generator through the four steps of the email-to-SMS path, see which carrier gateway addresses have stopped delivering, and move your alerts to a path you can check.

How Email-to-Text Works for Alarm and Facility Systems

Email-to-text for alarm and facility systems reuses the email notification the equipment already sends. The alert moves through four steps:

  1. Trigger: An HVAC controller, boiler, freeze stat, backup generator, fire or security panel, or SCADA system detects a fault.
  2. Email Dispatch: The system sends its alert over SMTP. Many system senders relay through a Gmail or Outlook account.
  3. Gateway Routing: The email arrives at an email to an SMS gateway address, such as +1[PhoneNumber]@sendemailtotext.com.
  4. SMS Delivery: The gateway converts the email into a text message. The subject and body become the text on the technician’s phone.

Nothing changes on the panel except the recipient address.

Carrier Email-to-Text Gateway Addresses and Status

Standard carrier email-to-SMS gateways use the pattern [10-digit number]@[carrier domain]. The Verizon example is [5551234567@vtext.com](mailto:5551234567@vtext.com). Alarm and facility systems set up years ago often still send to these addresses. Three major carriers have shut theirs down or scheduled the shutdown.

CarrierSMS gatewayMMS gatewayStatusDateReplacement
T-Mobiletmomail.nettmomail.netStopped quietlyLate 2024+1[PhoneNumber]@sendemailtotext.com
AT&Ttxt.att.netmms.att.netShut downJune 17, 2025+1[PhoneNumber]@sendemailtotext.com
Verizonvtext.comvzwpix.comScheduled to endBy March 31, 2027+1[PhoneNumber]@sendemailtotext.com

The same addresses as a list:

  • T-Mobile: [number@tmomail.net](mailto:number@tmomail.net). It stopped in late 2024.
  • AT&T: [number@txt.att.net](mailto:number@txt.att.net) and [number@mms.att.net](mailto:number@mms.att.net). Shut down June 17, 2025.
  • Verizon: [Number@vtext.com](mailto:Number@vtext.com) and [number@vzwpix.com](mailto:number@vzwpix.com). Sunset scheduled by March 31, 2027.

Format note: The two address types are written differently. Carrier gateways use the 10-digit number with no country code ([5551234567@vtext.com](mailto:5551234567@vtext.com)). The sendemailtotext.com address uses +1 followed by the 10-digit number (+1[PhoneNumber]@sendemailtotext.com).

These same retired domains also broke patron notices in library systems. Our walkthrough of why library ILS hold and overdue text alerts stopped covers that case.

Why Carrier Gateways Fail for Alarm Alerts

Carrier email-to-text gateways were never built for alarm and facility alerts. Here is where they break, and what a dedicated email-to-SMS service does instead:

  • Shut down or scheduled: The gateway’s status depends on each recipient’s carrier, and three major carriers have retired theirs or set a date. Instead one sendemailtotext.com domain is used for every recipient, whatever their carrier.
  • Silent failures: Messages sent to a retired gateway are dropped with no bounce and no error, so the alarm system logs the alert as sent. Instead the service shows delivery status per message.
  • Filtering and rate limits: Carriers filter and throttle gateway traffic. A burst of alarms is the traffic most likely to be held back. Instead alerts go out from a registered business number.
  • No delivery receipts or audit trail: A carrier gateway gives you no record that a technician received anything. Instead every alert and reply sits in your inbox, where you can search and archive it.
  • No two-way acknowledgment: A technician cannot answer an alarm through a carrier gateway. Instead replies thread back to the sending inbox.

Route Alarm and Facility Alerts Through TextBolt’s Email to SMS Service

A dedicated email-to-SMS service is the route for alarm and facility text alerts. TextBolt is a business-grade, drop-in replacement for the retired carrier email-to-SMS gateways (txt.att.net, vtext.com, tmomail.net) and a simpler alternative to code-heavy SMS APIs: a team changes an email address instead of running an integration project. TextBolt lets any system or team that can send an email send and receive text messages: text customers straight from your inbox with replies threaded back, or pipe alerts from monitoring tools, alarm panels, and IoT sensors to a phone, all with no code or APIs.

What Does TextBolt Change for an Alarm System?

  • One address per recipient: Each technician gets one destination, +1[PhoneNumber]@sendemailtotext.com. You no longer look up carriers, and delivery works across all major US and Canadian carriers.
  • No integration project: No SDK. No code. The email your system already sends just goes to a different address.
  • Registered sending: Business texting in the US requires A2P 10DLC registration. TextBolt is a Verified A2P 10DLC business sender and registers each US account. The 10DLC compliance guide explains what registration involves.
  • Two-way: Text replies come back to email. The section on acknowledgment below explains how.

How Do You Set Up Alarm and Facility Text Alerts in TextBolt?

Setting up alarm and facility text alerts through an email to SMS gateway takes five steps:

  1. List your system senders: Write down every alarm panel, BAS, SCADA or HMI, generator controller and monitoring tool that emails alerts, along with every recipient address each one uses.
  2. Create your account: Sign up for TextBolt, and 10DLC registration is handled for your US account. Approval can take up to 48 hours, and texts can’t go out until it completes, so start before your cutover window.
  3. Swap the recipient: In TextBolt’s [confirmed module name], add the email address each system sends alerts from, such as its noreply@ address. Then replace each carrier address in the system’s notification settings with +1[PhoneNumber]@sendemailtotext.com.
  4. Keep the alert short: Stay within one SMS segment of 155 characters and put the location and fault code first. For example, FREEZE STAT AHU-3 | Bldg B mech rm | 34F.
  5. Test it: Trigger a manual test alarm on each system and confirm delivery status in the dashboard.

Send Critical Facility Alerts Straight to Your Phone

Set up TextBolt to receive important alarm notifications by SMS and keep your team informed when issues arise.

Which Alarm and Facility Alerts Should Go to Text?

Send only critical alarm and facility alerts to SMS. If every routine status email becomes a text, technicians learn to ignore their phones. Good candidates:

  • Freeze stat trips and low-temperature alarms
  • Main power loss or backup generator failure
  • Fire panel and security panel alarms
  • Boiler lockouts and HVAC failures in occupied spaces
  • High-level and temperature excursions from SCADA or sensors

Daily reports, filter-change reminders and routine status emails can stay in the inbox.

Can Technicians Acknowledge an Alarm Text by Replying?

Yes. Two-way texting lets the on-call technician answer the alarm text itself with a reply like “ON IT” or “BLDG B, ARRIVING 20 MIN”. The reply returns to the sending inbox as a timestamped email, threaded with the original alert.

The inbox then works as your alarm log. You can search it, archive it and hand it to whoever reviews incidents. Two details to know:

  • Panel senders: Many panels and BAS platforms send from a noreply@ address. Replies to those alerts go to the inbox you designate when you register the sender.
  • The panel itself: A reply arrives as an email. It does not clear or acknowledge the alarm inside the panel or BAS.

Which Alarm and Facility Systems Can Send Texts Through TextBolt?

Any system that emails alerts over SMTP can deliver them as SMS through a sendemailtotext.com address. Common senders include:

  • Monitoring and alerting tools: PagerDuty, Opsgenie, Datadog, Nagios, UptimeRobot, AWS CloudWatch, Grafana and custom webhooks. Point each tool’s alarm email at +1[PhoneNumber]@sendemailtotext.com and send a test alarm.
  • Alarm panels: Honeywell, ADT, DSC, Bosch and Notifier panels that send email notifications.
  • Building automation systems (BAS): Tridium Niagara and Metasys installations that email alarm notifications.
  • SCADA and HMI: Any SCADA or HMI notification list that can address an email can send SCADA text alerts through the same path.

Which Email to SMS Option Fits Alarm and Facility Alerts?

Alarm and facility teams have several ways to get alerts to a phone as SMS. Here is how they compare:

OptionHow alerts get inCode requiredDelivery status visibleReplies thread back to the sender’s inboxTypical fit
Carrier email-to-text gatewaysEmail to number@carrier domainNoNoNoLegacy setups. Shut down or scheduled to end.
TextBoltEmail to +1[PhoneNumber]@sendemailtotext.comNoYesYesAlarm, facility and monitoring alerts from existing email
Cloud SMS platforms with email-to-SMS relay (e.g., TextMagic, ClickSend)Email-to-SMS relay featureNo, for the email pathYes, delivery trackingVaries by vendorTeams that want a broader texting suite or multi-channel reach
SMS APIsProgrammatic integrationYesVaries by vendorVaries by vendorCustom software builds
Mass notification platformsPlatform-specificVaries by platformVaries by platformVaries by platformOrganization-wide emergency broadcasts
Hardware cellular dialersContact inputs, SNMP, Modbus or RTUNoVaries by deviceVaries by deviceSites wiring alarms directly to on-site hardware

TextMagic pairs email-to-SMS with a broader texting suite (shared inboxes, automation and apps) and suits irregular senders through non-expiring prepaid credits. ClickSend focuses on multi-channel reach (SMS, MMS, voice and physical mail), offers email-to-SMS as a secondary feature, and suits high-volume global senders.

Frequently Asked Questions

Why does my building automation system log an alarm as sent when nobody got the text?

Because the system only records that it sent the email, not that anyone received a text. When an alert goes to a retired carrier gateway, the message is silently dropped. No bounce or error returns, so the BAS or panel log still shows the alarm as sent. Carrier gateways also give no delivery receipt, so that log cannot prove a technician got anything.

Who can send texts through our account?

For a panel or BAS, the setup adds its forwarding noreply@ sending address in the Co-Worker/Alert Module, and the service texts the subject and body of its emails to the +1[PhoneNumber]@sendemailtotext.com recipient.

How long does setup take?

Switching a sender typically takes about 30 minutes: add the forwarding noreply@ address in the Co-Worker/Alert Module, then replace the To: address with the new one. Registration is the slower part, because US 10DLC approval can take up to 48 hours.

How do I confirm a test alarm was actually delivered as a text?

Trigger the test from the alarm system itself, then check the delivery status in your email-to-SMS service’s dashboard. Do not rely on the system’s own log, which only shows the email was sent. If the service does not retry failed sends, fix the cause of a failed test and run it again.

How do I page a second technician if the first one doesn’t respond to an alarm text?

Set up escalation in your alarm system or paging tool, not in the email-to-SMS path. The text service moves the message and does not watch the alarm, so it does not resend a failed text, alert you to a blocked number, or page anyone else. A technician’s text reply returns as an email and does not clear the alarm inside the panel or BAS.

Written by
Rakesh Patel
Rakesh Patel
Founder and CEO of TextBolt
Rakesh Patel is an experienced technology professional and entrepreneur. As the founder of TextBolt, he brings years of knowledge in business messaging, software development, and communication tools. He specializes in creating simple, reliable solutions that help businesses send and manage text messages through email. Rakesh has a strong background in IT, product development, and business strategy. He has helped many companies improve the way they communicate with customers. In addition to his technical expertise, he is also a talented writer, having authored two books on Enterprise Mobility and Open311.