Rogers Email-to-SMS Shutdown: pcs.rogers.com Replacement

HomeBlogRogers Email to SMS Alternative
Replace Rogers SMS Alerts With TextBolt

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.

What Happened to Rogers Email-to-Text?

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.

Key Details

  • Status: Rogers’ email-to-text gateway is discontinued. Mail sent to a Rogers number at that domain is no longer converted into a text.
  • Legacy domain: 10-digit number@pcs.rogers.com. The variant sms.rogers.com still appears in older gateway directories.
  • Timeline: Business and community reports place the end in 2023. Rogers has not published a shutdown notice, so treat any specific date as unconfirmed.
  • Affected brands: Fido (10-digit number@fido.ca) and Chatr numbers ran on the same Rogers infrastructure, and the same silent failures are reported on both brands.
  • Reason: Carriers retired free email-to-text gateways amid spam and phishing abuse and tighter rules on business messaging.
  • Impact: Automated alerts sent to these addresses fail silently, and the sending system usually gets no bounce.

What Was the Old Rogers Gateway, Historically?

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.

Why Don’t Alerts to pcs.rogers.com Bounce?

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:

  1. Send a test from the actual system. Use the alarm panel, monitor or ILS itself, not your desktop mail client. The route that matters is the one the system uses.
  2. Don’t wait for a bounce. A missing error message is not proof of delivery on a retired gateway.
  3. Check the sending log against the phone. “Sent” in the log but nothing on the handset means the route failed after the email left your server.
  4. Re-test on a schedule. Add a test send to the system’s maintenance checklist so a dead route shows up during a drill, not during an incident.

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.

What to Use Instead of Rogers Email-to-Text

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.

OptionCode or SDK requiredWorks from an existing email workflowReplies thread to the sender’s inboxRegistered business senderWhat changes in your system
TextBolt (email to SMS gateway)NoYesYes, two-wayYesThe destination address
App push notificationsAn app on every recipient’s phoneDepends on the appNo, not SMSNot 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 featureYes, through the email-to-SMS featureVaries by vendorThrough the providerDestination address and account setup per the vendor
Programmatic SMS APIs (e.g., Twilio)YesNoOnly through a reply handler you buildThrough the providerCode that calls the API
Email-to-voice call alertsNoYesNo, calls rather than textsNot applicable (not SMS)The destination address

1. TextBolt: Email-to-Text Replacement for System Senders

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.

  • What it is: A gateway that converts email to SMS. Put +1[PhoneNumber]@sendemailtotext.com where the old Rogers address used to be, and each email arrives as a text.
  • Best fit: System senders that already send email, such as alarm panels, monitoring stacks, ILS notices, scheduled check-in texts and sensor alerts.
  • Strengths: The only change is one destination address in your existing alert system, with no SDK, code or integration project. Replies are two-way and thread back to the original sender’s inbox. Staff can also send from Gmail, Outlook or any email client by typing a phone number into the To field.
  • Coverage and registration: TextBolt sends to US and Canadian numbers, including Rogers, Fido and Chatr lines. It handles 10DLC registration and compliance as a verified business sender, and sending starts once approval completes, which takes up to 48 hours.
  • Trade-offs: TextBolt does not run on-call schedules or escalation chains. Who gets paged, and what happens when nobody answers, stays in your monitoring tool or your written procedure.
  • Price: TextBolt pricing start at $29 a month for 500 message credits. Standard is $49 for 1,000 credits and adds team access for up to 10 people. Paying yearly takes 20% off, and a 7-day free trial is included.
  • Proof points: TextBolt is trusted by 3,000+ teams, carries 2.4M+ texts a month, and has 263,000+ installs on the Google Workspace Marketplace.

