IVORY COAST (CI)

Country Summary

Country nameIvory Coast
ISO codeCI
RegionMiddle East & Africa
Mobile country code612
Dialing code+225

Guidelines

Two-way SMS supported No
Twilio concatenated message supportYes
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, 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.

The Autorité de Régulation des Télécommunications/TIC de Côte d’Ivoire (ARTCI), Abidjan, hereby announces the modification of the national numbering plan of Côte d’Ivoire, from eight (8) to ten (10) digits, effective January 31, 2021 in Côte d’Ivoire. We strongly advise customers to follow the new numbering plan:

MSIDN will go to ten digits. Currently we have eight digits for national format.

  • Current format: (CountryCode) XXXXXXX
  • New format: (CountryCode) YYXXXXXXXX

Here are the new 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

AlphanumericLong CodeShort Code
Pre-registrationDynamicDomesticInternational
Operator network capabilitySupportedSupportedSupported --- Supported
Twilio supported Supported Supported
Learn more
Not Supported --- ---
Sender ID preservedYes --- --- --- ---
Provisioning time7 working days------------
UCS-2 support---------------
Use case restrictions

Pre-registration of Alphanumeric Sender IDs is required for customers based in Ivory Coast.

------------
Best practices---------------
Alphanumeric - Pre-registration
Operator network capabilitySupported
Twilio supported Supported
Sender ID preservedYes
Provisioning time7 working days
UCS-2 support---
Use case restrictions

Pre-registration of Alphanumeric Sender IDs is required for customers based in Ivory Coast.

Best practices---
Alphanumeric - Dynamic
Operator network capabilitySupported
Twilio supported Supported
Learn more
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---
Long Code - Domestic
Operator network capabilitySupported
Twilio supportedNot Supported
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---
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 capabilitySupported
Twilio supported---
Sender ID preserved---
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.