Ready to Route Your Predix Edge or Cimplicity Alarms to SMS?

Your SCADA or HMI already knows how to send an email when an alarm trips. The problem is nobody is watching an inbox at 2 a.m. A text message is.
Whether you’re using GE Predix Edge, CIMPLICITY, or another SCADA, HMI, or building automation platform, you can convert existing SMTP alarm emails into SMS using an email-to-SMS gateway. There’s no need to build API integrations or modify your SCADA application because the workflow uses the email notifications your system already generates.
If you’re replacing legacy carrier gateways such as @vtext.com, @txt.att.net, or @tmomail.net, the migration is equally straightforward. Your SCADA system continues sending email, but instead of routing messages through retired carrier gateways, a business email-to-SMS gateway like TextBolt delivers them into SMS messages to the operator’s phone.
This guide is intended for controls engineers, facilities and BMS managers, system integrators, and industrial operations teams using GE Predix Edge, CIMPLICITY, iFIX, Wonderware/AVEVA, Ignition, or alarm dispatchers such as Alarm Cast and FirstPAGE. If your platform can send SMTP email, you can use the same workflow to deliver production alarms as SMS.
TL;DR
Email-to-SMS for SCADA means configuring your industrial control systems to send critical alarm emails directly to mobile phones as SMS/text messages. When an alarm triggers, the SCADA system sends an SMTP email to an email-to-SMS gateway like TextBolt, which translates it into a text message or SMS alert for the on-call engineer.
Nearly every modern SCADA, HMI, and BMS platform supports SMTP notifications, including CIMPLICITY, Predix Edge, iFIX, Ignition, Wonderware/AVEVA, Alarm Cast, and FirstPAGE. Instead of sending alarms only to inboxes, those same email notifications can be routed directly to mobile phones without custom API integrations or hardware modems.
Supervisory Control and Data Acquisition (SCADA) and Human-Machine Interface (HMI) systems are built for industrial control rather than mobile messaging; they rely on basic SMTP (Simple Mail Transfer Protocol) to push notifications. The flow has three steps:
Industrial environments achieve this conversion in one of three ways:
Industrial facilities continue to rely on email-to-SMS because it builds on existing SCADA infrastructure instead of requiring new integrations or hardware. Most platforms already support SMTP notifications, making SMS deployment fast and cost-effective.
Of the three approaches, third-party email-to-SMS gateways have become the standard replacement for carrier gateways. With TextBolt, sending an alarm to +1XXXXXXXXXX@sendemailtotext.com delivers an SMS to any US or Canadian mobile number using a single address format, regardless of carrier.
That shift wasn’t driven by changes to SCADA systems. It was driven by the retirement of the carrier email-to-text gateways that industrial facilities had relied on for years.
For nearly two decades, industrial plants used free carrier email-to-text gateways to deliver alarms as SMS. As messaging volumes increased and business messaging became regulated under A2P 10DLC, carriers began retiring these services between 2025 and 2027.
| Carrier | Gateway address | Status as of 2026 |
| AT&T | @txt.att.net, @mms.att.net | Permanently discontinued June 17, 2025 |
| Verizon | @vtext.com, @vzwpix.com | Degrading, ~1 in 3 messages fail silently, full shutdown March 31, 2027 |
| T-Mobile | @tmomail.net | Effectively discontinued 2024 |
Even before the shutdowns, these gateways were a poor fit for alarm-grade traffic. They were never built for business-critical alerting, and three weaknesses bit plant teams the hardest.
The best email to SMS gateway most plants land on is a purpose-built business gateway. It solves each of those problems, but more importantly, it gives the plant something the free gateways never offered, an audit trail. When something goes wrong at 2 a.m. and the post-incident question is “was the on-call team actually notified,” a message log with timestamps and delivery status answers it in 30 seconds.
A Predix Edge or CIMPLICITY alarm follows a straightforward path. The SCADA system triggers an event, the dispatcher turns it into an email, the mail relay sends it through SMTP, and the email-to-SMS gateway converts it into a text message for the on-call team.

