Paraguay SMS Guide: A2P Senders & Consent

At a glance

A quick operational read on Paraguay. Anything marked route-dependent is decided by the supplier and operator path your traffic uses. Anything marked law applies whichever supplier you pick.

SMS to mobile: Supported on selected contracted A2P routes
Number format: +595 followed by the nine national mobile digits; the domestic trunk zero is removed when normalising to E.164
Number validation: Confirm the destination is Paraguayan, messaging-capable mobile and resolve the current operator before sending
Number portability: Available — CONATEL confirms mobile portability has operated since 30 November 2012 and the subscriber keeps the number, including the prefix
Provider portability summary: Twilio's current Paraguay country table still says number portability is unavailable; that summary is out of date against CONATEL
Seven-digit A2P origin numbering: CONATEL Resolución Directorio 2431/2024 establishes a seven-digit origin numbering format for A2P SMS within the national numbering plan, for national and international A2P traffic
Visible sender presentation: Route-assigned, preserved or replaced according to the selected provider and operator path
Sender confirmation: Confirm the actual visible sender before launch
Alphanumeric sender: Not supported on one major provider's current Paraguay route
Domestic long code: Paraguayan domestic long codes are not supported on that provider's current route
International numeric sender: Can terminate on that provider's route but is not preserved; expect a route-assigned replacement such as a local short code or long code
Dedicated short code: Operator-capable in Paraguay, but not offered by that provider's current Paraguay route
Two-way SMS: Not supported on that provider's current route
Inbound programmes: Treat any inbound requirement as unavailable until it is explicitly confirmed and tested on the path you buy
Concatenation: Supported on that provider and on selected routes, with sender and encoding qualifications
Unicode / UCS-2: Listed as unsupported on that provider's international long code row for Paraguay
Encoding validation: Test your real Spanish and Guaraní copy, and its real segment count, on the exact route before launch
MMS: That provider converts MMS into an SMS containing a URL
SMS to fixed lines: Not supported on that provider's standard route
Marketing: Law 5830/2017 and the SEDECO No Molestar framework, plus Law 4868/2013 electronic-commerce duties and the applicable permission and objection rules, all apply to promotional SMS
Contact window: Under the current official SEDECO No Molestar framework, contacts relying on the current-contract exception are limited to 08:00 to 18:00 on working days, Monday to Friday
Timing on other bases: Timing for traffic relying on express authorisation or another basis needs Paraguayan legal review and must not be inferred from the contractual-exception window
Data-protection transition: Law 7593/2025 was enacted and published on 27 November 2025 but does not enter into force until 27 November 2027, so it is not a current statutory duty
Last reviewed: 1 August 2026

Route-dependent: “Route-dependent” means the behaviour is decided by the supplier and operator path your traffic takes, not by Paraguayan law. Two providers can behave differently on the same day and a route can change its policy without notice. The seven-digit A2P origin numbering architecture, portability and the No Molestar duties, by contrast, are regulation and apply to every route.

Law, route policy and recommendation

Paraguay is a good example of why these layers must stay apart. Origin numbering and No Molestar are regulation, sender presentation and replies are route behaviour, and the way you evidence permission is largely our own standard.

Law / regulation
Law and regulation
Binding obligations from Paraguayan law and CONATEL regulation: the national numbering plan and +595 mobile formatting, active mobile number portability, Resolución Directorio 2431/2024 establishing seven-digit origin numbering for A2P SMS, Law 5830/2017 with the SEDECO No Molestar registry, and Law 4868/2013 on electronic commerce. Law 7593/2025 on personal data is enacted but not yet in force.
Carrier or route policy
Carrier or route policy
Rules applied by operators, aggregators or your provider on the specific path your traffic takes — which visible sender the recipient sees, whether a submitted numeric sender is preserved or replaced, whether inbound replies exist, concatenation behaviour, UCS-2 support, MMS conversion, landline handling, short-code availability and category acceptance. Supplier-specific 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 of the above — attributable permission evidence, live operator lookup instead of prefix guessing, brand and purpose in the body, separated templates, branded link domains, a working opt-out even where the sender cannot receive replies, and immediate suppression across every sending system.

