Skip to main content

Locale Summary

Locale nameSerbia
ISO codeRS
RegionEurope
Mobile country code220
Dialing code381

Guidelines

Two-way SMS supported No
Twilio concatenated message supportYes
Message length
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

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, particularly 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 capabilitySupportedSupported --- Not SupportedNot Supported
Twilio supported Supported Supported
Learn more
--- SupportedNot Supported
Sender ID preservedYesNo --- No---
Provisioning time16 days------------
UCS-2 supportSupportedSupported---Supported---
Use case restrictions

In Serbia, Sender ID preservation cannot be guaranteed without registration. We offer customers the option to register their Sender IDs so they can have their messages delivered with the Alphanumeric Sender IDs of their choice. This option comes with a monthly fee.

Dynamic Alphanumeric Sender IDs are not fully supported by the network mt:s (Telekom Srbijaand Telenor). Sender IDs may be overwritten with a generic Alphanumeric Sender ID outside the Twilio platform to ensure deliverability for this network.
We suggest our clinets to OPT IN the optional Sender ID Registration service we offer in case they need to use specific Alpha Sender IDs

---

Dynamic Numeric Sender IDs are not supported by mobile operators in Serbia. Sender IDs will be overwritten with a Generic Alphanumeric Sender ID outside the Twilio platform to ensure deliverability.

---
Best practices

In case the traffic is promotional we suggest the customer adding the phrase " Odjava STOPMFL na 1599, 0din" at the end of each SMS. This will allow the subscriber that receives the SMS to OPT - OUT the promotional content in case they want to stop receiving such messages

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

In Serbia, Sender ID preservation cannot be guaranteed without registration. We offer customers the option to register their Sender IDs so they can have their messages delivered with the Alphanumeric Sender IDs of their choice. This option comes with a monthly fee.

Best practices

In case the traffic is promotional we suggest the customer adding the phrase " Odjava STOPMFL na 1599, 0din" at the end of each SMS. This will allow the subscriber that receives the SMS to OPT - OUT the promotional content in case they want to stop receiving such messages

Alphanumeric - Dynamic
Operator network capabilitySupported
Twilio supported Supported
Learn more
Sender ID preservedNo
Provisioning time---
UCS-2 supportSupported
Use case restrictions

Dynamic Alphanumeric Sender IDs are not fully supported by the network mt:s (Telekom Srbijaand Telenor). Sender IDs may be overwritten with a generic Alphanumeric Sender ID outside the Twilio platform to ensure deliverability for this network.
We suggest our clinets to OPT IN the optional Sender ID Registration service we offer in case they need to use specific Alpha Sender IDs

Best practices---
Long Code - Domestic
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---
Long Code - International
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning time---
UCS-2 supportSupported
Use case restrictions

Dynamic Numeric Sender IDs are not supported by mobile operators in Serbia. Sender IDs will be overwritten with a Generic Alphanumeric Sender ID outside the Twilio platform to ensure deliverability.

Best practices---
Short Code
Operator network capabilityNot Supported
Twilio supportedNot Supported
Sender ID preserved---
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---

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.