Frequently Asked Questions
Use an SMS API provider like Twilio, Sinch, or MessageBird. Ensure the recipient's number is in E.164 format (+598) and comply with Uruguay's regulations by obtaining opt-in consent and honoring opt-out requests. Remember to handle errors gracefully and implement proper rate limiting as per provider guidelines.
Uruguay has a mature mobile market with high smartphone penetration. SMS remains important for business communication, despite WhatsApp's popularity. Antel, Movistar, and Claro are the major operators. Android devices are more common than iOS.
Most providers do not offer full two-way SMS support, impacting interactive campaigns and automated responses. This limitation is specific to the Uruguayan telecommunications infrastructure and provider capabilities.
Adhere to business hours (9:00 AM to 8:00 PM local time, UTC-3) and avoid Sundays and holidays. Limit marketing messages to 2-4 per month per recipient. Prioritize appropriate timing and respect local customs for optimal engagement.
Most Uruguayan carriers do not support alphanumeric sender IDs. They are usually overwritten with a numeric format. International long codes are supported with limitations but domestic long codes are not.
Uruguay supports concatenated SMS. Standard length limits apply (160 characters for GSM-7, 70 for UCS-2). Both encodings are supported, and messages are split automatically based on encoding used.
Process opt-out requests (STOP, BAJA, CANCELAR) within 24 hours, maintaining a database of unsubscribed numbers. Include clear opt-out instructions in every message and confirm the opt-out with a final message.
Gambling, adult content, unauthorized pharmaceutical promotions, and political campaign messages without authorization are restricted. Financial services require proper licensing. Be mindful of carrier content filtering rules.
Implement comprehensive error handling, logging errors with details like code, message, timestamp, and provider. Utilize retry logic for specific error codes, and monitor delivery rates across Antel, Movistar, and Claro.
Always use the E.164 format, which starts with +598 followed by the local number. This ensures proper routing and delivery across different carriers in Uruguay.
Twilio's rate limit is 250 messages per second, Sinch's is 30 per second, and MessageBird's is 60 per second. Implement rate limiting in your code to avoid exceeding these limits.
Obtain explicit opt-in consent, honor opt-out requests promptly, and maintain records of consent. Follow best practices and consult URSEC guidelines for compliance with consumer protection laws.
MMS is not directly supported. MMS content is converted to SMS with a URL where recipients can view the multimedia. This method ensures compatibility and still enables rich media sharing.
Number portability is not available in Uruguay. Numbers remain tied to the original carrier, simplifying routing but limiting consumer choice.
Uruguay does not support sending SMS messages to landline numbers. Attempts will result in delivery failure (error code 21614) from SMS platforms, without incurring charges.
Loading...
Uruguay SMS Best Practices, Compliance, and Features
Uruguay SMS Market Overview
Market Conditions: Uruguay has a mature mobile market with high smartphone penetration and widespread SMS usage. The country's telecommunications landscape is dominated by three major operators: Antel (state-owned), Movistar (Telef??nica), and Claro (Am??rica M??vil). While OTT messaging apps like WhatsApp are popular, SMS remains a crucial channel for business communications and authentication services. Android devices hold a significant market share advantage over iOS in the region.
Key SMS Features and Capabilities in Uruguay
Uruguay supports basic SMS functionality with some limitations on sender ID options and two-way messaging capabilities.
Two-way SMS Support
Two-way SMS is not supported in Uruguay through most providers. This limitation affects interactive messaging campaigns and automated response systems.
Concatenated Messages (Segmented SMS)
Support: Yes, concatenated messages are supported in Uruguay, though support may vary by sender ID type.
Message length rules: Standard SMS length limits apply - 160 characters for GSM-7 encoding, 70 characters for UCS-2 encoding.
Encoding considerations: Both GSM-7 and UCS-2 encodings are supported, with messages automatically split and concatenated based on the character encoding used.
MMS Support
MMS messages are not directly supported in Uruguay. Instead, MMS content is automatically converted to SMS with an embedded URL link where recipients can view the multimedia content. This ensures compatibility while still allowing rich media sharing capabilities.
Recipient Phone Number Compatibility
Number Portability
Number portability is not available in Uruguay. This means mobile numbers remain tied to their original carriers, which can simplify message routing but limits consumer flexibility.
Sending SMS to Landlines
Sending SMS to landline numbers is not supported in Uruguay. Attempts to send messages to landline numbers will result in delivery failure, typically generating a 400 response error (code 21614) from SMS platforms, with no charges incurred.
Compliance and Regulatory Guidelines for SMS in Uruguay
While Uruguay doesn't have specific SMS marketing legislation, communications are governed by general consumer protection laws and telecommunications regulations overseen by URSEC (Unidad Reguladora de Servicios de Comunicaciones). Best practices from global standards should be followed to ensure compliance.
Consent and Opt-In
Explicit Consent Requirements:
HELP/STOP and Other Commands
Do Not Call / Do Not Disturb Registries
Uruguay does not maintain an official Do Not Call registry. However, businesses should:
Time Zone Sensitivity
Uruguay observes UTC-3 time zone. While there are no strict legal restrictions on messaging hours:
Phone Numbers Options and SMS Sender Types for Uruguay
Alphanumeric Sender ID
Operator network capability: Not supported by most carriers
Registration requirements: N/A - feature not available
Sender ID preservation: Sender IDs are typically overwritten with a numeric format
Long Codes
Domestic vs. International:
Sender ID preservation: No, original sender IDs are not preserved
Provisioning time: Immediate to 24 hours for international long codes
Use cases: Transactional messages, alerts, and notifications
Short Codes
Support: Not currently supported in Uruguay
Provisioning time: N/A
Use cases: N/A
Restricted SMS Content, Industries, and Use Cases
Restricted Industries and Content:
Content Filtering
Carrier Filtering Rules:
Best Practices to Avoid Filtering:
Best Practices for Sending SMS in Uruguay
Messaging Strategy
Sending Frequency and Timing
Localization
Opt-Out Management
Testing and Monitoring
SMS API integrations for Uruguay
Twilio
Twilio provides a robust SMS API that supports messaging to Uruguay. Here's how to implement it:
Sinch
Sinch offers SMS capabilities for Uruguay through their REST API:
Bird (MessageBird)
MessageBird's API implementation for Uruguay messaging:
API Rate Limits and Throughput
When sending SMS to Uruguay, consider these limitations:
Throughput Management Strategies:
Error Handling and Reporting
Implement comprehensive error handling:
Recap and Additional Resources
Key Takeaways
Compliance Priorities:
Technical Considerations:
Best Practices:
Next Steps
Additional Resources