A US SMS gateway that routes messages and tells you what happened

A gateway is the layer between your systems and the carriers, and it deserves a precise description rather than a marketing paragraph. You submit messages over a documented HTTP API or SMPP; the gateway converts them to carrier-facing traffic; it routes to the destination network; it tracks the message through intermediate states; and it returns a receipt when a message reaches its final state.

We do not sell routes, and we do not promise a specific carrier path per message. US messages are delivered to the network that owns the number, and what you actually buy is truthful delivery information: receipt delivery into your callback, published state and error codes, and retry behavior you can reason about. If a message is filtered or fails, you should be able to find out rather than pay for silence.

The gateway also carries the US-specific work that submission alone does not cover. Sender type, registration status, consent state and opt-out handling are all part of delivery in the United States.

Feature lists are easy to write and hard to verify, so judge a gateway on outcomes that affect your business. Deliverability is the first: registered senders, sensible sender hygiene and a focus on getting messages accepted rather than simply submitted. Compliance is the second: US A2P traffic requires registration, and the gateway you choose needs to be willing to push that work through rather than leave it to you.

Throughput matters for large volumes, and in the US it is tied to your 10DLC trust score, so ask how a provider handles registered traffic. Reporting is the third: per-message receipts, documented state and error codes, and a way to reconcile what you sent with what was delivered. Support is the fourth: when network behavior changes, you want an answer from people who know SMS rather than a ticket queue. Price is last, not least: US destinations are charged per message at a published rate, and the right question is what you get for it.

In the United States, the gateway cannot stop at routing. Application-to-person traffic from a 10-digit number must be carried on registered senders: a registered brand and campaign through The Campaign Registry, with a trust score that affects how carriers treat your traffic. Toll-free numbers must be verified before they can carry A2P messages, and unverified numbers have been blocked for A2P in the US and Canada since January 2024.

Sending over an unregistered number does not fail at submission; it fails quietly later, when carriers throttle or filter your traffic. That is why registration is part of the infrastructure conversation, not an optional form. WorldText provisions both sender types and works through the registrations with you. Our 10DLC page and toll-free SMS page explain the paths, and our compliance guide covers the rules that sit behind them.

Toll-free verification is free and usually completes within a few business days, so there is no cost reason to defer it.

US coverage through WorldText spans the major national networks plus a very long tail of regional carriers. Our coverage page lists US networks including AT&T, Verizon, T-Mobile and many regional operators, so you can check the specific destinations you actually send to.

Pricing is destination based and published. US destinations cost 8 credits per single-part message, and multipart messages are charged as multiple messages rather than one. Credits are sold in bundles denominated in GBP including VAT, with bundle pricing published on our pricing page from small starter packs up to 200,000-credit bundles. No per-carrier tables, no hidden surcharges: the rate you see is the rate that applies.

For scale, bundles start at 2,000 credits for 13.50 GBP and reach 200,000 credits for 998 GBP, all including VAT. Destination rates are the only per-message variable, published per country rather than per carrier, so the cost you plan is the cost that applies.

The two answers are not in competition, and the distinction is worth being honest about. If your own systems generate the messages, transaction triggers, alerts, one-time passwords or order updates, you need infrastructure: a documented API or SMPP, receipts, and control over encoding and senders. If you are running marketing campaigns with contact lists, segmentation, scheduling and deliverability analytics, you need a campaign platform, and that platform needs gateway infrastructure underneath it whether or not you think about it.

WorldText is the infrastructure layer: specialist SMS plumbing rather than a campaign tool. Teams that use a campaign platform for broadcasts increasingly keep operational messaging on dedicated infrastructure, because the traffic types have different requirements and different compliance profiles. If you are deciding which to buy, buy the outcome you need, and do not assume a campaign tool replaces a gateway for application messaging.

When you compare providers, compare receipts and error behavior rather than interface gloss; that is where the real difference shows up.