Locale Summary |
|
---|---|
Locale name |
Dominican Republic |
ISO code |
DO |
Region |
North America |
Dialing code |
+1829 |
Guidelines |
|
---|---|
Use Cases |
Short codes are ideal for high-throughput programmatic messaging. Short codes are approved for specific use cases, so if you are experiencing carrier filtering on long codes you may be a good candidate for short codes. Some of the most common use-cases for short codes in Dominican Republic are:
|
Restrictions |
Short codes can only message users on carriers within the countries in which they are provisioned. If your customers do not have Dominican Republic phone numbers on carrier networks that have approved that short code, you should not obtain a Dominican Republic short code. If you have customers in other countries, Twilio may be able to provision short codes in those countries. Short codes require express consent from end users before any SMS can be sent; if you cannot obtain consent you should not use a short code. Twilio and/or the carriers will not support certain types of campaigns, including:
Please note that all Dominican Republic Short Codes that we offer are FTEU (Free to End User) and the owner pays extra to send messages for which end users do not pay. Minimum term commit for Dominican Republic Short Code is 18 months. The notice period before returning the Short Code is 1 month (provided minimum term commit has been fulfilled). Refer to this article for detailed explanation on Dominican Republic Short Code Best Practices. |
Other Options |
|
Requirements |
To apply for Dominican Republic Short Code the following details are needed:
|
Timeframe |
4 weeks, once you submit all required information and documentation. |
Regulatory Bodies |
Dominican Institute of Telecommunications (INDOTEL) |
Pricing |
Click to see SMS pricing, including for short codes. |
Next Steps |
To apply for Dominican Republic Short Code please follow these steps:
|
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.