What actually changes when you send OTP, transactional or marketing A2P SMS into the Dominican Republic — separated into Dominican law, supplier route policy and what we recommend operationally.
A quick operational read on the Dominican Republic. Anything marked route-dependent is set by the supplier and operator path your traffic uses, and is confirmed during route assessment.
SMS to mobile
Carrier or route policy
Supported
Number format
Law / regulation
+1 followed by area code 809, 829 or 849 and a seven-digit subscriber number — ten national digits, and no trunk zero to remove
Alphanumeric senderID
Carrier or route policy
Dynamic alpha is not reliably preserved on common routes and may be rewritten to a random or route-assigned shortcode; selected providers describe other behaviour, so preservation is route-dependent and never promised
International numeric / longcode senderID
Carrier or route policy
Commonly overwritten with a route-assigned shortcode — preservation is not promised
Domestic longcode
Carrier or route policy
Not a generally available standard A2P sender — selected local or two-way services only
Dedicated or local shortcode
Carrier or route policy
Supported only through selected carrier or supplier programmes; availability and use case are confirmed during route assessment
Two-way SMS
Carrier or route policy
Available on selected routes and services — not a universal property of every international A2P route
Number portability
Law / regulation
Available
Concatenation
Carrier or route policy
Supported on some routes and sender types — test the exact path, because provider documentation itself qualifies support by sender type and encoding
MMS
Carrier or route policy
Some provider paths convert MMS into an SMS containing an embedded URL
SMS to fixed line
Carrier or route policy
Not supported on standard routes
Marketing
Law / regulation
Law 310-14 consent or existing-relationship, sender-identification and opt-out rules apply; Law 172-13 personal-data duties also apply
Personal data
Law / regulation
Law 172-13 requires lawful, purpose-limited and informed handling and gives access, opposition and removal or blocking rights, with specific direct-marketing provisions
Last reviewed
Flowstates recommendation
1 August 2026
Route-dependent: “Route-dependent” means the behaviour is decided by the supplier and operator path your traffic takes, not by Dominican statute. Provider documentation for the Dominican Republic openly disagrees on senders and two-way support, and a route can change its policy. Confirm before launch.
Law, route policy and recommendation
Dominican statute, supplier route behaviour and our own operating standard are three different things. Every statement on this page is labelled so the right team can act on it.
Law / regulation
Law and regulation
Binding obligations from Dominican legislation and the sector authorities: the Instituto Dominicano de las Telecomunicaciones (INDOTEL) as telecom regulator, NANPA as the numbering authority for area codes 809, 829 and 849, Law 310-14 on unsolicited commercial electronic communications and Law 172-13 on personal-data protection. These apply whichever supplier you use.
Carrier or route policy
Carrier or route policy
Rules applied by operators, aggregators or your provider on the specific A2P path your traffic takes — sender rewriting, whether a brand or international number survives, whether replies are possible, concatenation behaviour, Unicode handling and MMS conversion. Route-dependent, subject to change, and described differently by different providers.
Flowstates recommendation
Flowstates operational recommendation
What we ask customers to do because it protects deliverability and keeps you comfortably inside both the law and route policy — including a conservative permission and suppression standard for promotional SMS even where the law recognises an existing-relationship basis.
Numbering and networks
The basics your validation layer and templates need to get right before the first send.
Law / regulationNumber format
The Dominican Republic is part of the North American Numbering Plan and uses country calling code +1 with three overlay area codes — 809, 829 and 849 — followed by a seven-digit subscriber number. Domestic dialling uses all ten digits, and there is no trunk zero to remove. Summaries that show only one area code are incomplete.
Law / regulationDialling code
Country calling code +1 under the NANP. Mobile country code 370.
Law / regulationNumbering administration
NANPA is the authority for the three Dominican area codes, so area-code questions are settled against NANPA material rather than provider documentation. INDOTEL is the national telecommunications regulator.
Law / regulationNumber portability
Number portability is available in the Dominican Republic, so a number can be held by an operator other than the one that originally received the range.
Flowstates recommendationPortability handling
Run a live mobile or current-operator lookup rather than inferring the network from the area code or the original number block. Do not infer mobile versus fixed service from the area code either — all three overlay codes cover the whole country.
Carrier or route policyNetworks
The current major consumer mobile networks to plan for are Claro, Altice and Viva (Trilogy). We publish no market-share figures and no guarantee that a given supplier reaches every network equally — that is validated per route.
Flowstates recommendationValidation
Validate to E.164, keep all ten national digits, and run mobile validation or lookup before sending. Standard A2P SMS should target mobile destinations, so validate fixed-line destinations out.
Country code 1, then one of the three overlay area codes and the seven-digit subscriber number — ten national digits in total, with no trunk zero. These are masked illustrative patterns, not real subscriber numbers.
SenderID options
Provider documentation for the Dominican Republic materially disagrees. One major provider states that dynamic alphanumeric senderIDs are not fully supported by Dominican mobile operators and may be overwritten with a random shortcode outside its platform, and that dynamic numeric senders may be overwritten in the same way. Other provider pages describe materially different sender and two-way capabilities. Treat sender presentation as route-dependent, never promise preservation, and design the message body so it still identifies your brand when the visible sender changes.
Carrier or route policy
This whole comparison — best for, what the recipient sees and replies — describes carrier or route behaviour on current A2P paths into the Dominican Republic, not Dominican statute. Suppliers describe this market differently, behaviour varies by operator and route, and it is validated live before launch rather than guaranteed universally.
Rewritten international A2P sender
Best for
Fast launch of one-way OTP and transactional traffic where numeric rewriting is accepted
What the recipient sees
A route-assigned or random shortcode rather than the submitted alpha or international number
Replies
Not assumed
Submitted alphanumeric senderID on a validated route
Best for
One-way branded traffic only where the selected supplier and operator path confirms preservation
What the recipient sees
The submitted brand where it is preserved; otherwise a rewritten shortcode
Replies
No
Provider-assigned local numeric / two-way sender
Best for
Selected service, support and conversational use cases
What the recipient sees
The numeric sender assigned to that service
Replies
Potentially available only when explicitly configured
Dedicated or local shortcode
Best for
Selected scale programmes requiring a consistent numeric identity
What the recipient sees
The approved or supported shortcode
Replies
Route- and programme-dependent
SenderID options
Option
Best for
What the recipient sees
Replies
Rewritten international A2P sender
Fast launch of one-way OTP and transactional traffic where numeric rewriting is accepted
A route-assigned or random shortcode rather than the submitted alpha or international number
Not assumed
Submitted alphanumeric senderID on a validated route
One-way branded traffic only where the selected supplier and operator path confirms preservation
The submitted brand where it is preserved; otherwise a rewritten shortcode
No
Provider-assigned local numeric / two-way sender
Selected service, support and conversational use cases
The numeric sender assigned to that service
Potentially available only when explicitly configured
Dedicated or local shortcode
Selected scale programmes requiring a consistent numeric identity
The approved or supported shortcode
Route- and programme-dependent
Put a meaningful brand and the purpose in the message body, because sender presentation can change on the way to the handset. Do not rely on a reply unless an inbound-capable sender or service is expressly configured. Generic sender identities may be filtered on some paths, so we recommend a recognisable brand — that is route policy and a Flowstates recommendation, not Dominican statute. A selected sender or shortcode programme may need route assessment before it can be used.
What changes by traffic type
The same destination behaves differently depending on the category you send and the route it takes.
OTP / authentication
Suitable on validated high-quality routes.
Flowstates recommendation
Keep the copy purely transactional and concise, and within a single segment wherever practical.
Flowstates recommendation
Put the brand in the message body, because the visible sender may be rewritten.
Flowstates recommendation
No promotional content in OTP templates.
Flowstates recommendation
Use a branded link domain rather than a public or shared shortener.
Flowstates recommendation
Monitor delivery, latency, completed-verification conversion and current operator or route performance.
Flowstates recommendation
Configure carrier-grade failover so a degraded path does not become a failed login queue.
Carrier or route policy
Do not design authentication around replies unless a two-way sender or service is explicitly configured.
Transactional / service
Suitable for alerts, confirmations and account or service updates.
Flowstates recommendation
Identify the brand and state the purpose of the message clearly.
Flowstates recommendation
Use a branded domain for links.
Flowstates recommendation
Keep promotional copy out of transactional templates.
Carrier or route policy
Test any concatenation on the exact route and sender type before relying on it, because support is qualified by sender type and encoding.
Carrier or route policy
Enable replies only where an inbound-capable service is configured.
Flowstates recommendation
Do not relabel promotional messaging as transactional.
Marketing / promotional
Law 310-14 controls, Law 172-13 duties and a conservative Flowstates permission standard.
Law / regulation
Law 310-14 regulates unsolicited commercial, advertising and promotional electronic communications and includes specific requirements for communications sent from mobile devices.
Law / regulation
It generally prohibits unsolicited or unconsented commercial communications, but recognises an exception where the recipient has or had a prior commercial relationship with the initiator and has not opted out, as well as where the recipient consented to or authorised the communication.
Law / regulation
For a mobile-originated commercial communication, identify the initiator by name or legal name and number, and provide a valid active phone number, email address or internet-based mechanism through which the recipient can state that they do not want further commercial communications.
Law / regulation
Stop sending after an opt-out and keep the stated response mechanism operational.
Law / regulation
Do not use misleading or fraudulent sender or content information.
Law / regulation
Law 172-13 personal-data duties apply to the underlying marketing data in parallel with Law 310-14.
Flowstates recommendation
Flowstates launch standard: retain timestamped, source-attributed, purpose-specific and SMS-channel-specific permission for promotions, unless qualified Dominican counsel documents a valid existing-relationship basis and the route accepts it.
Flowstates recommendation
Support natural Spanish opt-out requests such as BAJA, SALIR, CANCELAR and NO. We do not claim that one exact keyword is universally mandated.
Flowstates recommendation
Maintain cross-system suppression and do-not-disturb records so an opt-out applies everywhere you send from.
Flowstates recommendation
Do not use purchased lists.
Flowstates recommendation
Schedule promotions inside recipient-local daytime hours. That is our operational recommendation, not a statutory campaign-hours window.
Carrier or route policy
Use the agreed promotional route — category acceptance is confirmed privately during route assessment.
Dominican consent, anti-spam and personal-data rules
Two separate Dominican laws matter for SMS, and they answer different questions. Law 310-14 governs the commercial communication itself. Law 172-13 governs the personal data behind it. Neither is the same as your provider's route policy.
Law / regulation
Law 310-14 covers unsolicited commercial, advertising and promotional electronic communications and contains specific requirements for communications sent from mobile devices.
Law / regulation
Consent is not the only permitted route under Law 310-14: the law also recognises a prior commercial relationship with the initiator where no opt-out has intervened.
Law / regulation
Sender identity and a functioning way to stop further commercial communications are required — a name or legal name and number, plus a valid active phone number, email address or internet-based mechanism to refuse further messages.
Flowstates recommendation
The law's email-specific labelling requirements stay scoped to email. Do not import an email subject-line label into an SMS body; apply the mobile-device requirements to SMS instead.
Law / regulation
Law 172-13 generally requires free, express and informed consent, recorded in writing or an equivalent form, for the processing and transmission of personal data, subject to the exceptions the law provides.
Law / regulation
Data subjects must be clearly informed about the purpose, the recipients or categories of recipients, the consequences, the controller's identity and address, and their rights.
Law / regulation
Personal data must be relevant, appropriate and accurate, used only for compatible purposes, kept secure and not retained longer than necessary.
Law / regulation
Data subjects have access, rectification, opposition and deletion or destruction rights in the circumstances the law provides.
Law / regulation
Article 71 of Law 172-13 adds direct-marketing nuance: marketing entities may use data taken from documents of unrestricted public access, data supplied by the data subject, or data used with the subject's consent. At the subject's request the source of the data must be identified, and the subject can request removal or blocking — including retention of the minimal suppression data needed to avoid future unwanted advertising.
Flowstates recommendation
Because of Article 71, do not state that consent is always the only lawful basis for Dominican marketing data. Describe the basis you actually rely on and keep the evidence for it.
Flowstates recommendation
We still apply a conservative permission, notice, minimisation, retention, security, objection and suppression standard to promotional SMS, whichever basis is documented.
Flowstates recommendation
Keep OTP and service purposes and templates operationally separate from marketing purposes and templates.
Flowstates recommendation
Retain the privacy-notice version, the purpose, the data source, the permission or documented relationship basis, opt-out and objection handling, suppression records, campaign records and processing evidence.
Operational compliance checklist
What we expect to be in place before Dominican traffic goes live, and to stay in place afterwards.
Flowstates recommendation
Record the source, purpose and permitted use of every recipient record.
Law / regulation
Provide clear Law 172-13 information to data subjects and retain the version of the notice that was shown.
Flowstates recommendation
For promotions, retain the recipient, timestamp, source, exact wording and version, purpose and SMS-channel permission — or document a counsel-approved existing-relationship basis.
Law / regulation
Identify the brand, the initiator and the purpose of the message.
Law / regulation
Provide a valid, active and straightforward free way to stop commercial messaging, and keep that mechanism working.
Flowstates recommendation
Support BAJA, SALIR, CANCELAR and NO without claiming a universal keyword mandate.
Flowstates recommendation
Suppress promptly and across every sending system, not just the one that received the request.
Law / regulation
Keep the minimal suppression data needed to prevent future unwanted advertising.
Law / regulation
Identify the source of marketing data when a data subject validly requests it.
Law / regulation
Honour access, rectification, opposition and removal or blocking requests.
Flowstates recommendation
Do not use purchased lists.
Flowstates recommendation
Schedule campaigns by Dominican recipient-local daytime.
Flowstates recommendation
Keep OTP, transactional and marketing templates operationally distinct.
Flowstates recommendation
Use a branded short domain for links.
Carrier or route policy
Validate the exact senderID, use case, current operator and route before launch.
Carrier or route policy
Test concatenation and Unicode on the exact path you will send on.
Carrier or route policy
Confirm category acceptance privately with us during route assessment.
Flowstates recommendation
Retain template, notice, basis or permission, opt-out, campaign, suppression and route-approval records.
Encoding and delivery
Spanish copy changes segment maths more often than teams expect, and the Dominican route mix rewards testing the real path.
GSM-7 single message
160 characters
GSM-7 concatenated
153 characters per segment
Unicode / UCS-2 single message
70 characters
Unicode / UCS-2 concatenated
67 characters per segment
Flowstates recommendation
Spanish accents, smart punctuation, emoji and text pasted from a document can switch a message to Unicode and change the segment count without anyone editing the copy.
Carrier or route policy
Provider documentation marks UCS-2 as supported on dynamic alphanumeric and international numeric routes, but behaviour is still route-specific — test the final Spanish copy end to end.
Carrier or route policy
Test concatenation on the actual sender type and on the Claro, Altice and Viva paths you have purchased.
Law / regulation
Use the full ten national digits: +1 809 XXX XXXX, +1 829 XXX XXXX or +1 849 XXX XXXX. Domestic dialling is ten digits and there is no trunk zero to remove.
Flowstates recommendation
Run a mobile or current-operator lookup before sending, because portability is active and the area code identifies neither the current network nor the service type.
Flowstates recommendation
Validate fixed-line destinations out — standard routes do not deliver to them.
Carrier or route policy
Treat MMS-to-SMS-with-URL conversion as route policy, and check whether your path does it before designing around media.
A country guide is only useful when the route follows it.
Knowing that a sender may be rewritten or that a marketing message needs a working opt-out only helps if the operations layer enforces it on the live path. That is the part we run.
Per-country, per-category routing
OTP, transactional and promotional Dominican traffic can take different vendors and different routes, with the policy applied per category rather than per account.
SenderID management
We manage the sender arrangements each route actually supports, and design templates that still identify you when the visible sender is rewritten.
Carrier-grade failover
A degraded Dominican path fails over rather than queueing your logins behind it.
Per-route visibility
Delivery, latency and OTP-conversion reporting by route, so a change in behaviour is visible before your support queue notices.
24/7 vendor escalation
We chase the supplier and the operator path when Dominican delivery moves, in your name.
BYOV / BYOG
Keep your own vendor or gateway contracts and let us operate them, or use ours.
Branded short links
Branded link domains instead of public shorteners, which matters more when the sender itself may be rewritten.
Frequently asked questions about SMS in Dominican Republic
Can I send SMS to mobile numbers in Dominican Republic?
A quick operational read on the Dominican Republic. Anything marked route-dependent is set by the supplier and operator path your traffic uses, and is confirmed during route assessment. SMS to mobile: Supported. Number format: +1 followed by area code 809, 829 or 849 and a seven-digit subscriber number — ten national digits, and no trunk zero to remove. Alphanumeric senderID: Dynamic alpha is not reliably preserved on common routes and may be rewritten to a random or route-assigned shortcode; selected providers describe other behaviour, so preservation is route-dependent and never promised. International numeric / longcode senderID: Commonly overwritten with a route-assigned shortcode — preservation is not promised.
Which sender ID options work for SMS in Dominican Republic?
Provider documentation for the Dominican Republic materially disagrees. Rewritten international A2P sender — Best for: Fast launch of one-way OTP and transactional traffic where numeric rewriting is accepted. Submitted alphanumeric senderID on a validated route — Best for: One-way branded traffic only where the selected supplier and operator path confirms preservation. Provider-assigned local numeric / two-way sender — Best for: Selected service, support and conversational use cases. Dedicated or local shortcode — Best for: Selected scale programmes requiring a consistent numeric identity.
What are the consent and opt-out requirements for SMS in Dominican Republic?
Two separate Dominican laws matter for SMS, and they answer different questions. Law 310-14 covers unsolicited commercial, advertising and promotional electronic communications and contains specific requirements for communications sent from mobile devices. Consent is not the only permitted route under Law 310-14: the law also recognises a prior commercial relationship with the initiator where no opt-out has intervened. Sender identity and a functioning way to stop further commercial communications are required — a name or legal name and number, plus a valid active phone number, email address or internet-based mechanism to refuse further messages.
How many characters fit in an SMS to Dominican Republic?
Spanish copy changes segment maths more often than teams expect, and the Dominican route mix rewards testing the real path. GSM-7 single message: 160 characters. GSM-7 concatenated: 153 characters per segment. Unicode / UCS-2 single message: 70 characters. Unicode / UCS-2 concatenated: 67 characters per segment.
Sources and change control
Numbering wording follows NANPA. Law 310-14 and Law 172-13 wording follows official Dominican law and government sources. Telecom-regulator wording follows INDOTEL. Provider pages describe only their own route behaviour, and where they conflict we keep the language route-dependent.
States that dynamic alphanumeric and dynamic numeric senderIDs may be overwritten with a random shortcode, lists two-way SMS and portability, qualifies concatenation by sender type and encoding, notes MMS converted to SMS with a URL, and marks landline SMS unsupported.
Additional provider coverage reference for the Dominican Republic.
Change log
1 August 2026 — Initial publication; corrected the incomplete single-area-code summary and separated Law 310-14, Law 172-13 and live sender-route behaviour.
Last reviewed: 1 August 2026
Disclaimer
This is operational guidance, not legal advice. Requirements vary by operator, supplier route, senderID, traffic category, legal basis, message purpose and customer setup. Flowstates confirms the live path during onboarding.