Numbering and networks

The basics your validation layer and templates need to get right before the first send.

Law / regulationDialling code
Country calling code +595. Mobile country code 744.
Law / regulationNumber format
Ordinary Paraguayan mobile numbers are stored internationally as +595 followed by nine digits beginning with 9. A domestic form may be written as 09XX XXX XXX; the domestic trunk zero is removed when normalising to E.164.
Law / regulationA2P origin numbering
CONATEL Resolución Directorio 2431/2024 establishes a seven-digit origin numbering format for A2P SMS under the national numbering plan. Its structure identifies the mobile provider, whether the traffic originates on a national or a foreign provider network, and the integrator or aggregator involved. It applies to national and international A2P traffic.
Carrier or route policySender presentation
The exact sender a recipient sees, whether a submitted sender is preserved or replaced, and which A2P programmes are actually available are provider and operator decisions on the contracted route, not part of the numbering rule.
Flowstates recommendationAllocation detail
We do not publish supplier allocation, onboarding or provisioning detail for Paraguayan A2P origin numbers. We confirm the live position with you privately during route assessment.
Law / regulationNumber portability
Mobile number portability is available in Paraguay. CONATEL's official material confirms subscribers can change mobile provider while keeping their number, including the prefix, and portability has operated since 30 November 2012.
Carrier or route policyOutdated provider summary
At least one major provider's Paraguay country table still summarises number portability as unavailable. That summary is out of date against CONATEL.
Flowstates recommendationDo not build on the outdated summary
Do not use a provider's no-portability summary in routing or per-operator reporting logic. Follow CONATEL and run a live lookup instead.
Flowstates recommendationDo not infer the operator
Because portability is active, the prefix does not prove the current network. Run a live current-operator lookup before routing and before per-operator quality reporting.
Flowstates recommendationValidation before sending
A number that matches the syntax is not automatically messaging-capable. Validate Paraguayan jurisdiction, line type and mobile capability, and the current operator.
Carrier or route policyNetworks to plan for
Representative paths for operational testing include Tigo, Personal and Claro, plus Vox and other currently active or contracted paths where applicable. We publish no market-share claims and we do not assume every supplier has direct coverage on each path.
Flowstates recommendationValidate current operators
Confirm current operator status from official CONATEL material before you fix a route-testing matrix, because market participants and contracted paths change.

E.164 example

+595 9XX XXX XXX

Country code 595, then the nine national mobile digits with the domestic trunk zero removed. This is a masked illustrative pattern, not a real subscriber number, and it is not a substitute for live line-type and current-operator validation.

SenderID options

Paraguay is a route-assigned sender market in practice. Provider documentation for one major route is explicit that alphanumeric senders and Paraguayan domestic long codes are not supported, that international numeric senders are not preserved and may be replaced with random short codes or local long codes outside its control, and that two-way SMS is unavailable. Other routes can behave differently, so treat everything below as the behaviour of the specific path you buy and test it before launch.

Carrier or route policy

This whole comparison — best for, what the recipient sees and replies — describes carrier and provider route behaviour and programme availability on current A2P paths into Paraguay. The regulatory part sits underneath it: the seven-digit A2P origin numbering architecture comes from CONATEL Resolución Directorio 2431/2024. A selected sender programme may require assessment, and category acceptance is confirmed privately rather than published here.

Route-assigned Paraguay A2P sender

Best for: One-way OTP, transactional, service and permissioned marketing traffic on a contracted Paraguay A2P route
What the recipient sees: A seven-digit A2P origin or another local route-assigned sender confirmed by the supplier
Replies: No, unless a separate inbound-capable programme is explicitly configured and tested

International numeric sender

Best for: Selected one-way traffic where the supplier confirms Paraguay termination
What the recipient sees: On one major provider, a route-assigned local short code or long code rather than the submitted international number; other paths must be tested
Replies: No reliable reply path unless a separate inbound service is configured

