Country Summary

Country nameIran
ISO codeIR
RegionMiddle East & Africa
Mobile country code432
Dialing code+98
Major carriersMobile Telecommunication Company of Iran(MCI), MTN Irancell, Rightel, TKC, MTCE, Taliya

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 toward Iranian networks. 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 capabilityRequiredNot SupportedNot SupportedNot SupportedNot Supported
Twilio supported Required
Learn more
--- --- Supported---
Sender ID preservedYes --- --- No---
Provisioning time10 working daysN/AN/AN/AN/A
UCS-2 supportSupportedN/AN/ASupportedN/A
Use case restrictions

Sending political, religious, and adult-related content is strictly prohibited.

N/A

N/A

N/A

N/A

Best practices

Dynamic sender ID is not supported in Iran. They would be overwritten with generic sender ID outside Twilio's network and delivered at best-effort basis only.

The MCI network in Iran supports alphanumeric sender ID pre-registration which could improve deliverability. Generic sender ID to this network is not allowed and would result in delivery failure.

N/A

N/A

N/A

N/A

Alphanumeric - Pre-registration
Operator network capabilityRequired
Twilio supported Required
Learn more
Sender ID preservedYes
Provisioning time10 working days
UCS-2 supportSupported
Use case restrictions

Sending political, religious, and adult-related content is strictly prohibited.

Best practices

Dynamic sender ID is not supported in Iran. They would be overwritten with generic sender ID outside Twilio's network and delivered at best-effort basis only.

The MCI network in Iran supports alphanumeric sender ID pre-registration which could improve deliverability. Generic sender ID to this network is not allowed and would result in delivery failure.

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

N/A

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

N/A

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.