What Is an SMS Gateway? Definition, How It Works, and Common Uses

HomeBlogWhat Is an SMS Gateway
What Is an SMS Gateway

An SMS gateway is a tool like TextBolt that lets computers, software applications, and business systems send and receive text messages over mobile phone networks without a cell phone in hand. It works by translating a message from your application into a format cellular networks can read, then routing it to the correct mobile carrier for delivery to the recipient’s phone, and returning a delivery status. Businesses use SMS gateways most often for two-factor authentication codes, automated alerts and reminders, and consented bulk messaging.

How An SMS Gateway Works

An SMS gateway sits between your software and the mobile carriers and handles four jobs. Here they are, in order:

  • Translates: It converts the message your application produces into a format cellular carrier networks can read and deliver.
  • Routes: It sends the message to the correct mobile carrier for the recipient’s number.
  • Delivers: The carrier hands the text off to the recipient’s phone over the mobile network.
  • Reports status: It returns whether the message was accepted, delivered, or failed. That status shows up in the dashboard; a failed message is not automatically retried and there is no alert when a recipient number is blocked you read the outcome, you don’t assume it.

The same translate-route-deliver chain runs regardless of whether an API call or an ordinary email hands the message in email in, text out, no cell phone required.

Common Uses for an SMS Gateway for Businesses

Businesses reach for an SMS gateway when a message has to land on a phone and a person has to see it fast. The three most common uses:

  • Two-Factor Authentication (2FA) and One-Time Passwords (OTP): Sending short-lived security codes to verify a login or a transaction.
  • Automated alerts and reminders: Appointment reminders and booking confirmations, delivery and shipping updates, and on-call paging, alarm-panel and IoT sensor alerts routed straight to an engineer’s phone.
  • Two way replies threaded back to the sender: Consented customer follow-ups where the reply returns to the original sender’s inbox instead of a shared catch-all.

If your page turns to marketing texts, note the rule that governs all of them: US business texting runs on documented consent. Every account that sends application-to-person SMS in the US needs A2P 10DLC registration and see the 10DLC compliance guide for what that involves. This is not legal advice; it’s the baseline for delivery carriers will accept.

Email-to-SMS Gateway: The Drop-In Replacement for Retired Carrier Gateways

An email-to-SMS gateway is an SMS gateway that any system or team that can send an email can use you address an email to a phone number and the recipient gets a text. This is the part of the SMS gateway landscape that just changed, because the free carrier gateways that quietly powered it for years are being shut off.

For most of the last decade, sending a text from software meant emailing a carrier-specific address like +1XXXXXXXXXX@txt.att.net. That worked until the carrier retired the domain and when it did, every monitoring alert, hold notice, and appointment reminder pointed at it started failing silently.

Free Carrier GatewaysAT&T (incl. Cricket, FirstNet)VerizonT-Mobile (incl. legacy Sprint) 
Gateway domain(s)txt.att.net / mms.att.net (Cricket: sms.cricketwireless.net / mms.cricketwireless.net)vtext.com / vzwpix.comtmomail.net / messaging.sprintpcs.com
StatusPermanently shut downShutdown in progress, some senders already losing accessFailing, with DNS errors and heavy spam filtering. T-Mobile calls it a legacy system that may be decommissioned
Effective/scheduled dateJune 17, 2025Full shutdown by March 31, 2027Failures since November 2024, complete DNS failure reported December 14, 2024. No official shutdown date
Official sourceAT&T SupportVerizon SupportT-Mobile email-to-text status

How TextBolt’s Email-to-SMS Gateway Works

Every TextBolt account gets one inbound address shaped like +1[Phone Number]@sendemailtotext.com; a message emailed there over SMTP turns its subject and body into the text, and any reply lands back in the original sender’s inbox one path used both directions.

You don’t guess at carriers. Where the old method needed a different domain for AT&T, Verizon, T-Mobile and the rest, TextBolt uses one destination address per recipient and delivers carrier-agnostically across major US and Canadian carriers. The substitution is one-for-one: a former AT&T sender swaps +1[Phone Number]@txt.att.net for +1[Phone Number]@sendemailtotext.com, and a former Cricket sender swaps +1[Phone Number]@sms.cricketwireless.net the same way, without any code change, SDK or system installation.

This is the drop-in migration path for teams whose ILS, monitoring stack, or scheduling tool still emails a dead carrier gateway. For libraries, that means setting Koha’s SMSSendDriver to Email and the provider domain to `sendemailtotext.com’ and more on that setup in the guide to library text notifications.

Move Your Alerts Off a Retired Carrier Gateway

See how TextBolt gets your alerts back on phones with one address change. No API build needed.

Email-to-SMS Gateway vs. SMS API

Both send text over mobile networks. They differ in what your team has to build and operate.

FeatureEmail-to-SMS gateway (TextBolt)SMS API 
SetupChange a destination email address, then wait up to 48 hours for 10DLC approvalBuild and maintain an integration
Code requiredNone. If a system can send email, it worksSDK, endpoints, and ongoing maintenance
Inbound repliesThread back to the sender’s inboxYou host and secure a webhook receiver
Address per recipient+1[Phone Number]@sendemailtotext.comHandled in code
Right fitAlerts, reminders, low-to-mid volume operational textingHigh-volume, deeply custom applications

Twilio, for example, competes on programmatic SMS and as a strong tool for custom builds with the lowest raw per-message pricing (Twilio Flex, $1 per active user/hour on the vendor’s own pricing page as of Sep 2026). The gateway approach differs: no SDK, no API contract, and no developer needed to send an email, and replies route back to the email inbox that sent them. Pick the email to SMS gateway when the message matters more than the machinery or pick the API when you’re building something the machinery has to serve.

If you want the mechanism itself broken down step by step, the deeper walkthrough lives in what email-to-SMS is and how it works, and the channel tradeoffs are covered in the comparison of email versus text message.

Why Teams Route SMS Through TextBolt

For an SMS gateway specifically, TextBolt swaps in wherever a retired carrier address (txt.att.net, vtext.com, tmomail.net) used to sit and skips the build an SMS API demands. It carries texts across major US and Canadian carriers with no code, threads replies into the inbox that sent them, and registers as a Verified A2P 10DLC sender so every message stays searchable and auditable. Used by 3,000+ teams and moving 2.4M+ texts last month, plans open at $29/month with 500 credits, no per-message fee, and a 7-day free trial.

TextBolt delivers your texts, but it doesn’t monitor your systems or retry failed sends. The dashboard shows each message’s status, so your team can follow up when something doesn’t go through.

Swap Your Old Gateway Address for TextBolt Today

Keep your alerts reaching phones with TextBolt, and see every message’s delivery status in one dashboard.

Frequently Asked Questions

Why would someone use SMS messaging?

Businesses use SMS when a message needs to be seen quickly. Texts land on the phone and tend to get read sooner than email, which can sit unopened for hours. Common uses include one-time passcodes, alerts and reminders, and two-way conversations with customers or staff.

Does Verizon have an email-to-SMS gateway?

It does, but it’s being retired. Verizon has started shutting down its vtext.com and vzwpix.com gateways and expects to finish by March 31, 2027. Some senders are already losing access before then. Businesses that still rely on these addresses should move to a registered email-to-SMS service.

How do I build an SMS gateway?

Building your own SMS gateway means creating an integration with an SMS provider, including API endpoints and a secure webhook for inbound replies. That suits high-volume, custom applications. If you only need alerts or reminders, an email-to-SMS gateway works without code. You change a destination address instead.

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.