The diagram above shows the end-to-end notification flow, from the alarm generated by Predix Edge or CIMPLICITY to the SMS received by the on-call operator. Most of this workflow already exists in your environment. Your SCADA system detects the alarm, your notification service sends the email, and your SMTP server delivers it. TextBolt simply converts that email into a business SMS and forwards it to the recipient’s mobile phone.
Under normal conditions, the entire process completes within seconds. The only new component introduced is the email-to-SMS gateway, which sits between your mail server and the mobile carrier network.
The email that leaves your dispatcher and hits the gateway is a plain SMTP message. Nothing exotic. Here is what a real Cimplicity or Predix Edge alarm looks like on the wire, so you can compare it against what your dispatcher is actually sending:
From: alarms@yourplant.com
To: +15551234567@sendemailtotext.com
Subject: Critical Alarm – Cooling Tower Fan #1
Date: Tue, 01 Jul 2026 02:14:07 -0500
Content-Type: text/plain; charset=utf-8
CRITICALCooling Tower Fan #1 Failed
Location: Building A, roof
Time: 02:14 AM
Acknowledge via reply or dispatcher
The gateway reads two things from that message: the From header (to authorize the sender) and the plain-text body (to send as the SMS).
Everything else, including the Subject, Date, Content-Type, and Message-ID, is standard SMTP metadata that the gateway parses but does not use in the outbound SMS body. If your dispatcher sends multipart or HTML-only messages instead, the parsed body ends up empty and the message is dropped, which is one of the three silent failure modes covered later.
While the workflow itself is straightforward, two design principles determine how reliable it remains in production.
The notification service (Alarm Cast, FirstPAGE, or a custom .bcl script) sends one email to every intended recipient. TextBolt then converts that single email into an individual SMS for each operator.
This means there are no SMS distribution groups to maintain inside TextBolt. Your on-call rotation continues to be managed where it already exists, making it easier to add or remove engineers without keeping multiple contact lists synchronized.
Unlike consumer messaging systems, TextBolt authenticates the sender email address before processing notifications. Every mailbox or service account that sends alarms, whether it’s a production mailbox, shared service account, or test environment, should be registered before deployment.
Registering every sender email address during setup helps prevent notification failures and ensures every alarm follows the same trusted delivery path.
Setting up GE Predix Edge SMS alerts or CIMPLICITY SMS notifications typically takes about 30 minutes, plus 1-2 business day for A2P verification. Most migration issues come from three preventable mistakes:
The steps below help you avoid all three.
Before updating your dispatcher, gather the following information. Correcting these details after deployment can delay your migration.
US carriers require every business sender on a 10DLC pipe to be registered. So, complete your A2P 10DLC registration using your legal business name, EIN, website, sample messages, and expected message volume. Approval typically takes one business day, although corrections may extend the process.
This registration is completed once per legal entity and covers all sites operating under that brand.
You only do this once per brand. Every alarm, every recipient, every site under the same legal entity uses the same registration. After it clears, you move to the address-level authorization, which is where most migrations actually get stuck.
Beyond the brand-level 10DLC approval, the gateway checks the specific sender address on every inbound email. If the From is not on your authorized list, the message is dropped with no bounce, no SMS, no log entry. Your dispatcher records a successful send. The gateway records nothing. The alarm is gone, and nobody notices until the post-incident review.
The fix is to register every From address your dispatcher might use, not just the obvious one:
Review the authorized sender list after infrastructure changes, firmware updates, or new deployments to ensure new service accounts are included.
Update each recipient to the email-to-SMS format:
+1<mobile-number>@sendemailtotext.com
If you are migrating from a carrier gateway such as @vtext.com, the change is typically a domain swap plus the +1 prefix.
For CIMPLICITY, navigate to:
Project → Equipment → Alarm Cast Gateway → User ID
Then configure the recipient list under Settings. Multi-project deployments should also verify the listening TCP port assigned to each project.
Keep escalation rules, distribution lists, severity levels, and acknowledgements inside the dispatcher. The gateway should only handle the email-to-SMS conversion.
The gateway converts the email body into the SMS message. If the dispatcher places alarm details only in the subject line, or sends HTML without a plain-text body, recipients may receive a blank message.
Most dispatchers handle this with a single checkbox in the alarm action: include the message body, or equivalent.
Subject-line passing can be turned on as a per-account setting if you need it, but the body almost always wins because the SCADA subject is usually a system identifier like ALM_42_HIGH, not the human-readable alarm. Nobody on call wants to wake up to a hex-style alarm code.
Trigger an actual alarm condition. Not a mock send. Not a test email from your laptop. A real alarm that exercises the same path your production traffic will use.
Walk it through in order:
If three or four phones receive it, the test fails. That is not a “mostly worked” outcome. Missing phones almost always trace to formatting (no +1, a non-NANP number, a stray space, a dash where the dispatcher does not expect one). Fix every gap before going live. Catching one missing recipient at 2 a.m. during a real incident is much more expensive than the 10 minutes you save by skipping the test now.
If your organization operates multiple plants, register the sender brand under the parent company’s legal entity. Individual sites can continue using their own authorized sender addresses, but the A2P 10DLC registration should remain tied to the parent organization.
Multi-site setups are one common special case. If any of those sites also run WIN-911, that platform brings its own set of quirks worth handling before you cut over.
Many migrations involve WIN-911 V7 or V2021 environments. WIN-911’s email notifier requires:
Register that mailbox as an authorized sender in TextBolt.
Before going live, also verify:
WIN-911 also supports hardware SMS modems, but teams evaluating WIN-911 alternatives often replace them with an email-to-SMS gateway to remove the need for SIM cards, cellular contracts, and hardware maintenance.
Ready to Point Your Dispatcher at the Gateway?
The setup is quick once A2P 10DLC verification clears, with affordable plans available. Migrate before your next on-call rotation.
Once the notification path is configured and tested, the next step is deciding which alarms should generate SMS notifications and which are better suited for email or dashboard alerts.
SMS should be reserved for alarms that require an immediate response. Routine notifications are better suited for email, dashboards, or scheduled reports. Limiting SMS to high-priority events helps reduce alert fatigue and ensures critical notifications receive immediate attention.
The most common SMS-worthy alarms fall into four categories.
Typical building automation alarms include:
Building Management Systems (BMS) is the noisiest category by a wide margin. These systems often generate large numbers of related alarms from a single fault. Use alarm suppression, de-bouncing, and severity filtering in the dispatcher so only actionable events generate SMS notifications. On Johnson Controls sites the same filtering logic applies to Metasys alarms delivered as text, where the Event Filter trims the noise before the alarm email ever leaves the server.
GE Predix Edge, CIMPLICITY, and other SCADA platforms commonly generate alarms such as:
These events typically have higher operational impact than building automation alarms. Configure the dispatcher to send SMS only for critical or high-severity events, while routing warnings and informational alarms to email.
Power-related SMS alerts commonly include:
Power events often occur in bursts during outages or transfers. Plan SMS capacity for peak event volumes rather than average daily traffic.
SMS alerts are also valuable for monitoring supporting infrastructure, including:
These alerts usually originate from monitoring platforms such as PRTG, Datadog, or Zabbix rather than the SCADA system itself. Register each monitoring platform’s sender address separately so notifications follow the same email-to-SMS workflow.
Two-way acknowledgements allow engineers to reply with messages such as “ACK” or “GOT IT,” with the response delivered back to the sender’s mailbox. This provides a simple acknowledgement workflow without requiring a separate mobile application.
Each alarm is delivered individually to every member of the on-call rotation. Adding or removing recipients only requires updating the dispatcher contact list, while TextBolt handles SMS delivery to each authorized mobile number.
Most SCADA email-to-SMS migration guides focus on configuration but overlook what happens when message delivery fails. In production, silent failures are more dangerous than visible errors because the dispatcher records a successful SMTP send while no SMS is ever delivered.
Most delivery failures fall into three categories:
The gateway only converts an email into an SMS if the From address matches an authorized sender on your account. Unlike consumer messaging, where the recipient’s phone number determines delivery, business email-to-SMS gateways use the sender address as the primary authorization check.
If your dispatcher sends from an unregistered or malformed address, such as one containing an extra quotation mark, a second @ symbol, or an invalid domain, the email is rejected before SMS conversion. The dispatcher and mail relay still record a successful SMTP transaction, but no SMS is sent because the sender fails the gateway’s authorization check.
✗ From: “alarms@yourplant.com” <“alarms@”@yourplant.com> ← stray second “@”, parsed as a DIFFERENT address → dropped
✓ From: alarms@yourplant.com
✓ From: “Plant Alarms” <alarms@yourplant.com>
This commonly happens because industrial environments or SCADA platforms use multiple sender addresses over time, including service accounts, test mailboxes, site-specific addresses, and firmware-generated accounts. Every sender must be explicitly authorized.
A Predix Edge service account starts sending after a firmware refresh with a brand-new local-part nobody added to the authorized list. Every sending address has to be on the registered list, and the registration is exact-match: display names like “Plant Alarms” do not matter for authorization, only the bracketed address inside the < > does.
How to detect this in production: Compare the alarm dispatcher’s outbound log to the TextBolt message log on a weekly basis for the first month after migration. If the dispatcher shows 47 sends and the gateway shows 38 conversions, the missing 9 are coming from an unregistered sender. Compare dispatcher logs with gateway logs during the first few weeks after migration. Missing conversions usually indicate an unregistered sender address.
By default, the gateway converts the email body into the SMS message. If your GE Predix Edge, CIMPLICITY, or other SCADA dispatcher places alarm details only in the Subject line, or sends an HTML-only email without a plain-text body, the gateway has no message content to convert. The resulting SMS may be blank or display “None,” depending on the carrie
There are two ways to resolve this:
In many GE Predix Edge and CIMPLICITY deployments, the subject line contains identifiers such as ALM_42_HIGH, while the email body includes the descriptive alarm message, such as Cooling Tower Fan #1 Failed. Using the email body provides operators with clear, actionable information.
This issue commonly appears when migrating from legacy carrier gateways such as @txt.att.net, which convert the email subject into the SMS message by default. Modern business email-to-SMS gateways use the email body unless subject forwarding is explicitly enabled.
How to detect this in production: Trigger a test alarm from GE Predix Edge or CIMPLICITY after migration and verify that the SMS contains the complete alarm message. If the SMS is blank, displays “None,” or contains only sender information, the dispatcher is not populating the email body correctly.
Delivery is US and Canada mobile (NANP) only. International recipients will not receive the text, and the gateway does not return an error to your dispatcher (the message is accepted, then dropped at the carrier handoff with no visible signal).
If international engineers require SMS alerts, provision a US or Canadian number for alerting or use an alternative 2-way text messaging platform. Forwarding services, dual-SIM setups, and dedicated alerting phones all work. Trying to route international recipients through the gateway and hoping for the best leaves a recipient class out of the rotation without any signal that they are missing alarms.
How to detect this in production: Cross-reference your on-call recipient list against the +1 country code on every entry before going live. Any non-NANP number is a guaranteed silent drop and should either be replaced with a NANP number or routed through a different alerting tool.
Beyond the common migration issues, a few operational considerations can affect the reliability and efficiency of your email-to-SMS workflow. Planning for them upfront helps reduce unnecessary alerts, simplify troubleshooting, and improve long-term reliability.
| Case | What happens | Recommended approach |
| Alarm storm | A single equipment fault can generate dozens of related alarms, resulting in large SMS fan-outs and unnecessary notifications. | Apply de-bouncing, alarm grouping, and severity filtering in the dispatcher. Send SMS only for actionable or critical alarms. |
| Fan-out message usage | Each recipient receives an individual SMS. Long messages may be split into multiple SMS segments (approximately 160 characters each), increasing message usage. | Keep alarm messages concise and size your messaging plan based on expected alarms, recipients, and message segments. |
| Quiet periods | No SMS messages may be sent for days or weeks when no alarms occur. | Schedule a periodic heartbeat or test alarm to verify the notification path remains operational. |
| Outbound SMTP or firewall restrictions | Firewalls, mail relays, or security tools such as UFW or Fail2ban may block or rate-limit outbound SMTP traffic. | Allowlist the SMTP path and verify connectivity before migration. Ensure security controls do not block production or test notifications. |
| Attachments or images | SMS supports text only. Attachments and embedded images are removed during conversion. | Include essential alarm details in the message body and link to dashboards or monitoring systems when additional context is required. |
| Delivery verification | After an incident, operators may need to confirm whether an alarm was successfully delivered. | Use the TextBolt message log to review timestamps, delivery status, and message history for every notification. |
Most of these issues are easy to avoid with proper configuration. The next consideration is understanding how the email-to-SMS path performs under production workloads and what level of reliability you can realistically expect.
Avoid Silent Alarm Drops on Your Next Migration
TextBolt logs every send with timestamp and delivery status, so you can audit the gap between dispatcher output and SMS delivery rather than guessing at it during a post-incident review.
Reliable enough to trust on operational alarms, with specific numbers and caveats worth understanding before you go live. The six dimensions below cover what plant teams actually ask during evaluation.
Single-digit seconds, end to end. The path from your dispatcher’s outbound SMTP to the SMS landing on a phone runs in roughly 2 to 10 seconds under normal carrier load. Most of that variance sits in the cellular handoff, not the gateway itself, which processes each message in well under a second. If you see minute-plus delays in normal conditions, check your mail relay queue or the recipient carrier first; the gateway is rarely the bottleneck.
Well-configured deployments typically achieve up to 98% delivery rates when using verified business senders, A2P 10DLC registration, supported US and Canadian carriers, and properly formatted messages.
No SMS provider can guarantee 100% delivery because the final handoff depends on mobile carrier networks. Scheduling a periodic heartbeat alarm provides an easy way to detect delivery issues before a real incident occurs.
Every send is logged with sender, recipient, body, delivery status, and timestamp. The log lives on the TextBolt dashboard and is queryable by date range. When the post-incident question of “was the on-call team actually notified” comes up, you can pull a timestamped delivery record instead of relying on assumption. For regulated industries that need to demonstrate notification compliance, this is the difference between a finding and a clean audit.
Replies route back to the sender’s email inbox, which is the same address your dispatcher sent From. An engineer texts “ACK” or “GOT IT” and the dispatcher or ops team sees the reply in the inbox where they already manage email-based escalation. That two-way path is what makes the gateway feel like a paging tool rather than a one-way fire-hose, and it is the workflow the carrier gateways killed under A2P rules before the gateways themselves went dark.
Texts arrive from a shared business number by default, or from a dedicated toll-free number for an extra $45/year. The dedicated number gives the on-call staff a consistent inbound caller-ID they learn to recognize as plant alarms at a glance, which reduces ignored-text incidents during storms. The shared number works for outbound-only alerts but weakens two-way trust because the inbound rotates. Most plants running production alarms with acknowledgement workflows pay the $45.
No additional on-premises hardware is required. Your SCADA platform, dispatcher, SMTP relay, and on-call workflows remain unchanged. The migration typically involves only two configuration updates:
With the technical requirements covered, the next step is replacing any remaining legacy carrier email-to-SMS gateways with a modern, supported email-to-SMS workflow. The checklist below walks through the migration process.
If you’re looking for a vtext / txt.att.net replacement, TextBolt provides a modern business email-to-SMS gateway that preserves your existing SCADA workflow. Instead of rebuilding your notification system, you simply register your business for A2P 10DLC, authorize your sender email addresses, and replace legacy carrier gateway addresses.
Use the checklist below to complete the migration with minimal disruption.
Complete these checks before making any configuration changes:
Once your business verification is underway:
Before relying on the new notification path for production alarms:
Most plants complete the whole migration inside 1 to 2 business days end to end: the configuration itself is roughly 30 minutes, and the rest is waiting on A2P 10DLC verification. If your stack is CIMPLICITY-specific, the CIMPLICITY email-to-SMS integration page walks through the exact Alarm Cast and .bcl script changes, the User ID setup, and the sender-authorization steps you would run through on a real project.
Book a demo or email support@textbolt.com with a description of your alarm flow. A real engineer will map your setup before you commit to the migration.
Stop Relying on Legacy Carrier Gateways
Move your CIMPLICITY alarm notifications to reliable business SMS with TextBolt. No APIs, no SCADA changes, and no new infrastructure to manage.
No. If your alarm system can send email, and Predix Edge, Cimplicity, iFIX, Ignition, Wonderware/AVEVA, Alarm Cast, and FirstPAGE all can, you only change the destination addresses to +1XXXXXXXXXX@sendemailtotext.com and register your dispatcher’s sender address. There is no SDK to install and no firewall change on the gateway side. Most plants are sending their first test SMS within 30 minutes of finishing business verification.
Yes. Address the alarm email to each person’s +1<number>@sendemailtotext.com address and the gateway delivers one SMS per recipient. Recipients are unlimited on TextBolt plans, so adding a person to the rotation is a single line in your dispatcher’s contact list, not a billing event. If your dispatcher supports distribution lists, those work too.
Almost always one of two things. Either your dispatcher put the alarm in the email subject only, or it sent an HTML-only email with no plain-text part. The gateway texts the body by default, so an empty body becomes an empty (or “None”) SMS. Move the alarm text to the body, or ask support to enable subject passing on your account.
In nine cases out of ten, the missing alarms are coming from an unregistered sender address. A new service account, a one-off test address, or a per-site local-part that nobody remembered to register. The gateway silently drops mail from unauthorized senders to protect your account from spoofing. Audit the from addresses your dispatcher is actually sending from (not the ones you intended to use) and add every one to your registered sender list.
Probably not, alarms are event-driven and a quiet plant is a healthy plant. The reliable answer is to schedule a recurring heartbeat alarm (one a day is plenty) that fires regardless of plant state. If the heartbeat arrives, the path is live. If the heartbeat fails, you have a real signal to investigate. Do not infer health from silence.
Yes. Replies route back to the sender’s email inbox, which is the same address your dispatcher sent From. That is what makes two-way acknowledgement work without a separate app. An engineer texts “ACK” and the dispatcher sees the reply in its inbox or shared mailbox, where the existing escalation rules can act on it.