Skip to main content

Country Summary

Country nameCuba
ISO codeCU
RegionNorth America
Mobile country code368
Dialing code+53

Guidelines

Two-way SMS supported No
Message length160 Characters
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.

Phone Numbers & Sender ID

Toll FreeLong CodeShort Code
DomesticInternationalDomesticInternational
Operator network capability --- --- --- --- ---
Twilio supported --- --- Not Supported --- Not Supported
Sender ID preserved --- --- --- --- ---
Provisioning time---------------
UCS-2 support---------------
Use case restrictions---------------
Best practices---------------
Toll Free - Domestic
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---
Toll Free - International
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---
Long Code - Domestic
Operator network capability ---
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 capability---
Twilio supportedNot Supported
Sender ID preserved---
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices---
Alphanumeric - Pre-registration
Operator network capabilitySupported
Twilio supported Supported
Sender ID preservedYes
Provisioning time6 months
UCS-2 supportSupported
Use case restrictions

You must pre-register Sender IDs before sending any application-to-person (A2P) traffic to Cuba.

All Sender IDs may only contain uppercase and/or lowercase letters. Operators in Cuba do not support combinations of letters and numbers, or Numeric Sender IDs. 

Promotional messages are forbidden via registered Sender ID.

Best practices---
Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio supported Not Supported
Sender ID preservedNo
Provisioning time---
UCS-2 support---
Use case restrictions---
Best practices

You must pre-register Sender IDs before sending any application-to-person (A2P) traffic to Cuba.

Phone Numbers & Sender ID (continued)

Alphanumeric
Pre-registrationDynamic
Operator network capabilitySupportedNot Supported
Twilio supported Supported Not Supported
Sender ID preservedYesNo
Provisioning time6 months---
UCS-2 supportSupported---
Use case restrictions

You must pre-register Sender IDs before sending any application-to-person (A2P) traffic to Cuba.

All Sender IDs may only contain uppercase and/or lowercase letters. Operators in Cuba do not support combinations of letters and numbers, or Numeric Sender IDs. 

Promotional messages are forbidden via registered Sender ID.

---
Best practices---

You must pre-register Sender IDs before sending any application-to-person (A2P) traffic to Cuba.

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.