Dedicated short code

Best for: Selected local high-scale programmes where carrier and provider support is confirmed
What the recipient sees: The approved short code
Replies: Route- and programme-dependent

Alphanumeric sender

Best for: Not a supported production option on one major provider's current Paraguay route
What the recipient sees: Unavailable, rejected or replaced according to the selected route
Replies: No

SenderID options
Option	Best for	What the recipient sees	Replies
Route-assigned Paraguay A2P sender	One-way OTP, transactional, service and permissioned marketing traffic on a contracted Paraguay A2P route	A seven-digit A2P origin or another local route-assigned sender confirmed by the supplier	No, unless a separate inbound-capable programme is explicitly configured and tested
International numeric sender	Selected one-way traffic where the supplier confirms Paraguay termination	On one major provider, a route-assigned local short code or long code rather than the submitted international number; other paths must be tested	No reliable reply path unless a separate inbound service is configured
Dedicated short code	Selected local high-scale programmes where carrier and provider support is confirmed	The approved short code	Route- and programme-dependent
Alphanumeric sender	Not a supported production option on one major provider's current Paraguay route	Unavailable, rejected or replaced according to the selected route	No

Flowstates recommendation: put a recognisable brand and the purpose of the message in the body, because the visible sender in Paraguay is frequently route-assigned rather than yours. Do not rely on replies unless inbound messaging is expressly configured and tested on the purchased service. Confirm the live sender and route with us privately before you build against either.

What changes by traffic type

Paraguay is not one rulebook. The same destination behaves differently depending on the category you send, the sender you use and the route it takes.

OTP / authentication

Suitable on a contracted Paraguay A2P path with a validated route-assigned sender.

Flowstates recommendation
Use a contracted Paraguay A2P path with a validated route-assigned sender rather than assuming your submitted sender survives.
Flowstates recommendation
Keep the copy purely transactional and concise, ideally inside a single segment.
Flowstates recommendation
Identify the brand and the purpose, and include an appropriate code-expiry cue.
Flowstates recommendation
No promotional content in OTP templates.
Flowstates recommendation
Use a branded domain only where a link is genuinely necessary.
Flowstates recommendation
Document the user action or context that caused the OTP. That context is not marketing permission.
Flowstates recommendation
Monitor delivery, latency, completed-verification conversion and per-route and per-operator performance.
Flowstates recommendation
Make sure every fallback sender or path is itself valid for Paraguay and for the traffic being sent.
Flowstates recommendation
Do not depend on replies unless an inbound path is explicitly configured and tested on the purchased route.

Transactional / service

Suitable for expected alerts, confirmations and account updates.

Flowstates recommendation
Keep the content within the purpose for which the number was provided.
Flowstates recommendation
Identify the brand and the purpose in the message body, and use branded links.
Flowstates recommendation
Maintain an appropriate objection, revocation and suppression process for recurring service programmes.
Flowstates recommendation
Test sender replacement, concatenation, Unicode behaviour and URL presentation on the exact path before relying on any of them.
Flowstates recommendation
A service context does not create permission for unrelated marketing. The category follows the content and purpose, not the template name.

Marketing / promotional

Registry checks, an accurately scoped exception or express authorisation, clear identification and a free way to stop.

