An SMS gateway is the system that sits between a business application and mobile carrier networks so that software can send and receive text messages. Your application hands the gateway a phone number and a message through an API or another interface; the gateway formats it for the messaging network, passes it toward the recipient’s carrier and reports back on what happened. Replies travel the other way. Most businesses use an SMS gateway as a service from a messaging or communications platform provider instead of building one.
At a glance
- An SMS gateway connects software to carrier text messaging, in both directions.
- Applications usually reach it through an HTTPS API; many providers also support SMPP for higher volumes.
- Most gateways reach carriers through SMS aggregators or direct carrier connections, depending on the provider and country.
- Delivery depends on carrier rules, registration and routing, so delivery rates and coverage vary by provider and region.
- Replies and delivery reports often come back to your system as webhooks.
What problem it solves
Mobile carriers built text messaging for phones, not for business software. A scheduling system, an e-commerce platform or a monitoring tool cannot send a text on its own. It needs something that speaks the carriers’ messaging protocols, holds the right connections and handles the details of message formatting, character encoding, long-message splitting and status reporting.
An SMS gateway does that translation. It lets a development team send a reminder, an alert or a one-time code with a simple API call, and receive customer replies as data the application can act on. For a buyer, the gateway is also where practical questions show up: which number types you can send from, how messages are routed, how much each message costs and how you find out why one failed.
How it works
Accepting messages. Your application sends a request to the gateway with the destination number, the sending number or sender ID, and the message text. Most gateways accept requests over HTTPS. Many also offer SMPP (Short Message Peer-to-Peer), a protocol designed for sustained, higher-volume traffic, and some accept email-to-SMS for simple use cases.
Preparing the message. The gateway checks the request, chooses a character encoding and splits long messages into segments. SMS segments hold up to 160 standard characters, or fewer if the message uses emoji or many non-Latin scripts, and business texting is usually billed per segment. Some gateways also handle MMS for images and media.
Routing. The gateway passes the message toward the recipient’s carrier. Depending on the provider and country, that happens through direct carrier connections or through one or more SMS aggregators that hold carrier connections on the gateway’s behalf. Routes differ in cost, reliability and whether they are approved by the receiving carrier.
Carrier rules. Carriers treat messages from software as application-to-person (A2P) messaging and apply their own rules. In the US, sending from ordinary local numbers generally requires 10DLC registration, toll-free numbers need verification, and short codes have their own approval process. Other countries set their own sender and content rules. The gateway provider usually helps with registration, but approval depends on your business and use case.
Status and replies. The gateway reports what happened to each message, such as accepted, sent, delivered or failed. Delivery receipts come from downstream networks, and what “delivered” confirms varies by carrier and country. Inbound replies arrive at the gateway and are passed to your application, often as a webhook that posts the message to an address you specify.
For buying guidance on messaging platforms, see our communications platform as a service solution page.
When it matters for buyers
- Adding texting to an application. If a product or internal process needs to send alerts, reminders or codes, it needs a gateway, usually bought as part of a CPaaS platform.
- Volumes are growing. Per-segment pricing, carrier pass-through fees and throughput limits start to matter at scale.
- Messages are being filtered. Delivery problems often trace back to registration status, sender reputation or the routes a provider uses.
- Expanding to new countries. Coverage, sender rules and rates differ by destination, and gateway providers differ in where they connect directly.
- Replacing a home-grown setup. SIM-based devices or old email-to-SMS scripts may not meet carrier rules for business traffic.
Questions to ask vendors
- Which interfaces do you support (HTTPS API, SMPP, email-to-SMS), and are there limits on each?
- How do you route messages to our main destination countries, and where do you rely on third-party aggregators?
- What does a “delivered” status actually confirm, and how quickly do delivery reports arrive?
- How do you help with 10DLC, toll-free verification and short code applications?
- What are your per-segment rates, and which carrier and registration fees are passed through?
- What throughput limits apply to each number type, and how are messages queued when we exceed them?
- How are inbound replies, STOP requests and HELP requests delivered to our systems?
How it differs from an SMS aggregator
An SMS gateway is the entry point your application talks to: it accepts messages, formats them and reports status. An SMS aggregator is a wholesale intermediary that holds connections to many carriers and carries messages between gateways or platforms and those carriers. Many CPaaS providers run their own gateway and buy delivery from aggregators; some large providers also act as aggregators themselves. When you compare providers, ask about both layers, because two services with similar APIs can use very different routes underneath.