Country Summary

Country nameBelarus
ISO codeBY
RegionEurope
Mobile country code257
Dialing code+375

Guidelines

Two-way SMS supported No
Number portability availableYes
Twilio concatenated message supportYes
Message length160 Characters
Twilio MMS supportConverted to SMS with embedded URL
Sending SMS to landline numbersYou cannot send SMS to a landline destination number: the Twilio REST API will throw a 400 response with error code 21614, the message will not appear in the logs, and the account will not be charged.
Compliance considerations

For companies based in Belarus, Twilio does not support domestic Alphanumeric Sender ID pre-registration because of local regulations. 

Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. The following are some general best practices:

  1. Get opt-in consent from each end user before sending any communication to them, particular for marketing or other non-essential communications.
  2. Only communicate during an end user's daytime hours unless it is urgent.
  3. SMS campaigns should support HELP/STOP messages, and similar messages, in the end user's local language.
  4. Do not contact end users on do-not-call or do-not-disturb registries.

Phone Numbers & Sender ID

AlphanumericLong CodeShort Code
Pre-registrationDynamicDomesticInternational
Operator network capabilitySupportedNot SupportedNot SupportedNot SupportedNot Supported
Twilio supported Supported --- --- Supported---
Sender ID preservedYes --- --- No---
Provisioning time6 weeksN/AN/AN/AN/A
UCS-2 supportSupportedN/AN/ASupportedN/A
Use case restrictions

For companies based in Belarus, Twilio does not support domestic Alphanumeric Sender ID pre-registration because of local regulations. 

The content of the messages needs to be related with the Sender ID that is being used otherwise the network operator may block the message. Generic Sender IDs are not allowed.

N/A

N/A

N/A

N/A

Best practices

Person-To-Person (P2P) messages are prohibited and these messages would be blocked/filtered by the mobile operators. 

Dynamic Alphanumeric Sender ID is not supported by mobile operators in Belarus. Send only with pre-registered sender Id. 

N/A

Numeric Sender ID is not supported by mobile operators in Belarus. It is overwritten with generic Alphanumeric Sender ID outside the Twilio platform and delivery is on best effort basis only. Twilio recommends sending only from registered sender Id.

Person-To-Person (P2P) messages are prohibited and these messages would be blocked/filtered by the mobile operators. 

N/A

Alphanumeric - Pre-registration
Operator network capabilitySupported
Twilio supported Supported
Sender ID preservedYes
Provisioning time6 weeks
UCS-2 supportSupported
Use case restrictions

For companies based in Belarus, Twilio does not support domestic Alphanumeric Sender ID pre-registration because of local regulations. 

The content of the messages needs to be related with the Sender ID that is being used otherwise the network operator may block the message. Generic Sender IDs are not allowed.

Best practices

Person-To-Person (P2P) messages are prohibited and these messages would be blocked/filtered by the mobile operators. 

Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

Dynamic Alphanumeric Sender ID is not supported by mobile operators in Belarus. Send only with pre-registered sender Id. 

Long Code - Domestic
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Long Code - International
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

N/A

Best practices

Numeric Sender ID is not supported by mobile operators in Belarus. It is overwritten with generic Alphanumeric Sender ID outside the Twilio platform and delivery is on best effort basis only. Twilio recommends sending only from registered sender Id.

Person-To-Person (P2P) messages are prohibited and these messages would be blocked/filtered by the mobile operators. 

Short Code
Operator network capabilityNot Supported
Twilio supported---
Sender ID preserved---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

For the benefit of all our customers, these guidelines are provided to help you comply with applicable requirements and to help ensure Twilio's platform remains compliant with global telecommunications ecosystem requirements. These guidelines represent our current understanding of common compliance requirements generally applicable to Twilio and its customers, and do not constitute legal advice. By posting these guidelines, Twilio makes no assurances regarding the legal compliance of your application built using our APIs. You are expected to understand and abide by all compliance obligations applicable to your specific application. 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.