Guidelines

Ivory Coast (CI)

We've compiled regulatory and compliance information to help ensure you're communicating effectively and compliantly around the world.

Back to Guidelines

Locale Summary
Locale name	Ivory Coast
ISO code The International Organization for Standardization two character representation for the given locale.	CI
Region	Middle East & Africa
Mobile country code A three digit code associated with the given locale and used in conjunction with a Mobile Network Code to uniquely identify mobile networks.	612
Dialing code The dialing prefix used to establish a call or send an SMS from one locale to the given locale.	+225

Guidelines
Two-way SMS supported Whether Twilio supports two-way SMS in the given locale.	No
Number portability available Whether number portability is available in the given locale.	No
Twilio concatenated message support Concatenation refers to the capability of splitting a message that is too long to be sent in one SMS into smaller pieces and then joining the pieces at the receiving end so that the receiver sees the message as one.	Yes* For certain sender ID types this may not be supported. Where messages are split and rejoined may vary based on character encoding.
Message length How many characters can be sent given a particular message encoding before the message will be split into concatenated segments.	-----
Twilio MMS support Multimedia Messaging Service (MMS) provides a standards-based means to send pictures and video to mobile phones.	Converted to SMS with embedded URL
Sending SMS to landline numbers How Twilio handles an SMS message destined for landline telephone number.	You 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. This table lists some general best practices.	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: Get opt-in consent from each end-user before sending any communication to them, particularly for marketing or other non-essential communications. Only communicate during an end-user’s daytime hours unless it is urgent. SMS campaigns should support HELP/STOP messages, and similar messages, in the end-user’s local language. Do not contact end-users on do-not-call or do-not-disturb registries. On 31 January, 2021, the Autorité de Régulation des Télécommunications/TIC de Côte d’Ivoire (ARTCI), Abidjan, updated the Ivory Coast numbering scheme from eight (8) to ten (10) digits. We strongly advise customers to follow this updated numbering plan: MSIDN is now ten digits: Current format: (CountryCode) YYXXXXXXXX Old format: (CountryCode) XXXXXXXX Here are the digits for each network (YY in the above formats): 01 for Moov/Etisalat (MCC/MNC=612/02) Example Current MSISDN: 225 01286981 New MSISDN: 225 0101286981 05 for MTN (MCC/MNC=612/05) Example Current MSISDN : 225 56555946 New MSISDN: 225 0556555946 07 for Orange (MCC/MNC=612/03) Example Current MSISDN: 225 47318432 New MSISDN: 225 0747318432

Phone Numbers & Sender ID

Alphanumeric

	Global Pre-registration	Dynamic
Operator network capability Whether mobile operators in the given country support the feature.	Required There is no segregation between International and Domestic Traffic	Not Supported
Twilio supported Whether Twilio supports the feature for the given country.	Supported Learn more and register via the Console	Supported Learn more
Sender ID preserved In some countries sender IDs for certain sender types are not preserved and are changed for compliance and/or deliverability reasons. In these countries mobile subscribers will see a different ‘from sender ID’ than the one sent by you.	Yes	No
Provisioning time Provisioning is the process of getting the sender ID approved and registered with mobile networks (depending on country requirements). Provisioning time is how long this process takes in the given country.	3 weeks	N/A
UCS-2 support	Supported	---
Use case restrictions	Promotional content is not allowed to be registered. Exception can be made for Domestic customers with +30,000 SMS per month	Sender ID Registration is Required. Submission with unregistered Sender IDs will be attempted on a best effort basis. Google as a Sender ID is prohibited in the Ivory Coast. Messages using this Sender ID may be blocked or filtered by the local operators.
Best practices	Please refrain from using requesting generic sender IDs like InfoSMS, INFO, Verify, Notify, etc. to avoid being blocked by network operators.	Twilio suggests using a pre-registered Alphanumeric Sender ID in Ivory Coast

Long codes and short codes

	Long code domestic	Long code international	Short code
Operator network capability Whether mobile operators in the given country support the feature.	Supported	Not Supported	Supported
Twilio supported Whether Twilio supports the feature for the given country.	Not Supported	Supported	---
Sender ID preserved In some countries sender IDs for certain sender types are not preserved and are changed for compliance and/or deliverability reasons. In these countries mobile subscribers will see a different ‘from sender ID’ than the one sent by you.	---	No	---
Provisioning time Provisioning is the process of getting the sender ID approved and registered with mobile networks (depending on country requirements). Provisioning time is how long this process takes in the given country.	---	---	---
UCS-2 support	---	---	---
Use case restrictions	---	Numeric Sender IDs are not supported by the MTN network in Ivory Coast. Submitting messages with a Numeric Sender ID will result in delivery failure.	---
Best practices	---	Twilio suggests using a pre-registered Alphanumeric Sender ID in Ivory Coast	---

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.