Law / regulation
Law 5830/2017 expressly covers commercial contact made to mobile subscribers by calls, SMS, MMS and other telephone messaging.
Law / regulation
The national No Molestar registry is administered by SEDECO.
Law / regulation
Providers must consult the registry before commercial contact, and numbers registered in No Molestar generally may not be contacted for commercial purposes.
Law / regulation
The recognised exceptions are narrow: a current contractual relationship, limited to the strict object of that relationship and to a reasonable form and timing, or the consumer's express authorisation.
Law / regulation
Under the current official SEDECO No Molestar framework, contacts relying on the current-contract exception are limited to 08:00 to 18:00 on working days, Monday to Friday.
Flowstates recommendation
Do not turn that window into a universal rule for all consented messaging without Paraguayan legal review of your specific basis.
Law / regulation
Express authorisation must be clear and it is revocable.
Flowstates recommendation
When permission is revoked, suppress immediately across every sending system rather than relying on any grace period.
Law / regulation
Law 4868/2013 requires commercial electronic communications to be identifiable as commercial from the beginning, to identify the person or entity on whose behalf they are sent, and to include a simple and free mechanism to object.
Law / regulation
Unrequested commercial communications must be identifiable as such and must offer an easy exclusion mechanism.
Flowstates recommendation
Our launch standard is prior affirmative, attributable, purpose-specific and SMS-channel-specific permission, unless qualified Paraguayan counsel documents a valid exception and the selected route accepts the traffic.
Flowstates recommendation
Do not use bought or rented lists.
Flowstates recommendation
Support natural Spanish opt-out expressions such as BAJA, SALIR, CANCELAR, STOP and NO. No single keyword is the exclusive statutory method, so recognise the intent.
Flowstates recommendation
Use a branded domain rather than a public or shared shortener.
Carrier or route policy
Category acceptance for promotional traffic remains route-specific and is confirmed privately.

Paraguay's No Molestar and electronic-commerce rules

Paraguay separates questions that are routinely mixed together: may you contact this mobile subscriber commercially at all, how must the commercial message identify itself, and what will the route actually do with your sender. Law 5830/2017 and the SEDECO framework answer the first, Law 4868/2013 answers the second, and route policy answers the third.

Law / regulation
Law 5830/2017 prohibits unauthorised advertising to mobile telephony subscribers and expressly covers calls, SMS, MMS and other telephone messaging.
Law / regulation
The national No Molestar registry created under that law is administered by SEDECO, the consumer-protection authority.
Law / regulation
Consultation of the registry before commercial contact is mandatory, and contact to registered numbers is prohibited except under the recognised exceptions.
Law / regulation
The current-contract exception applies only where a contractual relationship is in force, and it is limited to the strict object of that relationship and to a reasonable form and timing.
Law / regulation
Under the current official SEDECO No Molestar framework, contacts relying on the current-contract exception are limited to the specifically acquired product or service and to 08:00 to 18:00 on working days, Monday to Friday.
Law / regulation
The alternative exception is the consumer's express authorisation, which must be clear and which the consumer can revoke.
Flowstates recommendation
Where express authorisation rather than the current-contract exception is the basis, the permitted timing can differ. Have Paraguayan counsel confirm the timing you rely on rather than assuming either the exception window or an unlimited window.
Law / regulation
SEDECO states that the Supreme Court upheld the sanction in the AMX Paraguay case and held that the contacts made by third parties benefited the company, so it could not avoid liability in that case.
Flowstates recommendation
Do not assume that outsourcing contact activity to an agency, dialler or reseller removes your own responsibility for it.
Law / regulation
Law 4868/2013 requires an electronic commercial communication to be identifiable as commercial from the beginning of the message.
Law / regulation
It must identify the natural or legal person on whose behalf it is sent.
Law / regulation
A simple and free means of objecting must be available both at the point where the data is collected and in every commercial communication.
Law / regulation
Unrequested commercial communications must be identifiable as unrequested and must offer an easy exclusion mechanism.
Flowstates recommendation
Do not use unlawfully sourced, bought or rented lists.
Law / regulation
Law 7593/2025 on the protection of personal data was enacted and published on 27 November 2025, and Article 57 provides that it enters into force 24 months after publication.
Law / regulation
It is therefore not in force on 1 August 2026 and should not be presented as a current statutory duty. Its effective date is 27 November 2027.
Flowstates recommendation
Build records, transparency, purpose controls, security and rights handling now with that transition in mind — but describe those controls as preparation and good practice, not as duties that already bind you under Law 7593/2025.
Carrier or route policy
Sender replacement, two-way support, concatenation, UCS-2 support, MMS conversion and carrier filtering are route policy. None of them are No Molestar or electronic-commerce law, and complying with one says nothing about the other.

