Country Summary

Country nameNigeria
ISO codeNG
RegionMiddle East & Africa
Mobile country code621
Dialing code+234
Major carriersMTN, Airtel, Etisalat, Glo Mobile, Visafone

Guidelines

Two-way SMS supported No
Number portability availableYes
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

Dynamic alphanumeric sender IDs are supported, but numeric sender IDs will be attempted on a best-effort basis. We highly recommend sending with an alphanumeric sender ID specific to your brand and content. The Nigerian Communication Commission has mandated telecom operators in Nigeria to implement the Do-Not-Disturb (DND) registry. The Do Not Disturb service in Nigeria allows customers to opt out of receiving promotional messages. Any attempt to send promotional SMS to those numbers will fail. Twilio provides special routes that have permission to contact phone numbers on the DND list by SMS when the traffic is classified as OTP (one-time password). 1. Unsolicited messages are not allowed via this route. Your recipients must have expressed permission to be contacted via SMS. 2. A phone number on the DND list might also be switched off, out of network coverage, or simply dead. The delivery report will indicate the status of messages sent to phone numbers on the DND.

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

PreregisteredAlphanumericLong CodeShort Code
Operator network capability --- SupportedSupportedNot Supported
Twilio supported --- SupportedSupportedNot Supported
Sender ID preserved --- YesYes ---
Provisioning time--------
UCS-2 support --------
Use case restrictions --------
Best practices --Generic sender IDs are likely to be blocked. Use a sender ID that is specific to your brand and the content of your message.----
Preregistered
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices --
Alphanumeric
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices Generic sender IDs are likely to be blocked. Use a sender ID that is specific to your brand and the content of your message.
Long Code
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices --
Short Code
Operator network capabilityNot Supported
Twilio supportedNot 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.