The Sender ID — also called the originator, header or from-address — is the name or number recipients see when your SMS arrives. It looks like a small detail, but it is one of the most regulated parts of international messaging. The same message can be delivered flawlessly in one country and blocked or rewritten in another purely because of the sender field.
The three main Sender ID types
1. Alphanumeric Sender ID
An alphanumeric originator is a short text string, usually up to 11 characters (GSM 7-bit), such as ACMEBANK or SHOPALERT. It is the most brand-friendly option and is standard for notifications, marketing and one-time passwords in many markets.
Its main limitation is that it is one-way. A recipient cannot reply to an alphanumeric header, so it is unsuitable for conversational flows or support threads. Spaces, accented characters and some punctuation may be stripped or cause rejection depending on the operator, so most senders stick to A–Z, 0–9 and occasionally a hyphen or dot.
2. Numeric Sender ID (long number)
A numeric originator is a phone number in international format. It supports replies, which makes it the natural choice for two-way messaging, appointment confirmations with a "YES/NO" answer, or customer service. Numeric headers are also the fallback in countries where alphanumeric IDs are restricted or must be registered.
The trade-off: recipients see an unfamiliar number rather than your brand, which can slightly reduce open and trust rates for promotional traffic.
3. Short codes and service numbers
Short codes are country-specific numeric addresses, typically 3–6 digits, leased through local operators or aggregators. They offer high throughput and strong deliverability but are national in scope, require an approval process and carry recurring costs. They make sense for high-volume domestic programmes, not for global campaigns.
Why some Sender IDs get overwritten
If you send with a custom alphanumeric header and recipients see a random number or a generic word instead, your originator was overwritten. This normally happens for one of these reasons:
- The destination country requires Sender IDs to be pre-registered, and yours is not on the whitelist.
- Local regulation prohibits alphanumeric originators entirely for that traffic type.
- The route used does not support alphanumeric headers (common on grey or low-cost routes).
- The header contains unsupported characters or exceeds the length limit.
Overwriting is not always a delivery failure — the message may still arrive — but it breaks brand recognition and, for OTP traffic, can make legitimate codes look like phishing.
Country restrictions: the four broad categories
Regulations change frequently and differ per operator, so treat any list as a snapshot rather than a permanent rule. In practice, destinations fall into four groups:
- Open — dynamic alphanumeric Sender IDs are accepted without prior registration. Much of Western Europe historically works this way, although registration schemes keep expanding.
- Pre-registration required — you must submit the Sender ID, company documents and sometimes sample message content before traffic is allowed. Approval can take days or weeks.
- Alphanumeric not supported — messages are delivered from a numeric long number or short code only.
- Heavily regulated markets — local presence, local entity, content templates or explicit opt-in records may be mandatory, and marketing traffic may be separated from transactional traffic by law.
Because the rules are per-country and often per-operator, the only reliable approach is to confirm requirements for each destination before launching, rather than assuming a header that works in one market will work everywhere.
Sender IDs for OTP traffic
One-time password messages deserve extra care. Many operators apply stricter filtering to authentication traffic, and some markets require the sender name to match a registered brand or an approved template. A consistent, registered originator improves both delivery speed and user trust: people are trained to distrust verification codes that arrive from unknown numbers.
On UIPAPP, OTP traffic runs on priority routes with a template system and real-time delivery reports, and sender headers are configured together with support so they match what each destination market expects. Delivery status can also be pushed to your systems via webhook, which makes it easy to detect if a specific country starts failing after a regulatory change.
Practical checklist before you launch
- Keep alphanumeric headers under 11 characters and use plain A–Z / 0–9.
- Use a header that clearly maps to your brand — abbreviations that look random invite spam filtering.
- Separate transactional and promotional traffic; some regulators explicitly require it.
- Start Sender ID registration early in countries that need it; approval timelines are outside your control.
- Use a numeric originator where replies matter or where alphanumeric is not permitted.
- Monitor delivery reports per country, not just as a global average, so header-related issues surface quickly.
- Document which Sender ID is approved where, especially if you operate sub-accounts or resell messaging to clients.
Pricing and routing notes
Sender ID rules also affect cost indirectly. Registered routes and short codes generally carry different rates than plain international traffic, and pricing varies by country and operator. When comparing providers, ask specifically whether the quoted route supports your intended header type — a cheap route that overwrites your Sender ID is rarely cheap in practice.
Getting the originator right is unglamorous work, but it is what makes a message look legitimate at the exact moment a customer decides whether to trust it. If you are planning a multi-country rollout and are unsure which headers your destinations accept, it is worth checking the requirements market by market before the first campaign goes out.