The ADAP-KOOL system (whether you’re on an AK-SM 800A, an older SM 800\/850, or a legacy SC 255 that refuses to die) has pretty strong alarm email capabilities<\/strong>. Whether it’s compressor faults, temperature excursions, controller offline events, high discharge pressure \u2014 the System Manager sees it all and can email about it.<\/p>\n\n\n\n The problem? Email is where urgent alerts go to be ignored<\/strong>.<\/p>\n\n\n\n And if you’re not on Alsense (aka Danfoss’s cloud monitoring platform that’s priced for chains and enterprise accounts) email is your only built-in alarm channel. There’s no native SMS option on the System Manager, and there never was.<\/p>\n\n\n\n This article covers how to turn your ADAP-KOOL email alerts into SMS text messages<\/strong>. If SMTP is already configured on your System Manager, you’re about 60 seconds from your first text.<\/p>\n\n\n\n If it’s not, we’ll get that set up too.<\/p>\n\n\n\n Note: This covers the AK-SM 800A, AK-SM 800\/850, and AK-SC 255 System Managers. If you’re on the older AKM Windows-based monitoring platform, the alarm routing works through AKM’s Alarm Router software \u2014 different setup, same concept.<\/em><\/p>\n\n\n\n Your Danfoss System Manager can already send alarm emails. We’re going to use an email-to-text tool to bring those to your phone as SMS messages<\/strong>.<\/p>\n\n\n\n Here’s how.<\/p>\n\n\n\n text.email<\/a> is the easiest email-to-SMS<\/a> service out there; it’s literally a drop-in replacement.<\/p>\n\n\n\n You give text.email your phone number (and\/or your teams’ numbers), and it gives you an email address. So anything sent to that address arrives as a text on your phone<\/strong>.<\/p>\n\n\n\n Sign up at text.email<\/a>. You’ll pick a private keyword for your account, and your delivery address becomes: text.email handles something called A2P 10DLC carrier compliance<\/a> on its end, which is essential if you want your texts to actually get delivered (we’ll get into why in the What Broke?<\/a><\/em> section). For now, just know that it’s handled.<\/p>\n\n\n\n We’re going to plug this address into your System Manager’s alarm settings in Step 3.<\/p>\n\n\n\n If you’re already getting alarm emails from your System Manager, skip to Step 3. Your email setup (and SMTP sending server) is working.<\/p>\n\n\n\n If not, you need to tell the System Manager how to send email. You’ll do this at Configuration \u2192 Alarms \u2192 Connections<\/strong> on the local touchscreen, StoreView Browser, or StoreView Web.<\/p>\n\n\n\n Sending through your Gmail account’s sending server is the easiest (or, at least, most universal) method. Danfoss themselves publish a setup guide for it, though it’s a little out of date so we’ve got updated instructions here.<\/p>\n\n\n\n The first step is to generate an App Password, which Google now requires if you want some other tool to send through your account.<\/p>\n\n\n\n To generate one:<\/p>\n\n\n\n Then fill in the Connections screen in System Manager:<\/p>\n\n\n\n That Reply-to field is mandatory and must be valid. If it’s not, the System Manager accepts the settings but silently drops every email.<\/p>\n\n\n\n Save, then test.<\/strong> Hit Send Test Email<\/strong> on the Connections screen.<\/p>\n\n\n If you’re using a facility mail server, Microsoft 365, or any other server you’ll fill in the same fields, just with different values. You’ll need to get the SMTP address, port, and credentials from your IT team.<\/p>\n\n\n\n One crucial thing: the Reply-to address has to resolve to a valid user on that server<\/strong>.<\/p>\n\n\n\n The System Manager needs to resolve hostnames. Under Configuration \u2192 Network<\/strong>, make sure DNS is set. Google’s 8.8.8.8 and 8.8.4.4 work if your IT team doesn’t have a preference.<\/p>\n\n\n\n In System Manager, navigate to Configuration \u2192 System \u2192 Users<\/strong>.<\/p>\n\n\n\n That’s it for the recipient. Now you need to tell the system which alarms to actually send.<\/p>\n\n\n\n Navigate to Configuration \u2192 Alarms \u2192 Alarm Routing<\/strong>.<\/p>\n\n\n\n The SM 800A has an Alarm Action Matrix<\/strong> that controls which alarms go where, with what delay, and under what conditions. It’s pretty flexible and perfect for our situation here.<\/p>\n\n\n\n The critical settings:<\/p>\n\n\n\n Go to Configuration \u2192 Alarms \u2192 Service<\/strong>.<\/p>\n\n\n\n Generate a test alarm. You should receive a text within seconds.<\/p>\n\n\n\n If you don’t:<\/p>\n\n\n\n The SC 255 is end-of-life. Danfoss recommends the SM 800A as the replacement, and the upgrade path exists. But “end of life” and “out of the building” are different things, and plenty of these are still running.<\/p>\n\n\n\n The email alarm setup is similar but the interface is different, and you won’t have the Alarm Action Matrix; routing options are more limited. The email-to-SMS conversion works identically though<\/strong>.<\/p>\n\n\n\n If you’ve looked into alarm notifications for Danfoss systems before, you’ve probably been pointed toward Alsense, Danfoss’s cloud monitoring platform<\/strong> (the artist formerly known as Danfoss Enterprise Services).<\/p>\n\n\n\n Alsense is a robust<\/em> platform with remote monitoring, alarm management, energy analytics, HACCP compliance, fleet-wide dashboards. It’s hosted on Azure, it requires a VPN connection to your store, and\u2026 it comes with ongoing subscription pricing.<\/p>\n\n\n\n For a chain managing 200+ locations, it makes sense. The per-store cost amortizes into nothing, and you get centralized visibility that’s tough to replicate.<\/p>\n\n\n\n For a single facility? A small independent chain? A cold storage warehouse that isn’t part of a food retail fleet?<\/p>\n\n\n\n You’re paying for a cloud analytics platform to solve a notification delivery problem<\/strong>.<\/p>\n\n\n\n The System Manager already knows what’s wrong and can already email about it. The gap is getting that email to your phone as a text. That’s not a hundreds or thousands of dollars-per-month problem.<\/p>\n\n\n\n For most of the past two decades, you could solve the SMS problem by putting a carrier gateway address in the email recipient field. For example, Today? Those gateways are gone. Every major U.S. carrier (Verizon<\/a>, T-Mobile<\/a>, AT&T<\/a>, and beyond) has shut them down.<\/p>\n\n\n\n There were a few reasons. Lots of spam was one. New, strict compliance rules (which I mentioned briefly earlier in this article) were another. And the gateways weren’t generating revenue for the carriers, so when the regulatory cost went up, they pulled the plug.<\/p>\n\n\n\n If an LLM (or, uh, the Danfoss manual) tells you to use @vtext.com for your Danfoss alarm recipient, it’s working off stale training data.<\/p>\n\n\n\n Yes, you could build your own pipeline: receive the alarm email, parse it, hit the Twilio API<\/a>, send an SMS.<\/p>\n\n\n\n But sending application-to-person texts now requires 10DLC registration with The Campaign Registry. That means registering your business, registering your campaigns, waiting for carrier approval, and keeping your registration alive.<\/p>\n\n\n\n Yes, even for a handful of alerts a month from a single facility; it’s the same registration burden whether you’re alerting on a compressor fault or blasting 50,000 marketing messages.<\/strong> The compliance overhead is wildly disproportionate to the use case.<\/p>\n\n\n\nDanfoss ADAP-KOOL SMS Alerts: Table of Contents<\/h2>\n\n\n\n
\n
Getting Text Alerts from Your Danfoss System Manager<\/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 email is properly configured on your System Manager<\/h3>\n\n\n\n
Using Gmail as your SMTP relay<\/h4>\n\n\n\n
\n
\n
![\"\"](\"https:\/\/text.email\/blog\/wp-content\/uploads\/2026\/02\/danfossadapkool-smtp-tinified-799x1024.png\")
<\/a><\/figure>\n<\/div>\n\n\nOther SMTP servers<\/h4>\n\n\n\n
DNS<\/h4>\n\n\n\n
Step 3: Point your alarm emails at text.email<\/h3>\n\n\n\n
\n
Step 4: Configure alarm routing<\/h3>\n\n\n\n
\n
Step 5: Test<\/h3>\n\n\n\n
\n
If you’re still on an AK-SC 255\u2026<\/h3>\n\n\n\n
Alsense Can Send SMS Alerts \u2014 But Do You Need It?<\/h2>\n\n\n\n
What Broke? Carrier Gateways and the DIY Dead End<\/h2>\n\n\n\n
5551234567@vtext.com<\/code> for Verizon or 5551234567@txt.att.net<\/code> for AT&T.<\/p>\n\n\n\nWhy building your own doesn’t scale<\/h3>\n\n\n\n
Get Started with text.email<\/h2>\n\n\n\n