AZERBAIJAN (AZ)

Country Summary

Country nameAzerbaijan
ISO codeAZ
RegionAsia
Mobile country code400
Dialing code+994
Major carriersAzercell, Bakcell, Nar Mobile

Guidelines

Two-way SMS supported No
Number portability availableYes
Twilio concatenated message supportYes
Message length-----
Twilio MMS supportConverted to SMS with embedded URL
Sending SMS to landline numbersSMS cannot be sent to 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

Alpha senderID is supported in Azercell. Numeric senderID is not supported in Azercell, please use alpha senderID otherwise we will overwritte numeric sender to a generic alpha "InfoSMS" in order to deliver your numeric senderID msg. Alpha senderID is supported in Bakcell. Numeric senderID is not supported in Bakcell, please use alpha senderID otherwise we will overwritte numeric sender to a generic alpha "Info" in order to deliver your numeric senderID msg. All Msg to Nar Mobile will be overwritten to a local Long code (+994) to ensure delivey.

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

PreregisteredAlphanumericLong CodeShort Code
Operator network capabilityNot RequiredSupportedSupportedNot Supported
Twilio supportedNot RequiredSupportedSupportedNot Supported
Sender ID preserved --- YesNo ---
Provisioning time--------
UCS-2 support --SupportedSupported--
Use case restrictions ----Numeric sender ID would be overwritten with random alphanumeric or numeric sender ID to ensure delivery--
Best practices --------
Preregistered
Operator network capabilityNot Required
Twilio supportedNot Required
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices --
Alphanumeric
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning time--
UCS-2 support Supported
Use case restrictions --
Best practices --
Long Code
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedNo
Provisioning time--
UCS-2 support Supported
Use case restrictions Numeric sender ID would be overwritten with random alphanumeric or numeric sender ID to ensure delivery
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.