Swap One Address and Start Texting Your Bell Alerts Again

Bell email to SMS, the service Bell called Text via Email, shut down on December 31, 2025. Emails sent to a Bell number at txt.bell.ca, txt.bellmobility.ca, or txt.bellmobilite.ca now fail and never arrive as texts.
Bell tied the shutdown to spam and smishing abuse. Businesses that used the gateway for automated alerts now need a commercial email to text service or app-based notifications instead.
Here is how the shutdown shows up in practice. At 2 a.m. a disk fills on a production server. Your monitoring tool emails the on-call engineer’s Bell number at txt.bell.ca and records the alert as sent. The phone never lights up.
This guide covers what Bell changed, why, the options that replace it, and the exact email to text address swap that gets system senders texting again.
Bell Mobility’s Text via Email service no longer turns an email into a text message on a Bell phone. It ended on December 31, 2025, as confirmed in the Bell Community Forum announcement.
Bell retired three email-to-text domains on the same date:
Bell email to text shut down because the gateway was being abused to send spam and smishing texts to Bell customers. Bell’s FAQ also gives cost and technology reasons.
Bell’s shutdown follows the same move by the major US carriers, which have retired or are retiring their free email-to-text gateways. If your systems ever addressed texts by carrier domain, expect more than one of them to be dead.
| Carrier | Gateway domain(s) | Status | Date | Source |
|---|---|---|---|---|
| Bell | txt.bell.ca, txt.bellmobility.ca, txt.bellmobilite.ca | Shut down | December 31, 2025 | Bell end-of-life FAQ |
| AT&T | txt.att.net | Shut down | June 17, 2025 | AT&T support article |
| T-Mobile | tmomail.net | Reported stopped; no official notice | Not announced | User reports only |
| Verizon | vtext.com, vzwpix.com | Shutting down | By March 31, 2027 | Verizon support page |
Bell email to SMS can be replaced in a few ways. A third-party email-to-SMS gateway keeps the email your systems already send. The short code and Salesforce routes Bell names suit mass messaging.
A programmatic SMS API fits teams with developers. App push notifications work only if every recipient already uses your app.
| Feature | Retired Bell gateway | TextBolt | Custom SMS API build | App push |
|---|---|---|---|---|
| Change to your existing system | None possible; messages now fail | Replace the recipient address | Developer integration project | Build or adopt an app |
| Two-way replies to the sender’s inbox | Service ended | Yes, threaded to the original sender | Only if you build an inbound handler | Replies stay inside the app |
| Delivery status visible | Service ended | Yes, in the TextBolt dashboard | Depends on what you build | Depends on the app |
| Registered business sending | Service ended | Yes, verified A2P 10DLC sender; texts US and Canadian numbers | 10DLC registration required for US business texting | Not applicable (not SMS) |
| Works on any phone without an app | Bell numbers only; ended | Yes, arrives as a text | Yes | No, the app must be installed |
TextBolt is the replacement for system senders and inbox teams that want to keep sending the email they already send. If your system can send an email, change one recipient address and it can still text a phone. There is no SDK, code, or integration project involved.
Bell’s notice points to organizations that send in volume to Short Code Messaging Providers, and it names Cisco Webex CPaaS and Sinch.
Bell’s notice also lists Salesforce Marketing Cloud, implemented through the partner CloudKettle, as a route for mass messaging.
Twilio is built for teams that want to write their own messaging logic against an API and pay per message.
App push notifications replace Bell’s email-to-text path only when every recipient runs your mobile app.
Walk Through Your txt.bell.ca Swap on a Demo Call
TextBolt replaces each Bell gateway address with one sendemailtotext.com address your systems can already email.
Moving system senders off Bell’s retired domains means finding every Bell gateway address in your alert configurations, replacing it, and then proving each text actually arrives. Until you do, an alert that “sent” is not an alert that landed.
An alerting system only knows that it handed an email to a mail server. It cannot see what happens at Bell. Dispatch-alert vendors have told their customers the same thing. Messages reach the carrier, and the carrier stops delivering them. Your logs look clean while the on-call phone stays silent.
We have moved 200+ enterprise customers, including FedEx and GE Aerospace, off Verizon’s email-to-text gateway, and that switch typically takes about 30 minutes per system. The Bell migration is the same mechanic.
Move Your First Bell Alert to TextBolt in One Address Change
TextBolt shows delivery status in its dashboard, so you can confirm your test sent reached the phone.
Replacing Bell email to text works the same way in every use case. The system keeps sending its email, and only the destination changes. What differs is where the recipient field lives.
On-call teams that paged Bell phones through txt.bell.ca can point the same alert email at the new sendemailtotext.com address.
Facility teams whose alarm panels texted Bell numbers can replace the Bell address in the panel’s notification recipient field.
Libraries whose integrated library system (ILS) sent hold and overdue notices to Bell patrons through txt.bell.ca can keep the same notice email and change the delivery domain.
Safety managers who sent scheduled check-ins to Bell phones by email can run the same lone-worker check-in texts through the new address.
Phone systems that emailed voicemail notices to a Bell number at txt.bell.ca can send them to the sendemailtotext.com address instead. RingCentral, 8×8, Zoom Phone, Allworx, and 3CX all support voicemail-to-email, and the voicemail-to-SMS guide covers the setting in each.
Sales, support, and front-desk staff who texted customers with a Bell number through the gateway can text from Gmail, Outlook, or any email client by typing the number into the To field.
Every system still pointed at txt.bell.ca keeps failing in silence. The monitoring tool logs the alert as sent, the on-call phone stays dark, and the patron never hears a hold is ready. Nothing in your logs flags it, so the gap stays open until someone misses something important.
TextBolt replaces Bell email to SMS with one change. Your systems keep sending the same email, and only the address changes to +1[PhoneNumber]@sendemailtotext.com. Replies return to the sender’s inbox, and delivery status shows in the dashboard. The same swap fixes any system still using Verizon email to text.
Start with one sender, the system whose missed alert would hurt most. Account setup takes approx 30 minutes, and 10DLC approval for a US account can take up to 48 hours before the first text. Failed messages are not retried, so check the dashboard after each test.
Your next step is to start a TextBolt account and point that first alert at the new address. Once approval clears, the alert that used to vanish lands on the phone it was meant for.
No. Bell has not published a new gateway domain. Its FAQ points mass-messaging senders to short code providers and Salesforce Marketing Cloud, which are new sending programs rather than a drop-in address swap.
No. Every email to text Bell gateway address stopped converting messages on December 31, 2025. Email sent to one is not delivered as a text, and Bell has not published a replacement domain.
Yes. TextBolt uses a single destination format for every recipient, so you no longer need to know which carrier a number belongs to. Delivery status for each message shows in the dashboard.
Account setup takes approx 30 minutes, and 10DLC approval takes up to 48 hours before the first text sends. The address swap in each system takes a few minutes once approval is done.