What actually changes when you send OTP, transactional or marketing A2P SMS into Ecuador — separated into Ecuadorian law, supplier route policy and what we recommend operationally.
Last reviewed: 1 August 2026 · South America / LATAM
A quick operational read on Ecuador. 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
+593 followed by a nine-digit mobile number beginning with 9 — the domestic trunk zero is removed
Alphanumeric senderID
Carrier or route policy
Common routes rewrite it to a local shortcode or longcode; selected CNT paths may preserve it, so presentation is operator- and route-dependent
International numeric / longcode senderID
Carrier or route policy
Commonly overwritten with a local shortcode or longcode — preservation is not promised
Local numeric / two-way sender
Carrier or route policy
Selected services only; not a default international A2P capability
Dedicated or local shortcode
Carrier or route policy
Selected carrier or supplier programmes only
Two-way SMS
Carrier or route policy
Standard international routes are commonly one-way — do not assume replies
Number portability
Law / regulation
Available — never infer the current operator from the original range
Concatenation
Carrier or route policy
Not dependable across all routes: Movistar may deliver only the first segment and some providers mark concatenation unsupported
MMS
Carrier or route policy
Some provider paths convert MMS to an SMS containing a URL
SMS to fixed line
Carrier or route policy
Not supported on standard routes
Marketing
Law / regulation
Prior and express authorisation or acceptance under the telecommunications law, plus data-protection notice, opposition or withdrawal, opt-out and suppression controls
Direct marketing
Law / regulation
The data subject may object at any time under the LOPDP, and processing for that purpose must stop
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 Ecuadorian statute. Two providers can behave differently on the same day, and a route can change its policy. Confirm before launch.
Law, route policy and recommendation
Ecuador's telecommunications rules, its personal-data framework, supplier route behaviour and our own operating standard are 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 Ecuadorian legislation and regulators: the Ley Orgánica de Telecomunicaciones prior and express authorisation rule for commercial messaging, the ARCOTEL technical framework and its narrow informational-message exceptions, ARCOTEL numbering and portability, and the Ley Orgánica de Protección de Datos Personales with its General Regulation. 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 — senderID rewriting, whether the CNT alphanumeric exception applies, whether replies are possible, concatenation behaviour and MMS handling. Route-dependent and subject to change.
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. Deliberately stricter than the legal minimum.
Numbering and networks
The basics your validation layer and templates need to get right before the first send.
Law / regulationNumber format
Ecuadorian mobile subscriber numbers use nine national digits after the country code and begin with 9. Domestically the same number is written with a leading trunk zero, which is removed in E.164.
Law / regulationDialling code
Country dialling code +593. Mobile country code 740.
Law / regulationNumbering administration
ARCOTEL regulates telecommunications and administers the numbering plan and numeric series, so numbering questions are settled against ARCOTEL material rather than provider documentation.
Law / regulationNumber portability
Mobile number portability is available and has operated since 2009. Never infer the current operator from the original number range or prefix.
Carrier or route policyNetworks
The large mobile networks to plan for are Claro, Movistar and CNT. Tuenti is associated with the Movistar / OTECEL network rather than a separate national production route for this guide. The current operator is resolved by live lookup at send time, and we publish no market shares or route-coverage claims here.
Flowstates recommendationValidation
Validate to E.164 and run mobile validation or lookup before sending. Standard A2P SMS routes target mobile destinations, and fixed-line destinations should be validated out.
Flowstates recommendationPortability handling
Because portability is active, resolve the current operator at send time instead of caching an operator against a contact record.
E.164 example
+593 9X XXX XXXX
Country code 593, then the nine-digit mobile number beginning with 9. Domestically the same pattern is written 09X XXX XXXX, and that trunk zero is removed in E.164. This is a masked illustrative pattern, not a real subscriber number.
SenderID options
In Ecuador the submitted sender is commonly rewritten to a route-assigned local shortcode or longcode, with selected CNT paths reported as able to maintain an alphanumeric sender. Provider documentation does not fully agree, so treat preservation as route-dependent and never promise it. 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 in Ecuador, not Ecuadorian statute. Providers describe Ecuador differently, behaviour varies by supplier and operator, and it is validated live before launch rather than guaranteed universally.
Submitted alphanumeric senderID
Best for
One-way OTP, transactional and authorised marketing where numeric rewriting is accepted; selected CNT paths may preserve the brand
What the recipient sees
Usually a route-assigned local shortcode or longcode; the submitted brand only on selected supporting paths
Replies
No
International longcode
Best for
Selected one-way transactional or service traffic where the route accepts numeric sender submission
What the recipient sees
Commonly a route-assigned local shortcode or longcode rather than the submitted international number
Replies
Do not assume — only where an expressly selected service supports inbound SMS
Provider-assigned local numeric sender
Best for
Selected service, support or conversational use cases
What the recipient sees
The local numeric sender assigned to that service
Replies
Potentially available only when explicitly configured
Dedicated or local shortcode
Best for
Selected scale programmes and a stable numeric identity
What the recipient sees
The supported shortcode where the carrier or supplier programme is available
Replies
Route- and programme-dependent
SenderID options
Option
Best for
What the recipient sees
Replies
Submitted alphanumeric senderID
One-way OTP, transactional and authorised marketing where numeric rewriting is accepted; selected CNT paths may preserve the brand
Usually a route-assigned local shortcode or longcode; the submitted brand only on selected supporting paths
No
International longcode
Selected one-way transactional or service traffic where the route accepts numeric sender submission
Commonly a route-assigned local shortcode or longcode rather than the submitted international number
Do not assume — only where an expressly selected service supports inbound SMS
Provider-assigned local numeric sender
Selected service, support or conversational use cases
The local numeric sender assigned to that service
Potentially available only when explicitly configured
Dedicated or local shortcode
Selected scale programmes and a stable numeric identity
The supported shortcode where the carrier or supplier programme is available
Route- and programme-dependent
Put a meaningful brand and the purpose in the message body, because the visible sender can change. Generic sender identifiers may be filtered on some provider paths, so we recommend a recognisable brand — that is route policy and a Flowstates recommendation, not an Ecuadorian statute. Provider-assigned local numeric or two-way services exist only where expressly offered, and dedicated shortcodes only through selected carrier or supplier programmes.
What changes by traffic type
Ecuador is not one rulebook. 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 senderID is commonly rewritten.
Flowstates recommendation
No promotional content in OTP templates.
Flowstates recommendation
Use a branded domain for any link and avoid ambiguous link text.
Flowstates recommendation
Monitor delivery, latency, completed-verification conversion and current-operator performance.
Flowstates recommendation
Configure carrier-grade failover so a degraded path does not become a failed login queue.
Carrier or route policy
Do not rely on concatenation for OTP. Movistar may deliver only the first segment of a concatenated SMS on some routes.
Carrier or route policy
Standard international A2P routes into Ecuador are generally one-way. Do not build a verification flow around replies unless a two-way 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 rather than a public or shared shortener.
Flowstates recommendation
Keep promotional content out of transactional templates.
Flowstates recommendation
Prefer a single segment, and test any necessary concatenation on the selected senderID and operator route before relying on it.
Carrier or route policy
Enable replies only on an explicitly configured two-way service. Inbound handling is not a default on Ecuadorian A2P paths.
Law / regulation
Keep the legal distinction between a genuinely informational or service message and commercial promotion. Do not relabel marketing as transactional to avoid the prior-authorisation rule.
Marketing / promotional
Prior and express authorisation, clear privacy information, a free way to stop and prompt suppression.
Law / regulation
Article 22(24) of the Ley Orgánica de Telecomunicaciones gives users the right not to receive mass or individual messages or calls for direct sale, commercial, advertising or proselytising purposes unless they have previously and expressly authorised them.
Law / regulation
Article 23(8) also obliges users and subscribers not to send direct-sale, commercial, advertising or proselytising messages that have not been previously accepted by the recipient.
Flowstates recommendation
Treat that as a channel-specific prior-authorisation rule. We require timestamped, source-attributed, purpose-specific and channel-specific evidence for every promotional send.
Law / regulation
The ARCOTEL technical framework contains narrow informational-message exceptions, including certain service-related messages from a telecommunications provider to its own subscribers, authorised public, financial or educational communications within their competence, and emergency alerts. Those are narrow and purpose-specific.
Flowstates recommendation
Do not turn those exceptions into a blanket exemption for every business-labelled “transactional” SMS. Document the purpose and obtain legal review before relying on one.
Law / regulation
Under the LOPDP, where consent is the basis it must be free, specific, informed and unequivocal, and the data subject has the right to object at any time to processing for direct marketing, after which the data must stop being processed for that purpose.
Flowstates recommendation
Provide a simple and free opt-out in every promotional SMS and suppress promptly.
Flowstates recommendation
Support natural Spanish requests such as BAJA, SALIR, CANCELAR and NO. We do not claim any one keyword is universally mandated by statute.
Flowstates recommendation
We do not claim a national do-not-call registry for SMS unless a current authoritative source supports it. Maintain an internal suppression and do-not-disturb list regardless.
Flowstates recommendation
Schedule in recipient-local daytime as our operating recommendation, not an invented statutory campaign-hours window. A selected route may impose a stricter window, which we confirm privately.
Flowstates recommendation
Do not use purchased lists.
Carrier or route policy
Use the promotional route agreed for the traffic; category acceptance is confirmed privately for the selected route rather than published as a general list.
Ecuador's prior-authorisation, data-protection and direct-marketing rules
Ecuador combines a channel-specific telecommunications rule on commercial messaging with a general personal-data framework. They are separate obligations, and the nuance decides whether a campaign is compliant.
Law / regulation
The Ley Orgánica de Telecomunicaciones creates a specific prior and express authorisation or acceptance requirement for direct-sale, commercial, advertising and proselytising messages. That is stronger and more channel-specific than a generic privacy-policy statement.
Law / regulation
The ARCOTEL informational-message exceptions are narrow and purpose-specific. Do not claim every OTP, account alert or service message is automatically exempt — document the purpose and the applicable basis.
Law / regulation
The Ley Orgánica de Protección de Datos Personales was published in May 2021. Its General Regulation was issued by Executive Decree 904 and published in November 2023.
Law / regulation
Personal-data processing must have a lawful basis and comply with purpose, transparency and data-subject rights. Where consent is relied on, it must be free, specific, informed and unequivocal.
Law / regulation
Where personal data is processed for direct marketing, including related profiling, the data subject may object at any time, and the data must then stop being processed for that purpose.
Flowstates recommendation
A direct opt-out or withdrawal must be honoured promptly, whether or not the recipient appears on any external list.
Flowstates recommendation
Do not claim every OTP or service notification is marketing. Keep purpose and template categories separate, and keep promotional copy out of transactional and verification messages.
Law / regulation
The Superintendencia de Protección de Datos Personales (SPDP) is the current data-protection authority, while ARCOTEL regulates telecommunications, numbering, user rights and portability. Keep those roles distinct.
Flowstates recommendation
We deliberately do not reproduce internal compliance forms, fees or administrative process detail. Verify current obligations directly against current SPDP and ARCOTEL sources.
Law / regulation
ARCOTEL's 2020 commercial-call identification and masking rules are call-specific. They are not an SMS senderID-registration regime and must not be treated as one.
Flowstates recommendation
Retain the privacy notice and its version, the purpose, the consent or authorisation record, any opposition or withdrawal, and evidence of how the data was processed.
Carrier or route policy
Some content or use-case categories, including P2P-style use, can be restricted by provider policy. That is route policy confirmed per campaign, not a published Ecuadorian statutory category list.
Operational compliance checklist
What we expect to see in place before an Ecuador route goes live.
Law / regulation
Record the source, the lawful basis or purpose and the permitted use of every recipient record.
Law / regulation
Provide the applicable privacy information and retain the version shown to the recipient.
Flowstates recommendation
For promotions, retain recipient, timestamp, source, exact wording or version, purpose and SMS-channel authorisation.
Law / regulation
Document which ARCOTEL or telecommunications-law category the communication belongs to, and obtain legal review before relying on an informational exception.
Flowstates recommendation
Identify the brand and the purpose in every message.
Law / regulation
For direct marketing, provide a working, simple and free method to stop the communications.
Flowstates recommendation
Support BAJA, SALIR, CANCELAR and NO without claiming a universal statutory keyword.
Flowstates recommendation
Suppress promptly and maintain an internal suppression and do-not-disturb list across all systems.
Flowstates recommendation
Do not use purchased lists.
Flowstates recommendation
Schedule by Ecuador recipient-local daytime.
Flowstates recommendation
Classify OTP, transactional or informational and marketing templates, and keep promotional copy out of OTP and service messages.
Flowstates recommendation
Use a branded short domain rather than a public or shared URL shortener.
Carrier or route policy
Keep critical templates to one segment unless the exact route has passed concatenation testing.
Carrier or route policy
Validate the exact senderID, use case and route before launch.
Carrier or route policy
Confirm category acceptance privately for the selected route, rather than relying on a published category list.
Flowstates recommendation
Keep template, privacy, authorisation, opt-out, campaign, suppression and route-approval records.
Encoding and delivery
Spanish copy makes encoding a real cost and delivery question in Ecuador, and concatenation is not dependable across every route. Test the exact path rather than trusting a generic table.
GSM-7, single segment
160 characters
GSM-7, concatenated
153 characters per segment
Unicode / UCS-2, single segment
70 characters
Unicode / UCS-2, concatenated
67 characters per segment
Flowstates recommendation
Spanish accents, smart punctuation, emoji and formatting pasted from a document can change the encoding, which shortens the segment and changes the segment count. Check the encoding your template actually produces.
Carrier or route policy
Concatenation is not dependable across all Ecuador routes. One provider notes that Movistar may deliver only the first segment, and another marks concatenation unsupported on its ordinary route. Test the exact path.
Flowstates recommendation
Keep OTP and critical-service templates to a single segment, and run end-to-end testing across the purchased Claro, Movistar and CNT routes.
Flowstates recommendation
Normalise to E.164 as +593 9X XXX XXXX — domestically the same number appears as 09X XXX XXXX and the trunk zero is removed — then run mobile validation or lookup before sending. Fixed and mobile destinations need different handling, standard routes do not deliver to fixed lines, and portability is active so the original range tells you nothing reliable about the current operator.
Carrier or route policy
Some provider paths convert an MMS into an SMS containing a URL. That is route policy, not an Ecuadorian rule.
A country guide is only useful when the route follows it.
Knowing Ecuador's rules is the easy half. Keeping every send inside them, on supplier routes that describe Ecuador differently and change their policy, is the operational half — that is the part we run.
Per-country and per-category routing
OTP, transactional and marketing traffic take different Ecuador routes, with the right policy applied to each category.
SenderID management
We manage sender presentation where a route supports it, including selected CNT behaviour, and design templates for the common case where the sender is rewritten to a local numeric one.
Carrier-grade failover
When an Ecuador route degrades, traffic moves before your verification funnel does.
Per-route visibility
Delivery, latency and OTP conversion measured per route and per operator, so a route policy change shows up as data rather than complaints.
24/7 vendor escalation
We chase the supplier and the carrier. You get the update, not the ticket queue.
BYOV / BYOG
Keep your existing supplier and contracts and let us operate the routing, or use ours.
Branded short links
Links on your own domain instead of a shared shortener, which route filters treat very differently.
A quick operational read on Ecuador. 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: +593 followed by a nine-digit mobile number beginning with 9 — the domestic trunk zero is removed. Alphanumeric senderID: Common routes rewrite it to a local shortcode or longcode; selected CNT paths may preserve it, so presentation is operator- and route-dependent. International numeric / longcode senderID: Commonly overwritten with a local shortcode or longcode — preservation is not promised.
Which sender ID options work for SMS in Ecuador?
In Ecuador the submitted sender is commonly rewritten to a route-assigned local shortcode or longcode, with selected CNT paths reported as able to maintain an alphanumeric sender. Submitted alphanumeric senderID — Best for: One-way OTP, transactional and authorised marketing where numeric rewriting is accepted; selected CNT paths may preserve the brand. International longcode — Best for: Selected one-way transactional or service traffic where the route accepts numeric sender submission. Provider-assigned local numeric sender — Best for: Selected service, support or conversational use cases. Dedicated or local shortcode — Best for: Selected scale programmes and a stable numeric identity.
What are the consent and opt-out requirements for SMS in Ecuador?
Ecuador combines a channel-specific telecommunications rule on commercial messaging with a general personal-data framework. The Ley Orgánica de Telecomunicaciones creates a specific prior and express authorisation or acceptance requirement for direct-sale, commercial, advertising and proselytising messages. That is stronger and more channel-specific than a generic privacy-policy statement. The ARCOTEL informational-message exceptions are narrow and purpose-specific. Do not claim every OTP, account alert or service message is automatically exempt — document the purpose and the applicable basis. The Ley Orgánica de Protección de Datos Personales was published in May 2021. Its General Regulation was issued by Executive Decree 904 and published in November 2023.
How many characters fit in an SMS to Ecuador?
Spanish copy makes encoding a real cost and delivery question in Ecuador, and concatenation is not dependable across every route. GSM-7, single segment: 160 characters. GSM-7, concatenated: 153 characters per segment. Unicode / UCS-2, single segment: 70 characters. Unicode / UCS-2, concatenated: 67 characters per segment.
Sources and change control
Regulator, statute and provider references behind this guide. Provider documentation reflects a supplier's current route policy, not Ecuadorian law — official ARCOTEL sources control numbering, portability, telecom consent and informational exceptions, and official LOPDP, Registro Oficial and SPDP sources control personal-data wording. ARCOTEL's call-identification process is not imported into SMS sender guidance, and where providers disagree we use route-dependent language rather than picking a winner.
One supplier's current route policy: alphanumeric submission generally unsupported except dynamic alphanumeric senderIDs on CNT Mobile, international numeric senders overwritten with a shortcode or longcode, standard two-way unsupported, MMS possibly converted to SMS with a URL, fixed-line unsupported, and Movistar possibly delivering only the first segment of a concatenated SMS.
Official evidence that mobile number portability operates in Ecuador, so the current operator must be resolved by lookup rather than inferred from the range.
Official statement of the user right not to receive commercial, advertising or proselytising messages without prior express authorisation, and the matching user obligation.
Source for the narrow informational-message exceptions. The 2020 commercial-call identification and masking rules are call-specific and are not an SMS senderID-registration regime.
States that alphanumeric senderIDs are overwritten with a random local longcode or shortcode, except on CNT where an alphanumeric sender can be maintained dynamically.
States that alphanumeric and numeric senderIDs are changed to a random shortcode and that generic identifiers can be prohibited on its route. Its exact content windows and detailed category restrictions are provider policy, not Ecuadorian statute, and are not reproduced here.
States that senderIDs are replaced with local or random numeric numbers, and that two-way SMS and concatenation are not supported on its ordinary Ecuador coverage.
Evidence that supplier product descriptions differ: some advertise one-way alphanumeric coverage for Ecuador, which conflicts with country-specific route pages. We therefore never promise sender preservation.
Change log
1 August 2026 — Initial draft; separated Ecuador's prior-authorisation and data-protection requirements from live sender rewriting, CNT exceptions and concatenation behaviour.
Last reviewed 1 August 2026
Disclaimer
This is operational guidance, not legal advice. Applicable requirements vary by operator, route, senderID, traffic category, message purpose and customer configuration. Flowstates confirms the live path during onboarding.