Operational compliance checklist

The controls we expect to see in place before Paraguayan traffic goes live, and the records we expect you to be able to produce afterwards.

Law / regulation
Store destinations as +595 plus the nine national mobile digits, removing the domestic trunk zero.
Flowstates recommendation
Validate Paraguayan jurisdiction, line type and mobile capability, and resolve the current operator before sending.
Flowstates recommendation
Do not infer the current operator from the prefix, because portability is available.
Flowstates recommendation
Select the sender deliberately: a contracted route-assigned A2P sender, a validated international numeric route or an approved short code, as applicable.
Flowstates recommendation
Confirm the live visible sender and the fallback behaviour on the purchased route before launch.
Flowstates recommendation
Keep the brand, the website, the use case, the permission journey, the sample templates and the live traffic materially aligned.
Flowstates recommendation
Keep OTP, service and marketing purposes, templates and permission records separate.
Law / regulation
For marketing, the No Molestar registry must be checked before commercial contact.
Flowstates recommendation
Retain evidence of the registry result, its timestamp and the permission or exception relied on.
Flowstates recommendation
Retain the recipient, timestamp, source, disclosure version, purpose, channel and evidence of the permission or reviewed exception as our evidence standard.
Law / regulation
Identify the commercial nature of the message and the person or entity on whose behalf it is sent.
Law / regulation
Provide a simple and free way to object in every promotional message.
Flowstates recommendation
Recognise BAJA, SALIR, CANCELAR, STOP, NO and reasonable natural-language equivalents as opt-out requests.
Flowstates recommendation
Suppress immediately across every sending system, including separate campaign or CRM tooling. Do not rely operationally on any statutory or grace period.
Flowstates recommendation
Do not use bought or rented lists.
Flowstates recommendation
Apply the current-contract exception window of 08:00 to 18:00, Monday to Friday, carefully and only to contacts that genuinely rely on that exception.
Flowstates recommendation
Take Paraguayan legal review for any other timing or permission scenario rather than extending that window by analogy.
Flowstates recommendation
Use branded short domains rather than public or shared shorteners.
Flowstates recommendation
Test the Tigo, Personal and Claro paths, plus Vox or other current and contracted operator paths where applicable, before you scale.
Flowstates recommendation
Test sender replacement, concatenation, Unicode and UCS-2 handling, MMS conversion, inbound replies and opt-out handling on the exact purchased route.
Flowstates recommendation
Keep template, notice, permission or exception, No Molestar check, route approval, opt-out and suppression evidence.

Encoding and delivery

Segment maths, Spanish and Guaraní language pitfalls, and what to test on the live route before launch.

GSM-7 single segment: Normally 160 characters
GSM-7 concatenated: Normally 153 characters per segment
Unicode / UCS-2 single segment: Normally 70 characters
Unicode / UCS-2 concatenated: Normally 67 characters per segment
E.164 example: +595 9XX XXX XXX

Flowstates recommendation
Spanish copy does not automatically force UCS-2. ñ, ¿, ¡ and é are available in the GSM-7 basic alphabet, but á, í, ó, ú, smart quotation marks, emoji and many Guaraní nasal-vowel and diacritic characters can force UCS-2 unless they are replaced or transliterated.
Carrier or route policy
One major provider's international long code row for Paraguay states that UCS-2 is not supported. That is its own route policy, not a national rule, and other routes may differ.
Flowstates recommendation
Test the actual encoded Spanish and Guaraní copy, and its real segment count, on the exact sender and operator paths you intend to use.
Flowstates recommendation
Keep OTP messages within a single segment wherever practical. Do not treat a provider's maximum segment count as a copy target.
Law / regulation
Remove the domestic trunk zero when normalising a 09XX XXX XXX domestic form to +595 plus nine digits.
Law / regulation
Portability is active, so the original prefix is not proof of the current operator.
Flowstates recommendation
Run a live current-operator lookup for routing and per-operator quality analysis rather than inferring from the range, and use masked examples such as +595 9XX XXX XXX in documentation rather than real subscriber numbers.
Carrier or route policy
MMS conversion, media limits and sender replacement are route policy. One major provider converts MMS into an SMS containing a URL, and other paths may differ.