2. App Push Notifications (e.g., Pushover, ntfy)

  • What it is: Alerts delivered as notifications through an app installed on each recipient’s phone, instead of as SMS.
  • Best fit: Technical teams that control every recipient’s phone and can require the app.
  • Strengths: No carrier gateway sits in the delivery path.
  • Trade-offs: Every recipient must install the app and keep it signed in, which gets harder with contractors, shared devices or rotating staff.
  • Price: It varies by app. Pushover charges a one-time $4.99 per platform for individuals and $5 per user a month for teams, with 10,000 messages per user each month (Pushover pricing, as of October 2026).

3. ClickSend

  • What it is: A multi-channel messaging platform covering SMS, MMS, voice and physical mail, with email-to-SMS as one of its channels.
  • Best fit: High-volume and global senders who want several channels under one account.
  • Strengths: Email-to-SMS, MMS, voice and physical mail run from one account, which suits a team that sends more than text alerts.
  • Trade-offs: Email-to-SMS is one feature within a broader platform, so setup follows the wider account rather than a single alert address.
  • Price: Pay-as-you-go with no subscription. Top-ups start at $20, with volume discounts from $500 upward, and carrier fees apply on top of the per-message rate (ClickSend pricing, as of October 2026).

4. Twilio

  • What it is: A programmatic SMS API. Your application calls Twilio to send messages and handles replies in its own code.
  • Best fit: Custom builds with developers on staff who want full control over message logic.
  • Strengths: The API gives developers full control over message logic, retries and reply handling.
  • Trade-offs: It needs code, a developer, and an inbound handler for replies. An alarm panel or ILS that can only send email cannot use it directly.
  • Price: Sending to a Canadian long code is $0.0083 per message segment, plus a per-carrier fee that runs $0.0084 for Rogers and Fido numbers and $0.0087 for Bell and Virgin (Twilio Canada SMS pricing, as of October 2026).

5. Textmagic

  • What it is: An email-to-SMS service inside a broader texting suite that includes shared inboxes, automation and apps.
  • Best fit: Irregular senders who prefer prepaid credits that do not expire.
  • Strengths: A shared inbox and automation sit in the same account if the team later wants more than an alert route.
  • Trade-offs: It is a full texting suite, so a team that needs one alert route will use a small part of it.
  • Price: Pay-as-you-go outbound SMS is $0.049 per 160-character text, credit bundles start at 20, and credit never expires. Discounted subscription rates are offered in Canada but not published (Textmagic pricing, as of October 2026).

How Do You Replace pcs.rogers.com in Your Alerting System?

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:

  1. Add the sending address to your TextBolt account. The gateway only converts email from addresses registered on the account, so add the system’s own address (the alerts@yourserver.com in the example above) as a user first.
  2. Replace each one with that recipient’s TextBolt address, +1[PhoneNumber]@sendemailtotext.com.
  3. Send a test from the system itself, then confirm the delivery status in the TextBolt dashboard.

Replacing Alerts From a Specific System?

Alarm Panels (Honeywell, ADT, DSC, Bosch)

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.

IT and On-Call Monitoring (PagerDuty, Opsgenie, Datadog, Nagios, UptimeRobot)

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.

Library ILS Notices (Koha and Others)

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.

Lone-Worker Check-In Texts From Gmail and Outlook

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.

IoT and Sensor Alerts (AWS CloudWatch, Grafana)

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.

Is the Rogers Shutdown Part of a Wider Carrier Trend?

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.

What Does a Dead pcs.rogers.com Address Cost You?

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.

Frequently Asked Questions

Does the recipient’s mobile carrier matter?

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.

What is the fastest way to move an alert system off a carrier email-to-text gateway?

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.

How do we test the new setup without spamming our on-call team during business 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.

Written by
Rakesh Patel
Rakesh Patel
Founder and CEO of TextBolt
Rakesh Patel is an experienced technology professional and entrepreneur. As the founder of TextBolt, he brings years of knowledge in business messaging, software development, and communication tools. He specializes in creating simple, reliable solutions that help businesses send and manage text messages through email. Rakesh has a strong background in IT, product development, and business strategy. He has helped many companies improve the way they communicate with customers. In addition to his technical expertise, he is also a talented writer, having authored two books on Enterprise Mobility and Open311.