A text message fixes that. Your phone treats a text differently than an email (harder to miss those alerts), and so do you (we’re still wired to notice and respond to texts fast<\/em>).<\/p>\n\n\n\n The good news is: We can turn your Veeder-Root TLS alarm emails into instant text messages using a simple process that only takes a few minutes to set up with zero engineering help<\/strong>.<\/p>\n\n\n\n I’ll show you exactly how in this article.<\/p>\n\n\n\n Here’s the 5 minute setup guide to getting these text alerts going.<\/p>\n\n\n\n We’re going to use text.email<\/a>, which is an email-to-text<\/a> tool. Any email sent to your text.email address shows up as a text on your phone within seconds. It was built specifically for situations like this, where a system can send email alerts but not texts.<\/p>\n\n\n\n Sign up, pick a private keyword, and you’ll get an address like On your TLS-450PLUS console, go to Menu > Setup > Automatic Events > Address Book<\/strong>.<\/p>\n\n\n\n Tap Actions > Add Contact<\/strong>. Enter your name and your text.email address in the Email field. That’s the only contact info the console needs.<\/p>\n\n\n\n If you want alerts going to multiple people, add each person’s text.email address as a separate contact. You can assign different contacts to different alarm types later.<\/p>\n\n\n\n This is where you tell the console what<\/em> to email you about and when<\/em>.<\/p>\n\n\n\n Go to Menu > Setup > Automatic Events > Autoconnect Tasks<\/strong> and tap Actions > Add Task<\/strong>.<\/p>\n\n\n\n Here are the key settings:<\/p>\n\n\n\n The “On Event” trigger is the one you want for alerts. (There’s also “On Time” for scheduled reports like daily inventory \u2014 useful, but not what you need for catching emergencies.)<\/p>\n\n\n\n The console sends email over your site’s Ethernet connection, so it needs working network access. Go to Menu > Setup > Communication > Ethernet Port<\/strong> and check that:<\/p>\n\n\n\n If your site network blocks outbound email<\/strong> (which is common), you’ll also need to set up an SMTP relay. Go to Menu > Setup > Communication > SMTP Relay<\/strong> and enter your mail server details. (If you need a quick one, text.email can provide that SMTP relay<\/a> for you.)<\/p>\n\n\n\n Before you walk away from the console, send a test email to make sure everything’s connected. On the SMTP Relay screen, there’s a Send Test Email<\/strong> button at the bottom. Enter your text.email address and hit send.<\/p>\n\n\n\n You should get a text on your phone within a few seconds. If it doesn’t come through, check Menu > Setup > Automatic Events > Task Log<\/strong> to see if the console recorded an attempt.<\/p>\n\n\n\n And if you’re on an older software version that doesn’t have the Send Test Email button, you can trigger a test alarm manually through the console’s diagnostics to see if the email fires.<\/p>\n\n\n\n So why do we need to use this process? It’s because sending texts is tricker than it seems (and way<\/em> tricker than sending emails).<\/p>\n\n\n\n The TLS-450PLUS has a few ways to get alarm data off the console… but not text messages.<\/p>\n\n\n\n Veeder-Root makes two free mobile apps: The Plus View<\/strong> and The Remote View<\/strong>. Plus View isn’t real-time, and requires opening the app to check your alerts. Remote View is designed to run on a tablet mounted at the counter.<\/p>\n\n\n\n There’s also InSite360<\/strong> and the newer Veeder-Root Device Management<\/strong> dashboard, which are cloud platforms for managing fleets of gauges across multiple sites. That’s overkill if you just have a handful of locations and just want a quick text if something is leaking.<\/p>\n\n\n\n The console itself has a beeper and LEDs<\/strong>, which are great if someone’s standing in front of it. But I’m guessing you aren’t<\/em> always standing in front of it.<\/p>\n\n\n\n So the TLS can email. It can beep. It can show you data in an app if you check. But it can’t send you a text.<\/p>\n\n\n\n So… maybe you have a vague memory of being able to send an email to a Verizon or AT&T email and get a text back.<\/p>\n\n\n\n And you’re right. That used<\/em> to exit. <\/p>\n\n\n\n Verizon, AT&T, T-Mobile, and every other cell phone carrier offered email-to-SMS gateways<\/a> for years, and plenty of people plugged those addresses into their notification configs.<\/p>\n\n\n\n But… all those gateways are now shut down.<\/strong> If you’ve got a Yes, you could build your own text alert system \u2014 after all, anything’s possible in the vibe coding era according to everyone thirsting for likes in my LinkedIn feed.<\/p>\n\n\n\n To set that up, you’d need a Twilio integration<\/a> and then to set up and test the code until you can reliably trust it to email you at that moment of crisis. <\/p>\n\n\n\n But there’s another surprise waiting for you. You’ll need to deal with something called A2P 10DLC<\/a><\/strong>. That’s a registration process that’s now required for any application sending texts in the U.S. (It’s actually a big reason why the cell phone carriers all shut down their email-to-text gateways.)<\/p>\n\n\n\n It’s not hard, per se, it’s just paperwork, delays, and then ongoing maintenance for the system. Basically, it’s reinventing the wheel and putting reliability at risk. And based on the cost savings, all that is to save, at most, a couple of bucks a month.<\/p>\n\n\n\n Alright. Ready to implement the email-to-text system I laid out?<\/p>\n\n\n\nVeeder-Root TLS Text Alerts: Table of Contents<\/h2>\n\n\n\n
\n
Setting Up SMS Alerts From Your Veeder-Root TLS-450PLUS<\/h2>\n\n\n\n
Step 1: Sign up for text.email<\/h3>\n\n\n\n
yournumber@yourkeyword.text.email<\/code>. That’s what you’ll plug into your TLS console’s Address Book in the next step.<\/p>\n\n\n\nStep 2: Add your text.email address to the TLS Address Book<\/h3>\n\n\n\n
![\"\"](\"https:\/\/text.email\/blog\/wp-content\/uploads\/2026\/03\/veeder-root-addemail-tinified-1024x581.png\")
<\/figure>\n\n\n\nStep 3: Create an Autoconnect Task for alarm-triggered emails<\/h3>\n\n\n\n
\n
![\"\"](\"https:\/\/text.email\/blog\/wp-content\/uploads\/2026\/03\/veeder-root-autoconnectedtasks-tinified-1024x565.png\")
<\/figure>\n\n\n\nStep 4: Make sure your network and DNS are set up<\/h3>\n\n\n\n
\n
Step 5: Send a test<\/h3>\n\n\n\n
Why Your TLS-450PLUS Couldn’t Text You Before<\/h2>\n\n\n\n
The TLS console’s own notification options<\/h3>\n\n\n\n
The old cell phone carrier gateways are dead<\/h3>\n\n\n\n
@vtext.com<\/code> or @txt.att.net<\/code> address sitting in your TLS Address Book right now, those emails aren’t just disappearing silently into the void.<\/p>\n\n\n\nWhat about building your own system?<\/h3>\n\n\n\n
Getting Started with Veeder-Root TLS Text Alerts<\/h2>\n\n\n\n