SOUTH AFRICA (ZA)

Country Summary

Country nameSouth Africa
ISO codeZA
RegionMiddle East & Africa
Mobile country code655
Dialing code+27
Major carriersVodacom, MTN, Cell C, Telkom

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

Direct marketing messages are regulated under article 16 of the Wireless Application Service Providers’ Association (WASPA) Code of Conduct. Unless a consumer has expressly or implicitly requested or agreed otherwise, marketing messages should not be sent on: Sundays and public holidays; Saturdays before 9am and after 1pm; and all other days between the hours of 8pm and 8am the following day.

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 --- Not SupportedNot SupportedSupported
Twilio supported --- Not SupportedSupportedNot Supported
Sender ID preserved --- --- No ---
Provisioning time--------
UCS-2 support --------
Use case restrictions ----Non-local numeric senderId would be overwritten into generic alphanumeric outside Twilio's platform whilst local numeric senderId would be delivered intact.--
Best practices ----You may use a global SMS-capable number to reach mobile phones in South Africa.--
Preregistered
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices --
Alphanumeric
Operator network capabilityNot Supported
Twilio supportedNot Supported
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices --
Long Code
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning time--
UCS-2 support --
Use case restrictions Non-local numeric senderId would be overwritten into generic alphanumeric outside Twilio's platform whilst local numeric senderId would be delivered intact.
Best practices You may use a global SMS-capable number to reach mobile phones in South Africa.
Short Code
Operator network capabilitySupported
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.