Country-Specific Features and Restrictions
This section provides an overview of the most common destination countries with its (country- and / or mobile network operator-) specific regulations regarding SMS communication. Regulation changes cannot be influenced by Retarus and may affect already established configurations. You should check these pages regularly for updates as telecommunications ecosystem requirements continue to evolve and change, and the information below may be updated or changed without notice.
Sending recommendations
Sending successfully A2P SMS worldwide faces a lot of different country specific regulations. Most countries define similar guidelines that are listed in this chapter and that we highly encourage you to fulfill.
Compliance
Retarus strongly recommends customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws.
In general, the following is strictly prohibited in some countries:
gambling (e.g. betting odds) related message content
lottery-related message content
the use of URL shorteners such as http://bit.ly or tiny.url
Best practices
Avoiding trouble within the SMS communication, we strongly encourage you to implement the following best practices:
Get opt-in consent (via webpage, opt-in messages, ...) from each end user before sending any messages to them.
SMS campaigns should support opt-out functionality by supporting STOP messages.
SMS campaigns should support HELP/STOP messages in the end-user’s local language.
Only communicate during an end-user’s daytime hours unless it is urgent.
Do not contact end-users on do-not-call or do-not-disturb registries.
Do not use a mobile network operator name, sensitive senderIds (such as ‘Police’) or a company name that is not your own.
Try to avoid the use of alphanumeric senderIds that only contain numbers. They might be interpreted as Longcode and thereby face country-specific Longcode regulations.
Avoid content related to high-risk financial services, lead generation services, debt collection or forgiveness.
Countries
Austria
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
AT | AUT | Europe | +43 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported | |
Longcode | Domestic Longcode only, otherwise overwrite with Retarus Austrian LC. | ||
Shortcode | by network operator | Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
Belgium
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
BE | BEL | Europe | +32 |
Functional possibilities | |||
SenderID | Alphanumeric | Not Supported, overwrite with random Shortcode. | |
Longcode | Domestic Longcode only, otherwise overwrite with random Shortcode. | ||
Shortcode | by network operator | Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported (except Belgacom*) | ||
Two-way | Supported | ||
Delivery Notification | Supported** | ||
Concatenated Messages | Supported | ||
* SMS to Belgacom that are encoded with UCS-2 might not be displayed properly, since this network operator only supports HP Roman 8 character set.
** Delivery Notifications are originated by receiving network instead of receiving handset.
Brazil
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
BR | BRA | South America | +55 |
Functional possibilities | |||
SenderID | Alphanumeric | Not Supported | |
Longcode | Domestic Longcode only, otherwise overwrite with random Longcode or Shortcode. | ||
Shortcode | by network operator | Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported (except Oi, NEXTEL, and CTBC (Algar)) | ||
Two-way | Supported | ||
Delivery Notification | Supported* | ||
Concatenated Messages | Supported** | ||
* Delivery Notifications are originated by receiving network instead of receiving handset. Oi does not support Delivery Notifications.
** Concatenated messages are not supported in Oi network.
Denmark
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
DK | DNK | Europe | +45 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported | |
Longcode | Supported | ||
Shortcode | by network operator | Not Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Supported | ||
Delivery Notification | Supported* | ||
Concatenated Messages | Supported | ||
* Only delivery receipts on the network level.
France
Marketing traffic
Opt-out information has to be provided in SMS message text. Typically, opt-out is done by sending STOP to a dynamically shared Shortcode. Be aware that adding the opt-out Shortcode to your SMS message text decreases the number of characters that you can freely use in your SMS and might result in splitting your SMS in several parts.
Marketing SMS traffic is blocked on public French holidays and Sundays as well as from 10pm until 8am. During this time, SMS are queued and sent out the following day.
Transactional traffic
Compared to marketing SMS, an opt-out possibility needs to be provided as well, but the information does not need to be part of the SMS message text.
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
FR | FRA | Europe | +33 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported* | |
Longcode | Domestic Longcode only**, otherwise overwrite with random Shortcode. | ||
Shortcode | by network operator | Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported (except Bouygues Telecom***) | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
* Alphanumeric senderIds with numbers (e.g. A27462, 743B684, 7384C,…) are considered as numeric senderIds and will be blocked by SFR.
** Sending limitations of 10k SMS per month.
*** SMS to Bouygues Telecom that are encoded with UCS-2 will be replaced by GSM-7 encoding to ensure delivery.
Germany
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
DE | DEU | Europe | +49 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported | |
Longcode | Supported | ||
Shortcode | by network operator | Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
Hungary
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
HU | HUN | Europe | +36 |
Functional possibilities | |||
SenderID | Alphanumeric | Not Supported | |
Longcode | Domestic Longcode only; otherwise, overwrite with random domestic Longcode. | ||
Shortcode | by network operator | Not Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
India
To avoid Unsolicited Commercial Communication and enhance mobile subscriber policy, the Telecom Regulatory Authority of India (TRAI) are strongly regulating the Indian Mobile Network Communication.
Domestic traffic
Only companies having an office located in India are basically able to send A2P SMS through domestic routes. Therefor, they need to fulfill a successful TPOA registration.
International traffic
A2P traffic that is not registered for domestic routing will be sent via international routes with a random Shortcode.
Political motivated traffic
During the election period, sending political SMS throughout the country is prohibited. Messages towards Jammu and Kashmir networks (e.g. 405/55 – Airtel J&K) are blocked due to political sensitivity.
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
IN | IND | Asia | +91 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported (only for domestic companies after registration) | |
Longcode | Not Supported | ||
Shortcode | by network operator | Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Not Supported | ||
Delivery Notification | Supported* | ||
Concatenated Messages | Supported | ||
* Only for domestic traffic. For international traffic, DNs are not supported or unreliable.
Italy
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
IT | ITA | Europe | +39 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported with registration*, otherwise overwrite with generic alphanumeric senderId. | |
Longcode | Supported | ||
Shortcode | by network operator | Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
* Alphanumeric SenderIds need to be registered. You only need to fill out a registration sheet and Retarus (respectively the supplier we use for SMS termination) will take care of the registration for you.
Luxembourg
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
LU | LUX | Europe | +352 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported | |
Longcode | Supported | ||
Shortcode | by network operator | Not Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
Netherlands
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
NL | NLD | Europe | +31 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported | |
Longcode | Supported | ||
Shortcode | by network operator | Not Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
New Zealand
Marketing SMS
Social invites and marketing are not supported when sending SMS traffic with the Retarus dedicated Shortcode. Nevertheless, it is possible to send marketing SMS after a registration. For more information, please contact your Retarus contact or support@retarus.com.
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
NZ | NZL | Oceania | +64 |
Functional possibilities | |||
SenderID | Alphanumeric | Not Supported. Will be overwritten with Shortcode. | |
Longcode | Not Supported. Will be overwritten with Shortcode. | ||
Shortcode | by network operator | Supported | |
by Retarus | Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
Poland
Blocked traffic
A2P SMS related to Premium Services will be blocked, e.g. messages with ads of Premium Rate services and messages that contain premium numbers or Shortcodes.
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
PL | POL | Europe | +48 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported | |
Longcode | Domestic Longcode only, otherwise overwrite with alphanumeric SenderId. | ||
Shortcode | by network operator | Not Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
Portugal
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
PT | PRT | Europe | +351 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported | |
Longcode | Supported | ||
Shortcode | by network operator | Not Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
Singapore
Singapore does maintain a Do-Not-Call (DNC) registry. We highly recommend respecting the registered periods when sending to Singapore. For more information visit https://www.dnc.gov.sg/index.html.
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
SG | SGP | Asia | +65 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported | |
Longcode | Supported | ||
Shortcode | by network operator | Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
Spain
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
ES | ESP | Europe | +34 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported | |
Longcode | Supported | ||
Shortcode | by network operator | Not Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
Sweden
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
SE | SWE | Europe | +46 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported | |
Longcode | Supported | ||
Shortcode | by network operator | Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
Switzerland
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
CH | CHE | Europe | +41 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported | |
Longcode | Supported | ||
Shortcode | by network operator | Not Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
Turkey
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
TR | TUR | Middle East & Asia | +90 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported with registration*, otherwise overwrite with generic alphanumeric senderId. | |
Longcode | Not Supported | ||
Shortcode | by network operator | Not Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Not Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
* Alphanumeric SenderIds need to be registered. You only need to fill out a registration sheet and Retarus (respectively the supplier we use for SMS termination) will take care of the registration for you.
United Kingdom
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
GB | GBR | Europe | +44 |
Functional possibilities | |||
SenderID | Alphanumeric | Supported | |
Longcode | Supported* | ||
Shortcode | by network operator | Supported | |
by Retarus | Not Available | ||
Encoding | GSM-7 | Supported | |
UCS-2 | Supported | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
* International (non-UK) Long Virtual Numbers may be blocked by Mobile Network Operator EE.
United States of America
General | |||
|---|---|---|---|
ISO-2 | ISO-3 | Region | Dialing Code |
US | USA | North America | +1 |
Functional possibilities | |||
SenderID | Alphanumeric | Not Supported | |
Longcode | Only domestic Loncodes supported* | ||
Shortcode | by network operator | Supported | |
by Retarus | Available | ||
Encoding | GSM-7 | Supported** | |
UCS-2 | Supported** | ||
Two-way | Supported | ||
Delivery Notification | Supported | ||
Concatenated Messages | Supported | ||
* Due to throughput regulations, Retarus might overwrite with a random Longcode.
** The Euro symbol (€) is not supported.
Other countries
If you need information about sending regulations to other countries that are not listed in this document, please contact your Retarus contact or support@retarus.com to get more information.