Email doesn’t interrupt you \u2014 it sits in an inbox until you happen to check it, and for critical alarms, “when you happen to check” isn’t fast enough.<\/p>\n\n\n\n
This is especially true at smaller facilities. If you’ve got two operators splitting on-call and nobody watching screens at 2 AM, you need alarms that behave like something urgent. That means SMS.<\/p>\n\n\n\n
I’ll walk you through turning your SCADA system’s existing email alerts into text messages on your phone. This works across Ignition, VTScada<\/a>, AVEVA, FactoryTalk, GE iFIX, Geo SCADA \u2014 anything that can send an email. If SMTP is already configured, you’re looking at about a minute of setup.<\/p>\n\n\n\n We’ll also get into why the older methods for SCADA SMS have either died or become disproportionately expensive for what small operations need.<\/p>\n\n\n\n Your SCADA system sends an email, that email arrives as a text on your phone. No middleware, no hardware, no Twilio account.<\/p>\n\n\n\n text.email<\/a> is an email-to-text service<\/a> \u2014 the only one where you sign up and start receiving texts immediately<\/strong>. You send an email to a special address, it shows up as a text.<\/p>\n\n\n\n text.email handles A2P 10DLC carrier compliance<\/a> automatically (more on why that matters later).<\/p>\n\n\n\n Sign up, pick a private keyword for your account, and your delivery address becomes: Any email sent to that address arrives as a text. You’ll plug this into your SCADA notification settings in Step 3.<\/p>\n\n\n\n If you’re already receiving email alerts<\/strong>, skip to Step 3. SMTP is working and you don’t need to touch it.<\/p>\n\n\n\n If not, you need to set up an outbound SMTP connection. The navigation depends on your platform:<\/p>\n\n\n\n Ignition:<\/strong> Gateway \u2192 Config \u2192 Alarming \u2192 Notification \u2192 Email Settings. Version 8.1+ supports OAuth2 SMTP profiles.<\/p>\n\n\n VTScada:<\/strong> Application Configuration \u2192 Edit Properties \u2192 Alarms tab \u2192 Outgoing Email. Requires an external SMTP server. Recent versions support OAuth 2.0.<\/p>\n\n\n\n AVEVA System Platform \/ Wonderware:<\/strong> SMTP config under Alarm Notification in the Management Console. Varies by version.<\/p>\n\n\n\n Schneider Geo SCADA (ClearSCADA):<\/strong> Email Action under alarm redirection rules.<\/p>\n\n\n\n FactoryTalk View SE:<\/strong> SMTP settings in FactoryTalk Alarms and Events notification server properties.<\/p>\n\n\n\n GE iFIX:<\/strong> Alarm notification through the Alarm ODBC add-on or custom SMTP scripting.<\/p>\n\n\n\n Google killed “Less Secure Apps” access, so your regular Gmail password won’t work for SMTP anymore. You need an App Password.<\/p>\n\n\n\n Enable 2-Step Verification on the Gmail account, then generate an App Password at Google Account \u2192 App Passwords<\/a>. Google gives you a 16-character code \u2014 that’s what goes in the SMTP password field.<\/p>\n\n\n\n If your facility runs its own mail server or Microsoft 365, get the SMTP details from your IT team. (If you’re not sure what SMTP server to use<\/a>, we’ve got a guide for that too.) One thing worth knowing: the sender address must be a valid account on the SMTP server.<\/strong> The SCADA system will happily accept an invalid sender without complaint \u2014 emails just won’t go out.<\/p>\n\n\n\n In your SCADA system’s alarm notification settings, add a new contact or recipient<\/strong> with the email address: Ignition:<\/strong> In your Alarm Notification Pipeline, add a user to your On-Call Roster with the text.email address as their email contact. Ignition’s pipeline system lets you route different alarm priorities to different contacts \u2014 critical to SMS, advisory to email.<\/p>\n\n\n\n VTScada:<\/strong> Add the text.email address to a contact in your Alarm Notification System roster. Put it in the email field, not the SMS field.<\/strong> VTScada’s SMS functionality relied on carrier gateways that no longer work. The email path is your replacement.<\/p>\n\n\n\n Geo SCADA \/ ClearSCADA:<\/strong> Add the text.email address as the recipient in your Email Action. Alarm redirection rules control which alarms trigger it.<\/p>\n\n\n\n Everything else:<\/strong> Find wherever you configure email recipients for alarm notifications. It’s a standard email address \u2014 anywhere your SCADA system sends email, it can send a text through text.email<\/strong>.<\/p>\n\n\n\n You don’t want a text for every advisory and setpoint adjustment. That’s how you get alert fatigue, and alert fatigue means operators start ignoring texts the same way they ignored email.<\/p>\n\n\n\n Most SCADA platforms let you filter by priority, category, or area. Route critical and high-priority alarms<\/strong> to the text.email recipient. Leave the rest on standard email. I’ve got specific recommendations later in this article.<\/p>\n\n\n\n Trigger a test alarm or use your platform’s built-in email test. Confirm the text arrives.<\/p>\n\n\n\n If it doesn’t, start at the SMTP layer<\/strong> \u2014 can the SCADA system send a regular email to any address? If that’s not working, the problem is upstream of text.email.<\/p>\n\n\n\n The most common issue in industrial environments: the SCADA server sits on a segmented OT network and can’t reach an SMTP server.<\/strong> You need port 587 open for outbound SMTP from the SCADA server’s VLAN, or a mail relay on the OT side. Your integrator or network admin will know the right approach for your architecture.<\/p>\n\n\n\n Once a test text hits your phone, you’re done. Every alarm that passes your filters arrives as SMS.<\/p>\n\n\n\n Some SCADA systems had built-in SMS that worked by emailing carrier gateway addresses \u2014 Those gateways are all dead or dying.<\/strong> Verizon killed vtext.com<\/a>. AT&T shut down txt.att.net<\/a>. T-Mobile’s tmomail.net is non-functional<\/a>. The carriers pulled them because of A2P 10DLC compliance costs and spam abuse \u2014 no revenue, increasing regulatory burden, so they all pulled the plug.<\/p>\n\n\n\n If your platform’s documentation still references carrier gateway addresses, you’re configuring a path to infrastructure that no longer exists<\/a>. A lot of SCADA vendor documentation hasn’t been updated to reflect this.<\/p>\n\n\n\n (If an LLM recommended @vtext.com? Same issue:outdated training data.)<\/p>\n\n\n\n WIN-911, SCADALRT, ScadaPhone \u2014 purpose-built alarm notification systems that integrate via OPC or direct connectors. Escalation logic, shift-aware routing, voice callouts, two-way acknowledgment.<\/p>\n\n\n\n They start at several thousand dollars<\/strong> for the software license, require installation on or adjacent to your SCADA server, and come with annual support contracts. For a large facility with complex escalation across multiple shift teams, worth it. For a small plant where one or two people need a text when a pump faults, that’s a lot of infrastructure for a simple problem.<\/p>\n\n\n\nSCADA System Text Alerts: Table of Contents<\/h2>\n\n\n\n
\n
Setting Up SMS Text Alerts from Your SCADA System<\/h2>\n\n\n\n
Step 1: Sign up with text.email<\/h3>\n\n\n\n
yournumber@yourkeyword.text.email<\/code>.<\/p>\n\n\n\nStep 2: Make sure your SCADA system has SMTP configured<\/h3>\n\n\n\n
![\"\"](\"https:\/\/text.email\/blog\/wp-content\/uploads\/2026\/02\/scadatext-ignitionsetup-tinified-1024x487.png\")
<\/a><\/figure>\n<\/div>\n\n\nUsing Gmail as your SMTP relay<\/h4>\n\n\n\n
\n
![\"\"](\"https:\/\/text.email\/blog\/wp-content\/uploads\/2026\/02\/scadatext-vtscadasmtp-tinified.png\")
<\/a><\/figure>\n<\/div>\n\n\nStep 3: Add your text.email address as an alarm recipient<\/h3>\n\n\n\n
yournumber@yourkeyword.text.email<\/code><\/p>\n\n\n\nStep 4: Configure alarm filtering<\/h3>\n\n\n\n
Step 5: Test it<\/h3>\n\n\n\n
Why Older SCADA SMS Methods Stopped Working<\/h2>\n\n\n\n
The carrier gateways are dead<\/h3>\n\n\n\n
5551234567@vtext.com<\/code>, 5551234567@txt.att.net<\/code>, that kind of thing. VTScada’s Alarm Notification System is a well-known example. The SCADA system just emailed an address that the carrier converted to SMS on the other end.<\/p>\n\n\n\nDedicated alarm notification software is built for bigger operations<\/h3>\n\n\n\n
DIY means compliance paperwork<\/h3>\n\n\n\n