Move Your Alerts Off the Rogers Gateway

Emails addressed to a Rogers number no longer turn into texts, because Rogers Communications (Canada) has shut down its email-to-text gateway for good (10-digit number@pcs.rogers.com). If an alarm panel, monitoring tool, library system (ILS) or on-call pager still points there, swap that one address for +1[PhoneNumber]@sendemailtotext.com with TextBolt. The email itself stays the same.
A new facilities manager inherits a building and the installer’s handover binder. Under “SMS notifications” there is one line: the on-call phone number, followed by @pcs.rogers.com. Nothing in the binder says that route stopped carrying texts around mid-2023. Nothing on the panel will tell you either.
This blog guide covers what Rogers changed, which addresses are dead, how the replacement options compare, and how to swap the address in the system you actually run.
Rogers ran a free gateway that turned an email into an SMS. You sent mail to a subscriber’s 10-digit number at a Rogers domain, and the carrier delivered it as a text. That gateway is gone. Its main users were automated systems: alarm panels, server monitors, scripts and notification tools, not people at a keyboard.
The format was always 10digitphonenumber@pcs.rogers.com. In its early years, recipients had to reply “read” or “block” before messages would come through. According to comments on ruk.ca,Rogers started charging an extra $5 a month for “Direct Delivery” from July 1, 2005. The gateway was never a guaranteed business channel. It was a carrier convenience that system senders came to depend on whenever they used email to SMS Rogers phones.
A retired carrier gateway often accepts or drops the email without returning an error. The sending system therefore logs success, and nobody finds out until an alert is missed. Use these steps to find out whether a route is dead:
Leaving pcs.rogers.com behind doesn’t end the need to verify. The sendemailtotext.com route shows delivery status in its dashboard, but it won’t resend a failed message or warn you that a recipient’s number is blocked. Check the dashboard instead of trusting the system log.
Find Out Whether Your Alerts Still Arrive
TextBolt shows the delivery status of every text in its dashboard, so a dead route shows up on the first test send.
There are several replacement paths. Most are paid SMS gateways or providers, and the others are app push notifications and email-to-voice calls. The table compares the replacement categories on the questions that matter to system senders.
| Option | Code or SDK required | Works from an existing email workflow | Replies thread to the sender’s inbox | Registered business sender | What changes in your system |
| TextBolt (email to SMS gateway) | No | Yes | Yes, two-way | Yes | The destination address |
| App push notifications | An app on every recipient’s phone | Depends on the app | No, not SMS | Not applicable (not SMS) | Alert destination, plus an app install per recipient |
| Multi-channel SMS platforms with email-to-SMS (e.g., ClickSend, Textmagic) | Not for the email-to-SMS feature | Yes, through the email-to-SMS feature | Varies by vendor | Through the provider | Destination address and account setup per the vendor |
| Programmatic SMS APIs (e.g., Twilio) | Yes | No | Only through a reply handler you build | Through the provider | Code that calls the API |
| Email-to-voice call alerts | No | Yes | No, calls rather than texts | Not applicable (not SMS) | The destination address |
If your alerts used to go to pcs.rogers.com, TextBolt email to text gateway takes over the carrier gateway’s job at the address level. Your team edits one destination email instead of building an SMS API integration.
Alarm panels, monitoring tools and IoT sensors keep emailing exactly as they did, and the messages land on a phone as texts. Staff can also text from their inbox and get replies threaded back.
With TextBolt, the swap is one line per recipient.
Before: alerts@yourserver.com → 10-digit number@pcs.rogers.com
After: alerts@yourserver.com → +1[PhoneNumber]@sendemailtotext.com
TextBolt accepts mail at the new address over ordinary SMTP, and the subject line and body become the text the recipient sees. No code changes on the system that sends the alert. It handles 10DLC registration for your account, and approval can take up to 48 hours. Here are the following steps to migrate to TextBolt:
Alarm panels and their email add-on modules store the text recipient in a notification address field. EyezOn and Envisalerts setups work the same way. Replace the pcs.rogers.com entry with the recipient’s sendemailtotext.com address. Then trigger a test event from the panel, not a test email from a laptop.
These tools send alerts to email contacts, so the old gateway address usually lives in a contact or notification-channel setting. Swap it there, the same way the Datadog email to text alerts setup does. Shift handovers then become an address change rather than a redeploy.
Koha needs three settings changed. Point the SMS cellular provider domain at sendemailtotext.com instead of the Rogers domain, set SMSSendDriver to Email, and enable EnhancedMessagingPreferences. Notices go out unchanged, just to a new destination. For other platforms, see fixing library ILS text notices.
Supervisors can send scheduled check-in texts from Gmail to text or Outlook by addressing them to +1[PhoneNumber]@sendemailtotext.com. Replies come back to the same inbox as timestamped emails for the safety file. The gateway moves the message but does not watch the clock, so the missed check-in rule stays in your safety procedure.
Threshold alerts from CloudWatch, a custom webhook that emails out, or the Grafana email to text alerts route can point at the same sendemailtotext.com address format. Change the email destination in the alert rule and fire a test threshold breach to confirm it arrives.
Yes. Carriers on both sides of the border have retired or scheduled the end of the same kind of gateway:
Rogers was early, but it was not alone. Any alert route that still depends on a free carrier gateway should be treated as temporary.
Every alert still pointed at pcs.rogers.com is a missed alarm, a server left down overnight, or a hold notice a patron never sees. The system logs success, so nobody learns about it until something has already gone wrong.
TextBolt replaces that gateway at the address level. Your panels, monitors and library system keep sending the same emails, and they arrive as texts on a registered business number with replies threaded back to the sender’s inbox. The email to SMS guide covers how the service works end to end.
Start small. Sign up, allow up to 48 hours for 10DLC approval, and swap one recipient for the first test send. Move the rest of the list once the dashboard shows it delivered.
Your next step: start a free trial, then point one alert at +1[PhoneNumber]@sendemailtotext.com and watch the dashboard confirm it.
With legacy carrier gateways, yes. You needed a carrier-specific domain such as vtext.com for Verizon or txt.att.net for AT&T. With TextBolt the domain stays the same for every recipient and only the phone number changes. Rogers, Fido and Chatr numbers are covered, since TextBolt sends across the US and Canada.
Replace the pcs.rogers.com entry in your system’s notification field with +1[PhoneNumber]@sendemailtotext.com, and add the system’s sending address to your TextBolt account. The edit takes a few minutes. Sending starts once 10DLC approval completes, which takes up to 48 hours.
Swap a single recipient’s address first rather than the whole on-call list, and point it at a phone you control. Fire the system’s own test event, confirm delivery status in the dashboard, and only then replace the remaining addresses. The recurring test on the maintenance checklist covers the rest.