{"id":254,"date":"2026-04-02T22:07:20","date_gmt":"2026-04-02T22:07:20","guid":{"rendered":"https:\/\/text.email\/blog\/?p=254"},"modified":"2026-04-02T22:07:20","modified_gmt":"2026-04-02T22:07:20","slug":"opw-fuel-management-text-alerts","status":"publish","type":"post","link":"https:\/\/text.email\/blog\/opw-fuel-management-text-alerts\/","title":{"rendered":"OPW Fuel Management Text Alerts: How to Get SMS Notifications From Your Fuel System"},"content":{"rendered":"\n<p>OPW&#8217;s SiteSentinel consoles can track <em>everything<\/em> happening underground at your fuel site: tank levels, water intrusion, leak test results, probe failures, deliveries, theft detection, and a ton of other things (including the very one you&#8217;re thinking of now that somehow I forgot).<\/p>\n\n\n\n<p>That&#8217;s a lot of data, and pretty much all of it matters.<\/p>\n\n\n\n<p>But&#8230; most of it lives on the console screen or buried in an email inbox.<\/p>\n\n\n\n<p>So when you get an alarm email from your SiteSentinel and it lands right alongside vendor invoices, compliance paperwork, and the email from your mom because she still hasn&#8217;t figured out she should send to your personal Gmail \u2014 <strong>nothing about it screams &#8220;look at me right now.&#8221;<\/strong><\/p>\n\n\n\n<p>A text message does.<\/p>\n\n\n\n<p>So that&#8217;s why we&#8217;re here: To <strong>get your OPW fuel management system to send you real SMS texts when something at the site needs attention<\/strong>. And to do it <strong>without an long, drawn-out, complicated, expensive process<\/strong>.<\/p>\n\n\n\n<p>I&#8217;ll take you through the setup, which only takes about ten minutes and works with every SiteSentinel model that can send email.<\/p>\n\n\n\n<p>Let&#8217;s go&#8230;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"table-of-contents\">OPW Fuel Management Text Alerts: Table of Contents<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"#how-to-set-up-opw-sitesentinel-text-alerts-through-your-existing-email-path\">How to Set Up OPW SiteSentinel Text Alerts Through Your Existing Email Path<\/a><\/li>\n\n\n\n<li><a href=\"#what-happened-to-the-sitesentinels-built-in-sms-options\">What Happened to the SiteSentinel&#8217;s Built-In SMS Options?<\/a><\/li>\n\n\n\n<li><a href=\"#opw-fuel-management-text-alerts-without-the-enterprise-overhead\">OPW Fuel Management Text Alerts Without the Enterprise Overhead<\/a><\/li>\n\n\n\n<li><a href=\"#leak-tests-tank-levels-and-probe-failures-which-opw-alerts-deserve-a-text\">Leak Tests, Tank Levels, and Probe Failures: Which OPW Alerts Deserve a Text<\/a><\/li>\n\n\n\n<li><a href=\"#start-getting-opw-fuel-management-text-alerts-on-your-phone\">Start Getting OPW Fuel Management Text Alerts on Your Phone<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"how-to-set-up-opw-sitesentinel-text-alerts-through-your-existing-email-path\">How to Set Up OPW SiteSentinel Text Alerts Through Your Existing Email Path<\/h2>\n\n\n\n<p>Here&#8217;s how we&#8217;re going to get text alerts, using an email-to-text option that slides right into your current setup.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Sign up at text.email<\/h3>\n\n\n\n<p>text.email takes emails and turns them into text messages. You send an email to an address based on your phone number, and it shows up on your phone as a regular text.<\/p>\n\n\n\n<p><strong>You don&#8217;t need an app or any extra hardware<\/strong>. Go to <a href=\"https:\/\/text.email\">text.email<\/a> and create an account.<\/p>\n\n\n\n<p>You&#8217;ll get a special email address you can use for email-to-SMS. (It will be like <code>yournumber@yourprivatekeyword.text.email<\/code>).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Make sure your SiteSentinel has network and SMTP set up<\/h3>\n\n\n\n<p>Your console needs two things before any of this works: an internet connection and an SMTP mail server.<\/p>\n\n\n\n<p>For the network side, head to <strong>Settings &gt; System &gt; Networking<\/strong> on your SiteSentinel and confirm you&#8217;re on LAN\/WAN. If you&#8217;re running an Integra, that&#8217;s <strong>Configuration &gt; System &gt; Networking<\/strong>.<\/p>\n\n\n\n<p>If you&#8217;ve been getting emails from the console at all, this is probably already done.<\/p>\n\n\n\n<p>Next, go to <strong>Settings &gt; System &gt; Email &amp; SMS<\/strong>. On an Integra, that&#8217;s <strong>Configuration &gt; System &gt; Email &amp; SMS<\/strong>.<\/p>\n\n\n\n<p>The Integra sidebar might show it as &#8220;Email &amp; SM&#8221; because the label gets cut off in the nav, but you&#8217;re in the right place.<\/p>\n\n\n\n<p>The top half of this screen is your SMTP setup. Here&#8217;s what goes in each field:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Server Name<\/strong>: your SMTP server hostname<\/li>\n\n\n\n<li><strong>Port Number<\/strong>: usually 587 or 465<\/li>\n\n\n\n<li><strong>Username<\/strong> and <strong>Password<\/strong> for authentication<\/li>\n\n\n\n<li><strong>SiteSentinel Email Address<\/strong>: the &#8220;from&#8221; address your console will use when it sends alerts<\/li>\n\n\n\n<li>Check <strong>SMTP Server Authentication<\/strong> if your mail server requires it (most do)<\/li>\n<\/ul>\n\n\n\n<p>If your site doesn&#8217;t have its own mail server, OPW actually recommends SMTP2GO (smtp2go.com) as a third-party relay. Works fine for this.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Add a text.email contact to your Address Book<\/h3>\n\n\n\n<p>Now go to <strong>Settings &gt; Address Book<\/strong> and hit the Add button. On an Integra, that&#8217;s <strong>Configuration &gt; Address Book &gt; Add<\/strong>.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><a href=\"https:\/\/text.email\/blog\/wp-content\/uploads\/2026\/04\/opw-contactform-tinified.png\"><img loading=\"lazy\" decoding=\"async\" width=\"736\" height=\"676\" src=\"https:\/\/text.email\/blog\/wp-content\/uploads\/2026\/04\/opw-contactform-tinified.png\" alt=\"\" class=\"wp-image-257\" srcset=\"https:\/\/text.email\/blog\/wp-content\/uploads\/2026\/04\/opw-contactform-tinified.png 736w, https:\/\/text.email\/blog\/wp-content\/uploads\/2026\/04\/opw-contactform-tinified-300x276.png 300w\" sizes=\"auto, (max-width: 736px) 100vw, 736px\" \/><\/a><\/figure>\n<\/div>\n\n\n<p>The contact form has the usual stuff: name, company, phone, fax, plus separate fields for Email and SMS.<\/p>\n\n\n\n<p>Important: <strong>put your text.email address in the Email field, not the SMS field.<\/strong><\/p>\n\n\n\n<p>So if your phone number is 212-555-1234, you&#8217;d type <code>2125551234@yourkeyword.text.email<\/code> in the Email line.<\/p>\n\n\n\n<p>Why the Email field and not SMS? Because the SMS field routes through OPW&#8217;s Clickatell integration, which has its own problems (we&#8217;ll get into those later).<\/p>\n\n\n\n<p>The Email field sends through your SMTP server, and text.email handles the <a href=\"https:\/\/text.email\/blog\/email-to-text\/\">email to text<\/a> conversion on the other end.<\/p>\n\n\n\n<p>Give the contact a name you&#8217;ll recognize later. Something like &#8220;SMS &#8211; Mike&#8221; or &#8220;Text Alert &#8211; Night Manager&#8221; keeps things clear when you&#8217;re picking contacts from a list.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Point your tank alarms at that contact<\/h3>\n\n\n\n<p>Now go to <strong>Settings &gt; Alarm Actions<\/strong>, pick a tank, and hit <strong>Details<\/strong>.<\/p>\n\n\n\n<p>You&#8217;ll see columns for each notification type. Click the person icon under the <strong>Email<\/strong> column and select your text.email contact from the Address Book. Then hit Apply.<\/p>\n\n\n\n<p>Yeah, it says &#8220;Email&#8221; in the column header. That&#8217;s fine. Your SiteSentinel thinks it&#8217;s sending an email, and it is. text.email just turns it into a text on the receiving end.<\/p>\n\n\n\n<p>You can assign up to five email contacts per alarm action, so if multiple people need texts, create a separate Address Book entry for each phone number.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Optional: Set up system-level alerts too<\/h3>\n\n\n\n<p>Tank alarms are just one category. Your SiteSentinel also fires alerts for equipment issues: power failures, probe communication errors, backup battery warnings, and so on.<\/p>\n\n\n\n<p>To get those as texts, go to <strong>Settings &gt; System &gt; Preferences &gt; Warnings<\/strong>. On an Integra, <strong>Configuration &gt; System &gt; Preferences &gt; Warnings<\/strong>.<\/p>\n\n\n\n<p>Same approach. You&#8217;ll see a grid of system events with notification columns. Click the person icon under Email for each event you care about, select your text.email contact, and Apply.<\/p>\n\n\n\n<p>One thing to watch for: there&#8217;s an Apply button for individual rows and a separate one for the whole table at the bottom. Make sure you hit both.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Test it before you trust it<\/h3>\n\n\n\n<p>Obviously, before you rely on this for your real alarms, you&#8217;re going to want to see it work.<\/p>\n\n\n\n<p>The fastest way is to send an email to your text.email address (like <code>2125551234@yourkeyword.text.email<\/code>) from any email client, just to confirm that side of the pipe is flowing.<\/p>\n\n\n\n<p>Then trigger a test alarm on your SiteSentinel. It&#8217;s probably best to temporarily set a product-low threshold above your current level so it trips right away, then set it back after.<\/p>\n\n\n\n<p><strong>You should get a text within a few seconds<\/strong>. If nothing shows up, check your SMTP settings. Usually it&#8217;s the &#8220;from&#8221; address on your SiteSentinel not being recognized by the SMTP provider.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"what-happened-to-the-sitesentinels-built-in-sms-options\">What Happened to the SiteSentinel&#8217;s Built-In SMS Options?<\/h2>\n\n\n\n<p>Your SiteSentinel does technically have SMS built in. If you&#8217;ve looked at the bottom half of that Email &amp; SMS screen, you&#8217;ve seen the fields.<\/p>\n\n\n\n<p>But both native options have pretty much aged into dead ends.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Dead: The Clickatell gateway<\/h3>\n\n\n\n<p><strong>OPW&#8217;s SMS integration is hardcoded to a single third-party provider called Clickatell<\/strong>. The fields are right there on the Email &amp; SMS screen: Gateway Address, User, Password, API ID.<\/p>\n\n\n\n<p>The iSite manual actually spells it &#8220;Clickatel&#8221; with one L, which gives you a sense of how much attention this feature has gotten over the years.<\/p>\n\n\n\n<p>To use it, you&#8217;d need a Clickatell account on their legacy HTTP API. But Clickatell has likely deprecated that legacy gateway platform and stopped creating new accounts for it.<\/p>\n\n\n\n<p>If you had an account before the deprecation, it might still work (though it probably won&#8217;t, based on some of the things around modern text regulations we&#8217;ll discuss shortly). But if you&#8217;re setting this up fresh today, this path probably isn&#8217;t available.<\/p>\n\n\n\n<p>And even if you could get in, <strong>you&#8217;d be building on a deprecated API that will disappear entirely at some point in the near-ish future<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Alive, but perilous: The GSM modem option<\/h3>\n\n\n\n<p>The other native SMS path is a <strong>physical GSM modem connected to one of your SiteSentinel&#8217;s serial ports<\/strong>. You&#8217;d need the modem itself, a SIM card, and a cellular plan.<\/p>\n\n\n\n<p>Then you&#8217;d check the &#8220;Use GSM Modem&#8221; box in each Address Book contact.<\/p>\n\n\n\n<p>It works, technically. But do you <em>really<\/em> want to maintain a whole separate piece of cellular hardware on site just to get a handful of critical alerts on your phone? <\/p>\n\n\n\n<p>That&#8217;s a lot of overhead and a really fragile, hardware-intensive setup for something that really should be simple.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Dead: Cell phone carrier gateways<\/h3>\n\n\n\n<p>There used to be a completely different workaround that may sound vaguely familiar to you. Every major cell phone carrier ran <a href=\"https:\/\/text.email\/blog\/email-to-sms\/\">email-to-SMS<\/a> gateways, where you&#8217;d email an address like <code>2125551234@txt.att.net<\/code> and it&#8217;d arrive as a text.<\/p>\n\n\n\n<p>Plenty of fuel sites had these gateway addresses saved in their SiteSentinel Address Books for years.<\/p>\n\n\n\n<p>The carriers shut all of them down. <a href=\"https:\/\/text.email\/blog\/att-email-to-text\/\">AT&amp;T<\/a>, <a href=\"https:\/\/text.email\/blog\/tmobile-email-to-text\/\" data-type=\"post\" data-id=\"24\">T-Mobile<\/a>, <a href=\"https:\/\/text.email\/blog\/verizon-email-to-text\/\" data-type=\"post\" data-id=\"20\">Verizon<\/a>, and the rest \u2014 all gone. If you had one in your system, your alerts have been vanishing silently.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Overkill: DIY texting setups<\/h3>\n\n\n\n<p>You could build your own SMS pipeline with something like <a href=\"https:\/\/text.email\/blog\/twilio-alternatives\/\">Twilio<\/a>. But that&#8217;s a new system you have to maintain and make sure <em>it<\/em> doesn&#8217;t break.<\/p>\n\n\n\n<p>Plus, every cell phone carrier now require something called <a href=\"https:\/\/text.email\/blog\/a2p-10dlc\/\">A2P 10DLC registration<\/a> for any application-to-person texting. <strong>If you don&#8217;t have it, your texts will not be delivered<\/strong>.<\/p>\n\n\n\n<p>That means registering your brand, registering your campaign, paying carrier fees, and waiting weeks for approval.<\/p>\n\n\n\n<p>It&#8217;s a regulatory framework designed for companies sending thousands of marketing texts, not for a fuel site manager who needs to know when a leak test fails.<\/p>\n\n\n\n<p>text.email handles all of that on their end. You just use the email address.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"opw-fuel-management-text-alerts-without-the-enterprise-overhead\">Get OPW Fuel Management Text Alerts Without the Enterprise Overhead<\/h2>\n\n\n\n<p>So this is all you need to get text messages for critical alerts \u2014 and to get them going today.<\/p>\n\n\n\n<p>You can <strong>kick off the process right now by signing up at <a href=\"https:\/\/text.email\">text.email<\/a>, getting your email-to-text address, and then plugging it into your system<\/strong>.<\/p>\n\n\n\n<p>text.email plans include 200 messages per month&#8230; through really, you&#8217;re not paying by quantity (since you probably won&#8217;t have anywhere close to 200 critical alerts in a month). This is <strong>all about the moment where you actually find out instantly when something went wrong at the site<\/strong>.<\/p>\n\n\n\n<p>Want to try it out? You can do that for free, just send an email to <code>yournumber@text.email<\/code> (with your actual 10-digit number) and see it arrive as a text.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"leak-tests-tank-levels-and-probe-failures-which-opw-alerts-deserve-a-text\">Leak Tests, Tank Levels, and Probe Failures: Which OPW Alerts Deserve a Text?<\/h2>\n\n\n\n<p>Not everything your SiteSentinel reports needs to buzz your phone.<\/p>\n\n\n\n<p>Here are some quick suggestions for how split your OPW alerts between text and email. (Your picks will be different based on your site and your role, because I don&#8217;t know you personally, but this will hopefully get you started.)<\/p>\n\n\n\n<p><strong>Always text these:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Product High-High \/ Product Low-Low:<\/strong> critical level alarms that can trigger pump shutoffs<\/li>\n\n\n\n<li><strong>Water High-High:<\/strong> water at critical levels<\/li>\n\n\n\n<li><strong>In-Tank Leak Test Failure:<\/strong> a failed leak test can&#8217;t wait<\/li>\n\n\n\n<li><strong>LLD Leak Test Failed<\/strong> (0.1 GPH and 0.2 GPH): line leak detection failures<\/li>\n\n\n\n<li><strong>Theft:<\/strong> product leaving the tank while the site is closed<\/li>\n\n\n\n<li><strong>Power Fail:<\/strong> your console lost power<\/li>\n\n\n\n<li><strong>Probe Failure:<\/strong> you&#8217;re blind on that tank until it&#8217;s fixed<\/li>\n\n\n\n<li><strong>VSmart \/ OM4 \/ LIM Comms Failure:<\/strong> lost communication with field hardware<\/li>\n<\/ul>\n\n\n\n<p><strong>Probably fine as email:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Product High \/ Product Low:<\/strong> early warnings, not emergencies<\/li>\n\n\n\n<li><strong>Water High:<\/strong> worth knowing, not critical yet<\/li>\n\n\n\n<li><strong>Delivery Start\/Finish:<\/strong> useful for reconciliation, not urgent<\/li>\n\n\n\n<li><strong>Density Variation Warning:<\/strong> worth investigating on your own timeline<\/li>\n\n\n\n<li><strong>Printer Failure:<\/strong> unless event printing is a compliance requirement for you<\/li>\n\n\n\n<li><strong>Open\/Close Site:<\/strong> routine operational events<\/li>\n\n\n\n<li><strong>Temperature alarms:<\/strong> depends on your product and your climate<\/li>\n<\/ul>\n\n\n\n<p>The SiteSentinel also has escalation alarms. If nobody acknowledges a critical alarm within a set time window, it can bump the notification to a second contact, then a third.<\/p>\n\n\n\n<p>That escalation works through the same Email column, so your text.email contacts slot right in.<\/p>\n\n\n\n<p>If you&#8217;re also running a <a href=\"https:\/\/text.email\/blog\/veeder-root-tls-text-alerts\/\">Veeder-Root TLS<\/a> system at another site, the same email-to-text approach works there too.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"start-getting-opw-fuel-management-text-alerts-on-your-phone\">Start Getting OPW Fuel Management Text Alerts Right Now<\/h2>\n\n\n\n<p><strong>Everything you need for quick text alerts is already on your OPW&#8217;s SiteSentinel<\/strong> \u2014 you&#8217;re just putting a text.email address where an email address used to go.<\/p>\n\n\n\n<p>So sign up at <a href=\"https:\/\/text.email\">text.email<\/a>, add your address to the SiteSentinel Address Book, and point it at your critical alarms.<\/p>\n\n\n\n<p>That way, the next time a probe drops or a leak test comes back bad, you&#8217;ll get know immediately \u2014 and won&#8217;t miss it \u2014 thanks to a text.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The quickest and easiest way to get text message alerts from your OPW Fuel Management SiteSentinel.<\/p>\n","protected":false},"author":2,"featured_media":261,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16,4],"tags":[],"class_list":["post-254","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-fuel-petroleum-storage","category-system-alerts"],"_links":{"self":[{"href":"https:\/\/text.email\/blog\/wp-json\/wp\/v2\/posts\/254","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/text.email\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/text.email\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/text.email\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/text.email\/blog\/wp-json\/wp\/v2\/comments?post=254"}],"version-history":[{"count":6,"href":"https:\/\/text.email\/blog\/wp-json\/wp\/v2\/posts\/254\/revisions"}],"predecessor-version":[{"id":262,"href":"https:\/\/text.email\/blog\/wp-json\/wp\/v2\/posts\/254\/revisions\/262"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/text.email\/blog\/wp-json\/wp\/v2\/media\/261"}],"wp:attachment":[{"href":"https:\/\/text.email\/blog\/wp-json\/wp\/v2\/media?parent=254"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/text.email\/blog\/wp-json\/wp\/v2\/categories?post=254"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/text.email\/blog\/wp-json\/wp\/v2\/tags?post=254"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}