Country Summary

Country nameChad
ISO codeTD
RegionMiddle East & Africa
Mobile country code622
Dialing code+235
Major carriersAirtel, Tigo

Guidelines

Two-way SMS supported No
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, 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 capabilityNot RequiredSupportedNot SupportedSupportedNot Supported
Twilio supported Not Required Supported
Learn more
Not SupportedSupportedNot Supported
Sender ID preserved --- Yes --- Yes---
Provisioning timeN/ANoneN/AN/AN/A
UCS-2 supportN/ASupportedN/ASupportedN/A
Use case restrictions

N/A

N/A

N/A

Numeric sender IDs are prohibited for Milicom Tigo Use an alphanumeric sender ID to this network for better deliverability.

N/A

Best practices

N/A

Avoid the use of generic alphanumeric sender ID as it tends to be blocked and filtered by the mobile operators

N/A

N/A

N/A

Alphanumeric - Pre-registration
Operator network capabilityNot Required
Twilio supported Not Required
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

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

N/A

Best practices

Avoid the use of generic alphanumeric sender ID as it tends to be blocked and filtered by the mobile operators

Long Code - Domestic
Operator network capabilityNot Supported
Twilio supportedNot 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 capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

Numeric sender IDs are prohibited for Milicom Tigo Use an alphanumeric sender ID to this network for better deliverability.

Best practices

N/A

Short Code
Operator network capabilityNot Supported
Twilio supportedNot 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.