In this article, I’ll walk through how to route your CoreSense alarm emails to SMS so they hit your phone directly, using the same E3 or Site Supervisor interface you already have set up. Seriously, there’s no new hardware and you’ll be able to get this up and running in about five minutes flat.<\/p>\n\n\n\n
Copeland CoreSense Text Alerts: Table of Contents<\/h2>\n\n\n\n\n- How to Set Up Text Alerts from Your Copeland CoreSense’s E3 or Site Supervisor<\/a><\/li>\n\n\n\n
- Why the Site Supervisor’s Built-In SMS Feature Stopped Working<\/a><\/li>\n\n\n\n
- CoreSense Text Alerts: Get Started Now<\/a><\/li>\n\n\n\n
- What CoreSense Alerts Are Worth a Text (and What Can Stay on Email)<\/a><\/li>\n\n\n\n
- CoreSense Text Alerts: Wrap Up and Next Steps<\/a><\/li>\n<\/ul>\n\n\n\n
How to Set Up Text Alerts from Your Copeland CoreSense’s E3 or Site Supervisor<\/h2>\n\n\n\n
The setup here has two parts: getting set up to convert emails to texts, and then pointing your Site Supervisor’s alarm emails in the right direction. Again, the whole thing should take about five minutes.<\/p>\n\n\n\n
(Note: If you’re running a standalone Emerson E3 without CoreSense<\/a>, we have a separate guide for that.)<\/em><\/p>\n\n\n\nStep 1: Sign up for text.email<\/h3>\n\n\n\n
text.email<\/a> is an email-to-SMS service built specifically<\/em> for this kind of setup: systems that already generate email alerts but need those alerts to land on someone’s phone as a text.<\/p>\n\n\n\nYou’ll get an email address that’s yournumber@yourspecialkeyword.text.email<\/code>, and any email sent to that address gets delivered as an SMS to your phone.<\/p>\n\n\n\nSign up, pick your keyword, and you’ll have your text.email address ready to go<\/strong>.<\/p>\n\n\n\nStep 2: Open your Site Supervisor’s network settings and confirm SMTP is configured<\/h3>\n\n\n\n
Log into your E3 or Site Supervisor’s web interface.<\/p>\n\n\n\n
From here, go to Main Menu \u2192 Configure System \u2192 General System Properties \u2192 Network Settings<\/strong>. You’re looking for the Internet TCP\/IP section where your SMTP settings live.<\/p>\n\n\n\nIf your controller is already sending email alerts, this should already be filled in. You’ll see your SMTP server address and sender email.<\/p>\n\n\n\n![\"\"](\"https:\/\/text.email\/blog\/wp-content\/uploads\/2026\/03\/coresense-smtpconfig-tinified-1024x551.png\")
<\/figure>\n\n\n\nIf it’s not configured yet, you’ll need your SMTP server’s IP or hostname from your IT admin. Make sure the Sender Email address<\/strong> is a valid address on that SMTP server.<\/p>\n\n\n\nNeed an easy SMTP server just for these text alerts<\/a>? text.email can provide one.<\/em><\/p>\n\n\n\nStep 3: Add a user with your text.email address<\/h3>\n\n\n\n
Go to Main Menu \u2192 Configure System \u2192 Manage Users<\/strong>. You can either create a new user for text alert delivery or edit your current profile.<\/p>\n\n\n\nIn the user’s contact info, put your yournumber@yourkeyword.text.email<\/code> address in the Email<\/strong> field. Now when the controller sends an alarm email to this address, text.email converts it and delivers it as an SMS to your phone.<\/p>\n\n\n\nYou’ll notice there’s also a Mobile Phone (SMS)<\/strong> field \u2014 skip that one. It uses a different, and far, far, far less seamless delivery method that we’ll cover in the next section.<\/p>\n\n\n\nStep 4: Set up Alarm Communications for that user<\/h3>\n\n\n\n
Now you need to tell the controller which alarms should go to your new text alert user. Head to Main Menu \u2192 Configure System \u2192 Alarm Communications<\/strong>.<\/p>\n\n\n\nIn the Group<\/strong> tab, you can filter which alarm groups get sent: compressor faults, case temperatures, refrigerant leak detection, whatever matters most to you. You’ll also set the alarm priority level<\/strong> here.<\/p>\n\n\n\nThe controller uses a 0-99 priority scale (lower numbers = higher priority), and by default critical alarms sit at priority 20 and non-critical at 30.<\/p>\n\n\n\n
Click over to the Recipients<\/strong> tab and you’ll see a list of users. Select your text alert user and check the Email box<\/strong> next to their name.<\/p>\n\n\n\nFor most CoreSense setups, you’ll probably want to start by routing just the critical alarms (compressor lockouts, high case temps, refrigerant leaks) to text, and leaving the non-critical stuff on email<\/strong>. You can always change that up once you see how the volume feels.<\/p>\n\n\n\nWhy the Site Supervisor’s Built-In SMS Feature Stopped Working<\/h2>\n\n\n\n
If you’ve poked around the Site Supervisor’s alarm settings before, you probably noticed it already has an SMS option. There’s a Mobile Phone (SMS)<\/strong> field in Manage Users, an SMS toggle in the network settings, even retry and delay configuration.<\/p>\n\n\n\nCopeland built this feature specifically so you could get text alerts.<\/p>\n\n\n\n
And it used to work<\/strong>.<\/p>\n\n\n\nThe way it worked was through cell phone carrier email-to-SMS gateways<\/a>. You’d enter your phone number in a format like 5551234567@txt.att.net<\/code>, and AT&T would convert that email into a text message. Verizon had @vtext.com<\/code>, T-Mobile had @tmomail.net<\/code>.<\/p>\n\n\n\nCopeland’s own setup guide still lists these carrier addresses as the way to configure SMS alerts. Like, I’m looking at it right now. See:<\/p>\n\n\n\n![\"\"](\"https:\/\/text.email\/blog\/wp-content\/uploads\/2026\/03\/coresense-legacysms-tinified-1024x616.png\")
<\/figure>\n\n\n\nThe problem is that all the major carriers have shut those gateways down<\/strong>. AT&T, Verizon, T-Mobile have all pulled the plug over the last couple of years. And also Cingular hasn’t existed since, like, the Paris Hilton era.<\/p>\n\n\n\nSo if you followed Copeland’s documentation and entered your number in that @txt.att.net<\/code> format<\/a>, your texts just stopped arriving one day. The controller is still sending them. They’re just going nowhere.<\/p>\n\n\n\nThis isn’t a Copeland thing. The carriers killed these gateways themselves. <\/strong>Officially, they did it because of spam; but also, there were some newer regulations around business-to-consumer text messaging that weren’t worth the hassle to them.<\/p>\n\n\n\n(It you really want to get deep into the weeds on the modern history of the telecommunications industry, the regulatory framework is called A2P 10DLC<\/a>. Essentially, carriers now require any automated texting to be registered and approved.)<\/p>\n\n\n\nSo what about building your own replacement?<\/h3>\n\n\n\n
Those regulations are a big reason why it’s tough to just fire up your own email-to-text replacement.<\/p>\n\n\n\n
You’d need to register with the carriers, get a compliant phone number, set up an SMS API through something like Twilio<\/a>, and maintain that infrastructure yourself.<\/p>\n\n\n\nFor a controller that just needs to send a handful of critical alerts, that’s a massive amount of overhead<\/strong>. (Even dedicated alarm notification software like Win-911<\/a> can be more complexity than you need for straightforward compressor alerts.)<\/p>\n\n\n\nThat’s the gap that text.email fills. Instead of routing through dead carrier gateways or building your own SMS pipeline, you use the controller’s existing email capability (which still works perfectly) and let text.email handle the email-to-SMS conversion on the compliant side<\/strong>.<\/p>\n\n\n\nAre those the only options?<\/h3>\n\n\n\n
There is one other path that Copeland offers. They have their Connect+ \/ ProAct<\/strong> cloud monitoring platform, which handles alarm notifications at the mega enterprise level.<\/p>\n\n\n\nIt’s built for chains managing hundreds of stores \u2014 and also priced for chains managing hundreds of stores. If that’s not your situation, the process we’ve described in this article will get you there with a whole lot less overhead.<\/p>\n\n\n\n
CoreSense Text Alerts: Get Started Now<\/h2>\n\n\n\n
Alright, alright. You’re ready to go. So what’s next?<\/p>\n\n\n\n
Just follow the steps \u2014 and that means heading over to text.email<\/a> to sign up.<\/p>\n\n\n\nFor a CoreSense setup, 200 messages included in the text.email plans really should be more than enough. You’re not trying to text every routine defrost cycle. And really, what matters is that the one compressor lockout or high-temp alarm<\/strong> that happens on a Saturday night actually reaches someone’s phone.<\/p>\n\n\n\nIf you want to test it out, send a sample email to yournumber@text.email<\/code> and you’ll get the text in seconds. (You don’t need to sign up or anything to try that.)<\/p>\n\n\n\nAnd then get rolling, because you really are just a few minutes away from having this whole system set up and working.<\/p>\n\n\n\n
What CoreSense Alerts Are Worth a Text (and What Can Stay on Email)<\/h2>\n\n\n\n
Your E3 or Site Supervisor can generate a lot of alarm traffic, and you definitely don’t want all of it hitting your phone. Here’s a starting point for splitting them. Your priorities will obviously vary, but here’s what I’d do if you hired me. (P.S. Do not hire me. I am not qualified.)<\/p>\n\n\n\n
Route to text:<\/strong><\/p>\n\n\n\n\n- Compressor lockout (any CoreSense red-flash fault)<\/li>\n\n\n\n
- Case high temperature \u2014 critical priority<\/li>\n\n\n\n
- Refrigerant leak detection alarm<\/li>\n\n\n\n
- Compressor communication loss<\/li>\n\n\n\n
- Power failure \/ UPS failover<\/li>\n\n\n\n
- High discharge temperature lockout<\/li>\n\n\n\n
- Low oil pressure lockout<\/li>\n<\/ul>\n\n\n\n
Fine on email:<\/strong><\/p>\n\n\n\n\n- Case temperature return-to-normal<\/li>\n\n\n\n
- Compressor trip with auto-reset (CoreSense yellow\/orange flash)<\/li>\n\n\n\n
- Defrost cycle notifications<\/li>\n\n\n\n
- Lighting schedule alarms<\/li>\n\n\n\n
- Non-critical advisory messages (priority 30+)<\/li>\n<\/ul>\n\n\n\n
The alarm priority system in your E3 or Site Supervisor makes this easy to set up.<\/p>\n\n\n\n
In your Alarm Communications config, you can create separate communication groups: one for critical alarms routed to your text.email user, another for everything else routed to standard email recipients.<\/p>\n\n\n\n
(Another note: If you’re also running Danfoss ADAP-KOOL controllers<\/a> alongside your Copeland equipment, the same approach works there too.)<\/em><\/p>\n\n\n\nCoreSense Text Alerts: Wrap Up and Next Steps<\/h2>\n\n\n\n
How to Set Up Text Alerts from Your Copeland CoreSense’s E3 or Site Supervisor<\/h2>\n\n\n\n
The setup here has two parts: getting set up to convert emails to texts, and then pointing your Site Supervisor’s alarm emails in the right direction. Again, the whole thing should take about five minutes.<\/p>\n\n\n\n
(Note: If you’re running a standalone Emerson E3 without CoreSense<\/a>, we have a separate guide for that.)<\/em><\/p>\n\n\n\n text.email<\/a> is an email-to-SMS service built specifically<\/em> for this kind of setup: systems that already generate email alerts but need those alerts to land on someone’s phone as a text.<\/p>\n\n\n\n You’ll get an email address that’s Sign up, pick your keyword, and you’ll have your text.email address ready to go<\/strong>.<\/p>\n\n\n\n Log into your E3 or Site Supervisor’s web interface.<\/p>\n\n\n\n From here, go to Main Menu \u2192 Configure System \u2192 General System Properties \u2192 Network Settings<\/strong>. You’re looking for the Internet TCP\/IP section where your SMTP settings live.<\/p>\n\n\n\n If your controller is already sending email alerts, this should already be filled in. You’ll see your SMTP server address and sender email.<\/p>\n\n\n\n If it’s not configured yet, you’ll need your SMTP server’s IP or hostname from your IT admin. Make sure the Sender Email address<\/strong> is a valid address on that SMTP server.<\/p>\n\n\n\n Need an easy SMTP server just for these text alerts<\/a>? text.email can provide one.<\/em><\/p>\n\n\n\n Go to Main Menu \u2192 Configure System \u2192 Manage Users<\/strong>. You can either create a new user for text alert delivery or edit your current profile.<\/p>\n\n\n\n In the user’s contact info, put your You’ll notice there’s also a Mobile Phone (SMS)<\/strong> field \u2014 skip that one. It uses a different, and far, far, far less seamless delivery method that we’ll cover in the next section.<\/p>\n\n\n\n Now you need to tell the controller which alarms should go to your new text alert user. Head to Main Menu \u2192 Configure System \u2192 Alarm Communications<\/strong>.<\/p>\n\n\n\n In the Group<\/strong> tab, you can filter which alarm groups get sent: compressor faults, case temperatures, refrigerant leak detection, whatever matters most to you. You’ll also set the alarm priority level<\/strong> here.<\/p>\n\n\n\n The controller uses a 0-99 priority scale (lower numbers = higher priority), and by default critical alarms sit at priority 20 and non-critical at 30.<\/p>\n\n\n\n Click over to the Recipients<\/strong> tab and you’ll see a list of users. Select your text alert user and check the Email box<\/strong> next to their name.<\/p>\n\n\n\n For most CoreSense setups, you’ll probably want to start by routing just the critical alarms (compressor lockouts, high case temps, refrigerant leaks) to text, and leaving the non-critical stuff on email<\/strong>. You can always change that up once you see how the volume feels.<\/p>\n\n\n\n If you’ve poked around the Site Supervisor’s alarm settings before, you probably noticed it already has an SMS option. There’s a Mobile Phone (SMS)<\/strong> field in Manage Users, an SMS toggle in the network settings, even retry and delay configuration.<\/p>\n\n\n\n Copeland built this feature specifically so you could get text alerts.<\/p>\n\n\n\n And it used to work<\/strong>.<\/p>\n\n\n\n The way it worked was through cell phone carrier email-to-SMS gateways<\/a>. You’d enter your phone number in a format like Copeland’s own setup guide still lists these carrier addresses as the way to configure SMS alerts. Like, I’m looking at it right now. See:<\/p>\n\n\n\n The problem is that all the major carriers have shut those gateways down<\/strong>. AT&T, Verizon, T-Mobile have all pulled the plug over the last couple of years. And also Cingular hasn’t existed since, like, the Paris Hilton era.<\/p>\n\n\n\n So if you followed Copeland’s documentation and entered your number in that This isn’t a Copeland thing. The carriers killed these gateways themselves. <\/strong>Officially, they did it because of spam; but also, there were some newer regulations around business-to-consumer text messaging that weren’t worth the hassle to them.<\/p>\n\n\n\n (It you really want to get deep into the weeds on the modern history of the telecommunications industry, the regulatory framework is called A2P 10DLC<\/a>. Essentially, carriers now require any automated texting to be registered and approved.)<\/p>\n\n\n\n Those regulations are a big reason why it’s tough to just fire up your own email-to-text replacement.<\/p>\n\n\n\n You’d need to register with the carriers, get a compliant phone number, set up an SMS API through something like Twilio<\/a>, and maintain that infrastructure yourself.<\/p>\n\n\n\n For a controller that just needs to send a handful of critical alerts, that’s a massive amount of overhead<\/strong>. (Even dedicated alarm notification software like Win-911<\/a> can be more complexity than you need for straightforward compressor alerts.)<\/p>\n\n\n\n That’s the gap that text.email fills. Instead of routing through dead carrier gateways or building your own SMS pipeline, you use the controller’s existing email capability (which still works perfectly) and let text.email handle the email-to-SMS conversion on the compliant side<\/strong>.<\/p>\n\n\n\n There is one other path that Copeland offers. They have their Connect+ \/ ProAct<\/strong> cloud monitoring platform, which handles alarm notifications at the mega enterprise level.<\/p>\n\n\n\n It’s built for chains managing hundreds of stores \u2014 and also priced for chains managing hundreds of stores. If that’s not your situation, the process we’ve described in this article will get you there with a whole lot less overhead.<\/p>\n\n\n\n Alright, alright. You’re ready to go. So what’s next?<\/p>\n\n\n\n Just follow the steps \u2014 and that means heading over to text.email<\/a> to sign up.<\/p>\n\n\n\n For a CoreSense setup, 200 messages included in the text.email plans really should be more than enough. You’re not trying to text every routine defrost cycle. And really, what matters is that the one compressor lockout or high-temp alarm<\/strong> that happens on a Saturday night actually reaches someone’s phone.<\/p>\n\n\n\n If you want to test it out, send a sample email to And then get rolling, because you really are just a few minutes away from having this whole system set up and working.<\/p>\n\n\n\n Your E3 or Site Supervisor can generate a lot of alarm traffic, and you definitely don’t want all of it hitting your phone. Here’s a starting point for splitting them. Your priorities will obviously vary, but here’s what I’d do if you hired me. (P.S. Do not hire me. I am not qualified.)<\/p>\n\n\n\n Route to text:<\/strong><\/p>\n\n\n\n Fine on email:<\/strong><\/p>\n\n\n\n The alarm priority system in your E3 or Site Supervisor makes this easy to set up.<\/p>\n\n\n\n In your Alarm Communications config, you can create separate communication groups: one for critical alarms routed to your text.email user, another for everything else routed to standard email recipients.<\/p>\n\n\n\n (Another note: If you’re also running Danfoss ADAP-KOOL controllers<\/a> alongside your Copeland equipment, the same approach works there too.)<\/em><\/p>\n\n\n\nStep 1: Sign up for text.email<\/h3>\n\n\n\n
yournumber@yourspecialkeyword.text.email<\/code>, and any email sent to that address gets delivered as an SMS to your phone.<\/p>\n\n\n\nStep 2: Open your Site Supervisor’s network settings and confirm SMTP is configured<\/h3>\n\n\n\n
<\/figure>\n\n\n\nStep 3: Add a user with your text.email address<\/h3>\n\n\n\n
yournumber@yourkeyword.text.email<\/code> address in the Email<\/strong> field. Now when the controller sends an alarm email to this address, text.email converts it and delivers it as an SMS to your phone.<\/p>\n\n\n\nStep 4: Set up Alarm Communications for that user<\/h3>\n\n\n\n
Why the Site Supervisor’s Built-In SMS Feature Stopped Working<\/h2>\n\n\n\n
5551234567@txt.att.net<\/code>, and AT&T would convert that email into a text message. Verizon had @vtext.com<\/code>, T-Mobile had @tmomail.net<\/code>.<\/p>\n\n\n\n<\/figure>\n\n\n\n@txt.att.net<\/code> format<\/a>, your texts just stopped arriving one day. The controller is still sending them. They’re just going nowhere.<\/p>\n\n\n\nSo what about building your own replacement?<\/h3>\n\n\n\n
Are those the only options?<\/h3>\n\n\n\n
CoreSense Text Alerts: Get Started Now<\/h2>\n\n\n\n
yournumber@text.email<\/code> and you’ll get the text in seconds. (You don’t need to sign up or anything to try that.)<\/p>\n\n\n\nWhat CoreSense Alerts Are Worth a Text (and What Can Stay on Email)<\/h2>\n\n\n\n
\n
\n
CoreSense Text Alerts: Wrap Up and Next Steps<\/h2>\n\n\n\n