You saw it on a trip to London or Sydney: a text from your airline, and instead of a phone number the sender just read Qantas or BA. Clean. Branded. Instantly recognizable. So when you set up SMS for your own US business, you tried to do the same thing — set the sender name to ACME — and either the platform quietly ignored it and used a number, or the message never landed at all.
That's not a bug in your setup. Alphanumeric sender IDs are a real, widely-used feature in most of the world. They just aren't supported for two-way application-to-person (A2P) messaging in the United States. Full disclosure: I work for Ready, an SMS platform, so I provision the numbers we're about to talk about — but the constraint itself is a carrier-network fact, not a vendor limitation. No US provider can hand you a branded text sender for a normal two-way campaign, because the US networks don't route it.
What an alphanumeric sender ID actually is
An alphanumeric sender ID is a "from" field that's letters instead of a phone number — up to 11 characters, no spaces, like ACMEBANK or FedEx. In much of Europe, Asia, the Middle East, and Australia, businesses register these with local carriers and send from them at scale.
There's one catch that matters even where they are supported: alphanumeric senders are one-way only. There's no phone number underneath, so the recipient can't reply. That's fine for a one-time password or a "your package shipped" alert. It's useless for anything conversational — which is exactly the kind of two-way messaging most US businesses actually want.
Why the US doesn't allow it for A2P
The short version: the US carrier ecosystem standardized on a different trust model. Instead of registering a name, US A2P messaging registers a brand and a campaign tied to a real routable number under the 10DLC framework (10-digit long code). The carriers built their filtering, throughput, and accountability system around numbers, not name strings.
A few reasons alphanumeric senders never took hold domestically:
- No reply path. US consumers expect to text back — for support, for STOP, for a quick "yes." A name-only sender can't receive that reply, and carriers won't route STOP handling to a dead sender.
- Spoofing history. Letter-based senders are trivially impersonated. A bank sender named
CHASEis a phishing gift. US carriers chose registered numbers with a documented brand behind them instead. - The 10DLC framework already solves the trust problem. Rather than vetting name strings, US carriers vet the business — that's what brand and campaign registration is. If you want to understand that machinery, we wrote a full operator-grade 10DLC guide.
So when a US platform "accepts" an alphanumeric sender ID in a form field, one of two things happens: it silently substitutes a number, or it tries to send and the carrier drops it. Neither is what you configured.
The one exception: toll-free and shortcodes carry some brand weight
There are two US paths that get closer to a recognizable sender, though neither is a name.
Verified toll-free numbers (the 8XX numbers) are routable, support two-way, and once verified carry decent trust. Recipients don't see your brand name, but a consistent toll-free number becomes recognizable over time — and some devices display a verified-sender indicator. The tradeoff is that verification takes longer and caps throughput; we compared the two paths in toll-free verification vs 10DLC.
Shortcodes (5-6 digit numbers like 74757) are the closest thing to a "branded" sender the US offers, and big retailers use them. But they run four figures a month in leasing plus a multi-week provisioning process. For a nonprofit or local business that's overkill — a 10DLC keyword does the same job for pennies.
How to build brand recognition without a name in the "from" field
You can't put ACME in the sender slot. You can make every text unmistakably yours. Here's what actually works:
- Brand the first line of the message body. Lead with your name:
ACME: Your order #4021 shipped —. This is the single highest-leverage move. The recipient sees who it's from before they read a word of the offer, and it's what carriers expect for identification anyway.
- Use one consistent number per brand. Don't rotate. When the same 10DLC number texts a customer repeatedly, their phone starts associating it with you — many devices will even auto-suggest saving it as a contact. If you're sharing a number with 200 other businesses through a pooled reseller, that recognition never builds, and their spam complaints drag your delivery down too. Here's what a dedicated number actually costs vs shared.
- Keep a stable sending identity per use case. Send 2FA codes and promo blasts from separate numbers, but keep each number consistent for its job. Mixing them gets both filtered — the transactional/marketing split most SaaS teams skip.
- Register the right campaign use case. Brand recognition dies fast if your texts get throttled or filtered. Matching your registered use case to what you actually send keeps delivery healthy.
A quick comparison of your real options
| Option | Branded sender? | Two-way? | Speed to live | Rough cost | Best for |
|---|---|---|---|---|---|
| Alphanumeric sender ID | Yes (a name) | No | N/A in US | N/A | Not available for US A2P |
| 10DLC long code | No — number + body branding | Yes | Often same-day | ~$10/mo brand + ~$20/mo campaign carrier fees | Most US senders |
| Verified toll-free | No — consistent 8XX number | Yes | Weeks | Verification + per-msg | Senders who want higher trust, slower is OK |
| Shortcode | Closest to branded | Yes | Multi-week | Four figures/mo | High-volume retail/enterprise |
For the overwhelming majority of US businesses, the second row is the answer: a registered 10DLC number with your brand baked into the message body.
Where Ready fits
If you came in expecting a named sender and just learned you can't have one, the practical next step is getting a clean, dedicated 10DLC number registered so your body-line branding has a trustworthy number under it. Ready handles the full A2P 10DLC path in-app — brand plus campaign registration, roughly ~$10/mo per brand and ~$20/mo per campaign in carrier fees, with approvals typically landing in 1–3 days and often same-day.
On pricing, outbound runs $0.02/segment on Standard (0–50,000/month), plus the $0.0045/segment carrier pass-through we bill separately so your invoice stays legible. Past 50,000 segments in a month the rate drops to $0.016 automatically — no plan to pick. And STOP handling, quiet-hours enforcement, and consent capture are built in, which matters because your consistent branded number is only an asset if it stays deliverable. You get 2,500 free credits to try it, no card required, at app.tryready.com/signup.
The practical takeaway
The FROM: ACME sender you saw abroad is a real feature — it's just a different network's feature, and it's one-way even where it exists. US A2P messaging trades name-based senders for number-based trust through 10DLC. That's not a downgrade so much as a different bargain: you give up the letters in the header and gain a two-way, reply-capable, STOP-honoring channel.
Build the recognition you wanted by branding your first line, keeping one consistent number per use case, and registering the campaign correctly. Do that and your customers will know exactly who's texting — number or not. If you want the full mechanics before you register, the 10DLC compliance guide is the place to start.