A country guide is only useful when the route follows it.

Country rules only help if the route your traffic actually takes respects them. That is the part we operate.

Per-country and per-category routing
Multi-vendor routing decided per country and per traffic category, so OTP, service and marketing traffic into Paraguay do not share one compromise route.
SenderID management
We manage sender presentation per route and per category, including Paraguayan route-assigned A2P senders and validated numeric senders, and we check what the recipient actually sees before launch.
Carrier-grade failover
Automatic failover between vendors, with fallback senders that are themselves valid for Paraguay rather than a route that quietly replaces your sender.
Per-route visibility
Delivery, latency and OTP-conversion visibility per route, so a quality change on one Paraguayan operator path is visible while it is still small.
24/7 vendor escalation
We chase the vendor. Escalation runs around the clock rather than waiting for a support queue in another time zone.
BYOV / BYOG
Bring your own vendors or gateway and keep your commercial relationships while we operate the routing, sender policy and monitoring.
Branded short links
Branded short domains instead of public shorteners, so Paraguayan recipients see a link that matches the brand in the message body.

Developer docs Branded short links

What we need to validate your Paraguay route

What we need from you so we can validate senders, routes and category acceptance on the live Paraguayan path before you launch.

Company or legal entity and website
Customer-facing brand
Traffic category and use case
English, Spanish and any Guaraní sample templates for each distinct use case
Expected monthly volume and peak sending rate
Preferred sender type
Existing Paraguay sender inventory and provider, at a high level
Opt-in or permission journey, supporting evidence and the exact disclosure wording
Privacy notice and terms URLs
Marketing permission or exception relied on, and the owner of the legal review
No Molestar check process and its owner
Internal objection, opt-out and suppression process, and its owner
Link domains you intend to use
Whether you need replies or two-way messaging
MMS, Unicode or Guaraní and multi-segment requirements
How numbers are collected, normalised and validated
Target launch date

Validate my Paraguay route Book a messaging review

Frequently asked questions about SMS in Paraguay

Can I send SMS to mobile numbers in Paraguay?

A quick operational read on Paraguay. Anything marked route-dependent is decided by the supplier and operator path your traffic uses. Anything marked law applies whichever supplier you pick. SMS to mobile: Supported on selected contracted A2P routes. Number format: +595 followed by the nine national mobile digits; the domestic trunk zero is removed when normalising to E.164. Number validation: Confirm the destination is Paraguayan, messaging-capable mobile and resolve the current operator before sending. Number portability: Available — CONATEL confirms mobile portability has operated since 30 November 2012 and the subscriber keeps the number, including the prefix.

Which sender ID options work for SMS in Paraguay?

Paraguay is a route-assigned sender market in practice. Route-assigned Paraguay A2P sender — Best for: One-way OTP, transactional, service and permissioned marketing traffic on a contracted Paraguay A2P route. International numeric sender — Best for: Selected one-way traffic where the supplier confirms Paraguay termination. Dedicated short code — Best for: Selected local high-scale programmes where carrier and provider support is confirmed. Alphanumeric sender — Best for: Not a supported production option on one major provider's current Paraguay route.

What are the consent and opt-out requirements for SMS in Paraguay?

Paraguay separates questions that are routinely mixed together: may you contact this mobile subscriber commercially at all, how must the commercial message identify itself, and what will the route actually do with your sender. Law 5830/2017 prohibits unauthorised advertising to mobile telephony subscribers and expressly covers calls, SMS, MMS and other telephone messaging. The national No Molestar registry created under that law is administered by SEDECO, the consumer-protection authority. Consultation of the registry before commercial contact is mandatory, and contact to registered numbers is prohibited except under the recognised exceptions.

How many characters fit in an SMS to Paraguay?

