Skip to main content

Locale Summary

Locale nameIran
ISO codeIR
RegionMiddle East & Africa
Mobile country code432
Dialing code+98

Guidelines

Two-way SMS supported No
Number portability availableYes
Twilio concatenated message supportYes
Message length-----
Twilio MMS supportNot Available
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. Per local regulations, peer-to-peer (P2P) traffic is prohibited by Iranian networks. 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.

Please take note that gambling, betting, political, religious or adult-related content is strictly prohibited in Iran.

Phone Numbers & Sender ID

AlphanumericLong CodeShort Code
Pre-registrationDynamicDomesticInternational
Operator network capabilityRequiredNot SupportedNot SupportedNot SupportedNot Supported
Twilio supported Required
Learn more
Supported --- Supported---
Sender ID preservedYesNo --- No---
Provisioning time2 weeksN/AN/AN/AN/A
UCS-2 supportN/AN/AN/AN/AN/A
Use case restrictions

Only Sender IDs related to International OTP traffic will be allowed. Other type of traffic as well as the one generated from Domestic Companies is not permitted in Iran.

The registered Sender ID will not be reserved for the Network MTN to due local compliance reasons. The Sender ID will be replaced from a Longcode outside Twilio's platfrom 

N/A

N/A

N/A

N/A

Best practices

During registration please provide a representative sample as SMS as content allow listing is also required in Iran. Messages submitted via a registered Sender ID with content that is different from the allowlisted one will be rejected

Sender ID Registration is Required for Iran. Submission of messages with unregistered Sender IDs will be executed on a best effort basis

N/A

Sender ID Registration is Required for Iran. Submission of messages with unregistered Sender IDs will be executed on a best effort basis

N/A

Alphanumeric - Pre-registration
Operator network capabilityRequired
Twilio supported Required
Learn more
Sender ID preservedYes
Provisioning time2 weeks
UCS-2 supportN/A
Use case restrictions

Only Sender IDs related to International OTP traffic will be allowed. Other type of traffic as well as the one generated from Domestic Companies is not permitted in Iran.

The registered Sender ID will not be reserved for the Network MTN to due local compliance reasons. The Sender ID will be replaced from a Longcode outside Twilio's platfrom 

Best practices

During registration please provide a representative sample as SMS as content allow listing is also required in Iran. Messages submitted via a registered Sender ID with content that is different from the allowlisted one will be rejected

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

N/A

Best practices

Sender ID Registration is Required for Iran. Submission of messages with unregistered Sender IDs will be executed on a best effort basis

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 supportN/A
Use case restrictions

N/A

Best practices

Sender ID Registration is Required for Iran. Submission of messages with unregistered Sender IDs will be executed on a best effort basis

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.