Country Summary

Country nameTurkey
ISO codeTR
RegionMiddle East & Africa
Mobile country code286
Dialing code+90
Major carriersTurkcell, Vodafone, Turk Telecom

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 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

Turkish carriers are filtering traffic with Numeric, short code, and unregistered Alphanumeric Sender IDs. Pre-registration of Alphanumeric Sender IDs is mandatory and unregistered Sender IDs may be blocked by carriers. Person-to-person (P2P) traffic and gambling, political, or religious content are prohibited.

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 Supported --- Not Supported
Twilio supportedSupportedNot SupportedSupported --- Not Supported
Sender ID preservedYesNoNo --- No
Provisioning time1 week------------
UCS-2 support---------------
Use case restrictions

P2P, gambling, political, or religious content is prohibited.

All messages used for advertising and marketing purposes must follow these regulations:

  1. Preface messages with ‘REKLAM:’ or ‘TANITIM:’, which indicates to the end user that s/he is receiving a promotional message.
  2. Include the company’s URL or customer care number, and inform recipients where to find details of the campaign or promotion being advertised
  3. End the SMS with an option to opt-out.

Unsolicited messages will not be sent to end users.

Alphanumeric is only supported through pre-registration.

Numeric Sender IDs will be overwritten with generic Alphanumeric Sender IDs outside Twilio's platform.

---
---
Best practices
---

Use only pre-registered Sender IDs to ensure message delivery.

Messages submitted with Numeric Aender IDs are likely to be blocked by carriers. Pre-register Alphanumeric Sender IDs to ensure delivery.

---
---
Alphanumeric - Pre-registration
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning time1 week
UCS-2 support---
Use case restrictions

P2P, gambling, political, or religious content is prohibited.

All messages used for advertising and marketing purposes must follow these regulations:

  1. Preface messages with ‘REKLAM:’ or ‘TANITIM:’, which indicates to the end user that s/he is receiving a promotional message.
  2. Include the company’s URL or customer care number, and inform recipients where to find details of the campaign or promotion being advertised
  3. End the SMS with an option to opt-out.

Unsolicited messages will not be sent to end users.

Best practices
---
Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio supportedNot Supported
Sender ID preservedNo
Provisioning time---
UCS-2 support---
Use case restrictions

Alphanumeric is only supported through pre-registration.

Best practices

Use only pre-registered Sender IDs to ensure message delivery.

Long Code - Domestic
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning time---
UCS-2 support---
Use case restrictions

Numeric Sender IDs will be overwritten with generic Alphanumeric Sender IDs outside Twilio's platform.

Best practices

Messages submitted with Numeric Aender IDs are likely to be blocked by carriers. Pre-register Alphanumeric Sender IDs to ensure delivery.

Long Code - International
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions
---
Best practices
---
Short Code
Operator network capabilityNot Supported
Twilio supportedNot Supported
Sender ID preservedNo
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.