Segment maths, Spanish and Guaraní language pitfalls, and what to test on the live route before launch. GSM-7 single segment: Normally 160 characters. GSM-7 concatenated: Normally 153 characters per segment. Unicode / UCS-2 single segment: Normally 70 characters. Unicode / UCS-2 concatenated: Normally 67 characters per segment.

Sources and change control

Official Paraguayan sources control the law, numbering, portability, No Molestar and effective-date wording. Provider sources describe only their own current route. Where a provider page conflicts with CONATEL, we follow CONATEL and say so.

Provider route policy
Twilio — Paraguay SMS guidelines
Describes its own Paraguay route: no two-way SMS, concatenation supported with sender and encoding qualifications, MMS converted to an SMS containing a URL, no SMS to fixed lines, no alphanumeric sender IDs, no Paraguayan domestic long codes, international numeric senders able to terminate but not preserved and possibly replaced with random short codes or local long codes outside its control, UCS-2 listed as unsupported on its international long code row, and short codes operator-capable but not offered. Its country summary of number portability as unavailable is out of date against CONATEL.
Regulator
CONATEL — Resolución Directorio 2431/2024
Establishes numbering for application-to-person (A2P) short messages within the national numbering plan. The official page links the full resolution.
Regulation
CONATEL — Resolución Directorio 2431/2024 (official PDF)
The seven-digit A2P origin format: a provider identifier digit, a digit distinguishing origin on a national provider network from origin on a foreign provider network, and the integrator or aggregator identifier. Applies to national and international A2P traffic.
Official numbering
CONATEL — national numbering plan (PTFNN) material
The Plan Técnico Fundamental de Numeración Nacional and related CONATEL plans, used here for +595 formatting and the treatment of the domestic trunk zero.
Regulator
CONATEL — mobile number portability
Official portability material confirming that a mobile subscriber may change provider while keeping the number, including the prefix. Portability has operated since 30 November 2012, which is why the prefix cannot be used to infer the current operator.
Official market data
CONATEL — telecommunications indicators and operator information
Used only to confirm which operator paths to plan for in route testing. We publish no market-share claims.
Statute
BACN — Law 5830/2017
Prohibits advertising not authorised by mobile telephony subscribers and creates the national No Molestar registry. Calls, SMS, MMS and other telephone messaging are in scope.
Regulator
SEDECO — Registro Nacional No Molestar
The controlling official source for the current No Molestar framework and FAQ: registry consultation is mandatory; SMS and MMS are in scope; contacts relying on a current contract are limited to the specifically acquired product or service and to 08:00 to 18:00 on working days, Monday to Friday; express authorisation must be clear and can be revoked, after which calls and messages must stop immediately.
Enforcement note
SEDECO — Supreme Court confirms sanction for unauthorised commercial contact (2025)
Cited cautiously and as fact-specific: the official SEDECO note stating that the Supreme Court upheld the sanction in the AMX Paraguay case and that the contacts made by third parties benefited the company, so it could not avoid liability in that case.
Statute
BACN — Law 4868/2013 on electronic commerce
Articles 21 to 23 in particular: commercial electronic communications identifiable from the beginning, identification of the person or entity on whose behalf they are sent, a simple and free objection mechanism, and the treatment of unrequested communications.
Statute
BACN — Law 7593/2025 on personal data protection
Enacted and published on 27 November 2025. Article 57 sets entry into force 24 months after publication, so the effective date is 27 November 2027 and the law is not a current duty on 1 August 2026.

Change log

1 August 2026 — Initial publication; corrected Twilio's outdated no-portability summary, incorporated CONATEL's seven-digit A2P numbering, separated No Molestar and e-commerce duties from route policy, and recorded that Law 7593/2025 is not yet in force.

Last reviewed 1 August 2026

Disclaimer

This page is operational guidance, not legal advice. Requirements vary by law, message purpose, sender, provider, carrier route, recipient context and customer setup, and they change. Flowstates confirms the live route with you during onboarding, and you should take your own Paraguayan legal advice on marketing and data-protection obligations.

Paraguay SMS guide