Skip to main content

Country Summary

Country nameUruguay
ISO codeUY
RegionSouth America
Mobile country code748
Dialing code+598

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, 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

Toll FreeLong CodeShort Code
DomesticInternationalDomesticInternational
Operator network capability --- --- Not SupportedNot SupportedNot Supported
Twilio supported --- --- Not SupportedSupportedNot Supported
Sender ID preserved --- --- --- No---
Provisioning time------N/AN/AN/A
UCS-2 support------N/ANot SupportedN/A
Use case restrictions------

N/A

Dynamic Numeric Sender ID is not supported by mobile operators in Uruguay. All Sender ID will be overwritten into a generic Numeric or Shortcode outside the Twilio platform.

N/A

Best practices------

N/A

N/A

N/A

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 capabilityNot Supported
Twilio supportedNot Supported
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Long Code - International
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning timeN/A
UCS-2 supportNot Supported
Use case restrictions

Dynamic Numeric Sender ID is not supported by mobile operators in Uruguay. All Sender ID will be overwritten into a generic Numeric or Shortcode outside the Twilio platform.

Best practices

N/A

Short Code
Operator network capabilityNot Supported
Twilio supportedNot Supported
Sender ID preserved---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Alphanumeric - Pre-registration
Operator network capabilityNot Supported
Twilio supported Not Supported
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio supported Not Supported
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Phone Numbers & Sender ID (continued)

Alphanumeric
Pre-registrationDynamic
Operator network capabilityNot SupportedNot Supported
Twilio supported Not Supported Not Supported
Sender ID preserved --- ---
Provisioning timeN/AN/A
UCS-2 supportN/AN/A
Use case restrictions

N/A

N/A

Best practices

N/A

N/A

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.