An SMS sender name, also called an Alphanumeric Sender ID, is the branded text that appears as the sender of your SMS messages in supported countries. For example, recipients may see YourStore instead of a phone number.
Continue reading to learn how to set up your SMS sender name, understand character and format limits, and see how it displays across different countries.
Before You Begin
SMS sender names in the United States and Canada. The United States and Canada do not support custom alphanumeric sender names. Omnisend uses a dedicated toll-free number instead. Learn how to verify your toll-free number in Omnisend.
Sender names cannot be edited per campaign or automation. They apply globally to all SMS messages.
Recipients cannot reply to an SMS sender name. An alphanumeric sender name identifies the sender, but it is not a phone number or a reply-enabled inbox.
Sender names are not supported everywhere. Depending on the country, your SMS message may show your sender name or code instead.
Set Up Your SMS Sender Name
In Omnisend, you can save an SMS sender name and automatically apply it to all your SMS campaigns and automations.
To set it up, go to Store settings → SMS → Sender's name, add your sender name, and click Save.
The SMS sender name cannot be edited in message settings. If you need to update it, you can change it back following the same steps.
Your sender name now applies to all SMS campaigns and automation workflows.
💡 Tip: If your brand name has spaces (e.g., "Joe's Bakery"), combine it into one word: JoesBakery.
⚠️ Important: Even if saved, sender names won't appear in SMS sent to countries where the feature is unsupported. In those cases, a phone number displays instead.
SMS Sender Name Limitations
Character Limit
Maximum: 11 characters (letters and numbers only).
Minimum: 3 characters (shorter names may not display on all devices).
This limit is set by SMS network standards and cannot be changed.
Allowed Characters
Uppercase and lowercase letters (A-Z, a-z).
Numbers (0-9).
No spaces, special characters, or emojis.
Cannot be numbers only (must include at least one letter).
Example:
✅ Valid: BellasShop, Acme2024
❌ Invalid:
Bella's Shop (space).
Bella🌸 (emoji).
12345 (numbers only).
No Direct Replies
Recipients cannot reply to your SMS sender name. Replies will bounce back and appear as "not sent."
💡 If you're sending to US customers and want to receive and respond to SMS replies, you can integrate Gorgias with Omnisend.
Country Restrictions
SMS sender name support varies by destination. Depending on the country and carrier, your sender name may appear as entered, be replaced with a number or generic sender, or require registration.
For detailed registration instructions, see SMS Sender ID Registration by Country.
Some destinations are unavailable for SMS and are not included in the table below.
Status meanings:
✅ Supported: The sender name is delivered as entered.
✅ Supported — registration required: The sender name is supported after registration.
⚠️ Partial — operator-dependent: Delivery depends on the mobile operator.
❌ Not supported: The sender name is replaced with a number, short code, long code, or generic sender.
💡 Tip: Use Ctrl+F (Cmd+F on Mac) to search for your country in the table below.
Country | Alphanumeric Sender ID | Notes |
Afghanistan | ✅ Supported - registration required |
|
Albania | ✅ Supported - registration required |
|
Algeria | ✅ Supported |
|
American Samoa | ❌ Not supported | Sender ID replaced with a short or long code |
Andorra | ✅ Supported |
|
Anguilla | ❌ Not supported (alphanumeric) | Toll-free number required |
Antigua & Barbuda | ❌ Not supported | Sender ID replaced with a short code or a random long code |
Argentina | ❌ Not supported | Sender ID replaced with a short code or a random long code |
Armenia | ✅ Supported - registration required |
|
Aruba | ❌ Not supported | Sender ID replaced with a short code or a random long code |
Australia | ✅ Supported - registration required | See the Australia SMS Sender ID requirements |
Austria | ✅ Supported - registration required | See the Austria SMS Sender ID requirements |
Azerbaijan | ✅ Supported |
|
Bahamas | ❌ Not supported | Sender ID replaced with a short or long code |
Bahrain | ✅ Supported |
|
Barbados | ❌ Not supported | Sender ID replaced with a short or long code |
Belarus | ✅ Supported - registration required |
|
Belgium | ❌ Not supported | Sender ID replaced with a numeric sender |
Belize | ❌ Not supported | Sender ID may be replaced with a local long code or short code |
Benin | ✅ Supported - registration required |
|
Bermuda | ✅ Supported |
|
Bhutan | ❌ Not supported | Replaced with the generic sender ID InfoSMS |
Bolivia | ✅ Supported |
|
Bosnia and Herzegovina | ✅ Supported - registration required |
|
Botswana | ✅ Supported |
|
Brazil | ❌ Not supported | Sender ID may be changed to a short code or local number |
British Virgin Islands | ❌ Not supported (alphanumeric) | Toll-free number required |
Brunei | ✅ Supported |
|
Bulgaria | ✅ Supported - registration required |
|
Burkina Faso | ✅ Supported |
|
Burundi | ❌ Not supported | May be replaced with a generic ID or random short code |
Cambodia | ✅ Supported |
|
Cameroon | ✅ Supported - registration required |
|
Canada | ❌ Not supported (alphanumeric) | Dedicated toll-free number required |
Cayman Islands | ✅ Supported |
|
Central African Republic | ✅ Supported |
|
Chad | ✅ Supported |
|
Chile | ❌ Not supported | Sender ID replaced with a random numeric sender |
Colombia | ❌ Not supported | Sender ID generally replaced with a short code or local number |
Comoros | ✅ Supported - registration required |
|
Congo (Democratic Republic of the Congo) | ✅ Supported - registration required |
|
Congo (Republic of the Congo) | ✅ Supported - registration required |
|
Cook Islands | ✅ Supported |
|
Costa Rica | ❌ Not supported | Replacement varies by operator |
Croatia | ⚠️ Partial - operator-dependent | Some operators may replace the sender with InfoSMS |
Cuba | ✅ Supported - registration required |
|
Cyprus | ✅ Supported |
|
Czech Republic | ⚠️ Partial - operator-dependent | Some operators replace the sender with InfoSMS or a short code |
Denmark | ✅ Supported |
|
Djibouti | ✅ Supported |
|
Dominica | ✅ Supported |
|
Dominican Republic | ⚠️ Partial - operator-dependent | Some operators replace the sender with a short code |
Ecuador | ❌ Not supported | Sender ID may be overwritten |
Egypt | ✅ Supported - registration required |
|
El Salvador | ❌ Not supported | Sender ID replaced with a short code or long code |
Equatorial Guinea | ✅ Supported |
|
Estonia | ✅ Supported |
|
Falkland Islands | ✅ Supported |
|
Faroe Islands | ✅ Supported |
|
Fiji | ✅ Supported |
|
Finland | ✅ Supported - registration required | See the Finland SMS Sender ID requirements |
France | ✅ Supported |
|
French Guiana | ✅ Supported |
|
French Polynesia | ✅ Supported |
|
Gabon | ✅ Supported |
|
Gambia | ✅ Supported |
|
Georgia | ✅ Supported |
|
Germany | ✅ Supported |
|
Ghana | ✅ Supported |
|
Gibraltar | ✅ Supported |
|
Greece | ✅ Supported |
|
Greenland | ✅ Supported |
|
Grenada | ✅ Supported |
|
Guadeloupe & Martinique | ✅ Supported |
|
Guam | ❌ Not supported | Only long codes are permitted |
Guatemala | ❌ Not supported | Sender ID may be replaced with a domestic long code or short code |
Guernsey | ✅ Supported |
|
Guinea | ✅ Supported |
|
Guinea-Bissau | ✅ Supported |
|
Guyana | ✅ Supported |
|
Haiti | ✅ Supported |
|
Honduras | ❌ Not supported | Sender ID may be replaced with a local long code or short code |
Hong Kong | ✅ Supported |
|
Hungary | ⚠️ Partial - operator-dependent | Some operators replace the sender with a local long code |
Iceland | ✅ Supported |
|
India | ❌ Not supported |
|
Indonesia | ✅ Supported - registration required |
|
Iran | ✅ Supported - registration required |
|
Iraq | ✅ Supported |
|
Ireland | ✅ Supported - registration required | See the Ireland SMS Sender ID registration guide |
Isle of Man | ✅ Supported |
|
Israel | ✅ Supported |
|
Italy | ✅ Supported |
|
Ivory Coast | ✅ Supported - registration required |
|
Jamaica | ✅ Supported |
|
Japan | ✅ Supported |
|
Jersey | ✅ Supported |
|
Jordan | ✅ Supported - registration required |
|
Kazakhstan | ✅ Supported - registration required |
|
Kuwait | ✅ Supported - registration required |
|
Kyrgyzstan | ✅ Supported |
|
Laos | ✅ Supported |
|
Latvia | ✅ Supported |
|
Lebanon | ✅ Supported |
|
Lesotho | ✅ Supported |
|
Liberia | ✅ Supported - registration required |
|
Liechtenstein | ✅ Supported |
|
Lithuania | ✅ Supported |
|
Luxembourg | ✅ Supported |
|
Macao | ❌ Not supported | Sender ID replaced with a short code |
Macedonia | ✅ Supported - registration required |
|
Madagascar | ✅ Supported |
|
Malawi | ✅ Supported - registration required |
|
Malaysia | ❌ Not supported | URLs and phone numbers in message bodies may be blocked |
Maldives | ✅ Supported |
|
Mali | ✅ Supported |
|
Malta | ✅ Supported |
|
Martinique | ✅ Supported |
|
Mauritius | ✅ Supported |
|
Mayotte | ✅ Supported |
|
Mexico | ✅ Supported - registration required |
|
Moldova | ✅ Supported |
|
Monaco | ✅ Supported |
|
Montenegro | ✅ Supported - registration required |
|
Montserrat | ✅ Supported |
|
Morocco | ✅ Supported - registration required |
|
Mozambique | ✅ Supported |
|
Namibia | ❌ Not supported | Sender ID replaced with a short code |
Nauru | ❌ Not supported | No replacement details available |
Netherlands | ✅ Supported |
|
Netherlands Antilles | ✅ Supported |
|
New Caledonia | ✅ Supported |
|
New Zealand | ❌ Not supported | Sender ID replaced with a random short code |
Nicaragua | ❌ Not supported | Sender ID replaced with a short code or long code |
Niger | ✅ Supported |
|
Nigeria | ✅ Supported - registration required |
|
Norway | ✅ Supported |
|
Oman | ✅ Supported - registration required |
|
Pakistan | ✅ Supported - registration required |
|
Palestine | ✅ Supported - registration required |
|
Panama | ❌ Not supported | Sender ID overwritten with a short code or long code |
Papua New Guinea | ✅ Supported |
|
Paraguay | ❌ Not supported | No replacement details available |
Peru | ❌ Not supported | Sender ID replaced with a generic short code |
Philippines | ✅ Supported - registration required |
|
Poland | ✅ Supported |
|
Portugal | ✅ Supported |
|
Puerto Rico | ❌ Not supported (alphanumeric) | Toll-free number required |
Qatar | ✅ Supported - registration required |
|
Romania | ✅ Supported - registration required |
|
Rwanda | ✅ Supported |
|
Réunion | ✅ Supported |
|
Saint Vincent and the Grenadines | ✅ Supported |
|
Samoa | ✅ Supported |
|
San Marino | ✅ Supported |
|
São Tomé and Príncipe | ❌ Not supported | No replacement details available |
Saudi Arabia | ✅ Supported - registration required |
|
Senegal | ✅ Supported |
|
Serbia | ✅ Supported |
|
Seychelles | ✅ Supported |
|
Sierra Leone | ✅ Supported |
|
Singapore | ✅ Supported - registration required | Registration required; promotional traffic is limited to local companies |
Sint Maarten | ❌ Not supported (alphanumeric) | Toll-free number required |
Slovakia | ✅ Supported |
|
Slovenia | ✅ Supported |
|
Solomon Islands | ✅ Supported |
|
Somalia | ✅ Supported |
|
South Africa | ❌ Not supported | Sender ID replaced with a local long code |
South Korea | ❌ Not supported | Sender ID replaced with a local long code |
South Sudan | ✅ Supported |
|
Spain | ✅ Supported - registration required | See the Spain SMS Sender ID requirements |
Sri Lanka | ✅ Supported - registration required |
|
St. Kitts and Nevis | ✅ Supported |
|
St. Lucia | ✅ Supported |
|
Sudan | ✅ Supported |
|
Suriname | ✅ Supported |
|
Swaziland | ✅ Supported |
|
Sweden | ✅ Supported | No registration required |
Switzerland | ✅ Supported | No registration required |
Syria | ❌ Not supported | Sender ID replaced with a long code |
Taiwan | ❌ Not supported | Messages with URLs on non-whitelisted domains may be blocked |
Tanzania | ✅ Supported - registration required |
|
Thailand | ✅ Supported - registration required | Registration required; contact our Support for current requirements |
Togo | ✅ Supported |
|
Tonga | ✅ Supported |
|
Trinidad and Tobago | ✅ Supported |
|
Tunisia | ✅ Supported |
|
Turkey | ✅ Supported - registration required |
|
Turkmenistan | ✅ Supported |
|
Turks and Caicos Islands | ✅ Supported |
|
United Arab Emirates | ✅ Supported - registration required |
|
Ukraine | ✅ Supported |
|
United Kingdom | ✅ Supported | Auto-registration occurs after the first send; allow about 24 business hours |
United States | ❌ Not supported (alphanumeric) | Toll-free number required |
Uruguay | ❌ Not supported | Sender ID replaced with a generic short code or long code |
Vanuatu | ✅ Supported |
|
Venezuela | ❌ Not supported | Sender ID replaced with a generic short code or long code |
Vietnam | ✅ Supported - registration required |
|
Virgin Islands (US) | ❌ Not supported (alphanumeric) | Toll-free number required |
Yemen | ✅ Supported |
|
Zambia | ✅ Supported |
|
Zimbabwe | ✅ Supported |
|
Sender Names in the US
The US and Canada don't support custom SMS sender names due to carrier regulations and infrastructure requirements. Instead, Omnisend provides you with a dedicated toll-free phone number (e.g., 1-833-XXX-XXXX) that's exclusive to your account and remains consistent across all campaigns.
To help customers recognize your brand, start your SMS messages with your business name (e.g., "YourBrandName: Your order is ready!").
Country-Specific Registration Requirements
Some countries require you to register your Sender name/ID with telecommunications regulators before sending SMS. Currently, this applies to:
How it works: You register your Sender ID with the regulator, then use that registered value as your Sender Name in Omnisend.
Note: Singapore has separate registration requirements. See the SGNIC SMS Sender ID Registry for more information.
💡 Learn more: SMS Sender ID Registration Requirements by Country.
FAQ
Can I use emojis in my sender name?
No. Only letters (A-Z) and numbers (0-9) are allowed.
What happens if my country doesn't support sender names?
A phone number will display instead. Start your message text with your brand name to ensure recognition.
Can I use a different sender name for each SMS Campaign?
No. The sender name is configured globally in Store settings → SMS and applies to all SMS Campaigns and Automation Workflows.
Why is there an 11-character limit?
This is an SMS network standard across all carriers and cannot be changed.
Do I need to register my sender name?
It depends on the destination. Check the SMS Sender ID Registration by Country before sending.
If you have any further questions or need additional assistance, contact our Support Team via in-app chat or [email protected].