What actually changes when you send OTP, transactional or marketing A2P SMS into Argentina — separated into Argentine law, supplier route policy and what we recommend operationally.
Last reviewed: 1 August 2026 · South America / LATAM
A quick operational read on Argentina. 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
National number normalisation
Law / regulation
Argentina uses country code +54 and the national mobile number carries ten digits — remove the domestic trunk 0 and the mobile 15 when normalising numbers or using the ENACOM lookup
SMS submission format
Carrier or route policy
On the documented major A2P SMS paths, submit +54 plus those ten national digits and do not add the voice/WhatsApp 9 by default — confirm the final format on the selected supplier route
Alphanumeric senderID
Carrier or route policy
Local networks do not preserve dynamic alpha on common routes; it is normally replaced by a route-assigned local long code or shortcode
International numeric / longcode senderID
Carrier or route policy
Supported on selected international paths but commonly overwritten — preservation is not promised
Domestic longcode
Carrier or route policy
Network capability exists, but it is not a generally available standard sender through every international provider — selected local or two-way services only
Shared or route-assigned local sender
Carrier or route policy
Available on selected managed routes; the visible identity may vary between sends
Dedicated or local shortcode
Carrier or route policy
Supported through selected operator or supplier programmes; a consistent identity only where the programme confirms it
Two-way SMS
Carrier or route policy
Available through selected local-number or shortcode services — not a universal property of every international A2P route
Number portability
Law / regulation
Available
Concatenation
Carrier or route policy
Supported on Twilio and some other paths — test the exact sender and operator route
MMS
Carrier or route policy
Twilio converts MMS into an SMS containing an embedded URL; other providers may describe no MMS support at all, so treat it as route-dependent
SMS to fixed line
Carrier or route policy
Not supported on standard routes
Marketing
Law / regulation
Law 26.951 and the Registro Nacional No Llame, Decree 2501/2014, Law 25.326 and individual blocking or opt-out duties apply
Personal data
Law / regulation
Law 25.326 requires lawful, purpose-compatible, accurate, secure and appropriately retained processing, clear notice at collection and respect for data-subject rights
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 Argentine statute. Provider documentation for Argentina disagrees on senders, numeric support and two-way messaging, and a route can change its policy. Confirm before launch.
Law, route policy and recommendation
Argentine 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 Argentine legislation and the authorities that apply it: ENACOM as the telecom regulator and numbering authority, Law 26.951 and Decree 2501/2014 for the Registro Nacional No Llame, and Law 25.326 with Decree 1558/2001 for personal data, supervised by the AAIP. 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 an international number survives, whether replies are possible, concatenation behaviour, Unicode handling, MMS conversion and any promotional sending windows the supplier imposes. 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 screening No Llame immediately before each campaign rather than relying only on a monthly batch, and maintaining an internal suppression list in parallel.
Numbering and networks
Argentina is the market where teams most often store the wrong number. Get the SMS destination format right before the first send.
Carrier or route policySMS destination format
Use +54 followed by the ten-digit Argentine national mobile number. Remove the domestic trunk 0 from the area code and remove the domestic mobile marker 15. Do not insert the 9 after +54 unless the selected SMS supplier expressly requires a different normalisation.
Carrier or route policyThe 9 is a voice and WhatsApp convention, not the SMS format
+54 9 ... may be correct for international voice calls and for WhatsApp, but on the documented Twilio, Vonage and 8x8 SMS paths it is generally not the SMS destination format. Vonage states plainly that the 9 should not be included for SMS, and Twilio's Proxy documentation distinguishes the Argentine SMS and voice formats. Treat the final normalisation as supplier-route validation rather than a guess.
Law / regulationNational significant number
Argentine national numbers carry ten national digits, but the area-code length varies: two digits for Buenos Aires, three or four digits elsewhere, with the subscriber number making up the balance. Store the ten digits rather than assuming a fixed area-code length.
Law / regulationNumbering administration
ENACOM is the national telecommunications regulator and numbering authority. Its operator lookup explicitly tells users not to enter the area-code 0 or the mobile 15. ENACOM Resolution 1369/2023 modernises the national numbering plan, so do not hard-code historical locality assumptions into validation.
Law / regulationDialling code
Country calling code +54. Mobile country code 722.
Law / regulationNumber portability
Mobile number portability is available in Argentina, so a number can be held by an operator other than the one that originally received the range.
Flowstates recommendationPortability handling
ENACOM publishes an original and current provider lookup. Run a live lookup rather than inferring the network from the original range, because the original range cannot reliably identify the current operator.
Carrier or route policyNetworks
The consumer brands currently relevant for route testing are Claro, Personal and Movistar. On 18 June 2026 Argentina's competition authority conditionally approved Telecom's acquisition of Telefónica Argentina with structural remedies intended to preserve three competitive mobile operators. Consumer brands may remain visible during the transition, so treat neither the brand nor the original range as a stable proxy for current ownership, network or route.
Flowstates recommendationValidation
Validate to E.164, keep all ten national digits, and run mobile and current-operator validation before sending. Standard A2P SMS should target mobile destinations, so validate fixed-line destinations out.
Drop the domestic trunk 0 and the mobile 15, keep the ten national digits, and do not add the voice/WhatsApp 9 by default. These are masked illustrative patterns, not real subscriber numbers — the final normalisation is confirmed against the selected supplier route.
SenderID options
Argentine sender presentation is decided by the route, and providers describe it consistently enough to plan for rewriting. Twilio states that pre-registered and dynamic alphanumeric senderIDs are not supported by local networks, that a submitted dynamic alpha is not preserved and is delivered using a random shortcode outside Twilio, and that international long codes are supported but not preserved. Telnyx says alpha senderIDs are overwritten to a random local long code or shortcode. Vonage says alphanumeric senders are unsupported or overwritten, that numeric senders are unsupported unless supplied through its two-way service, and that generic senders are prohibited by its route policy. 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 live carrier and supplier route behaviour on current A2P paths into Argentina, not Argentine 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 sender rewriting is accepted
What the recipient sees
A route-assigned local long code or shortcode rather than the submitted alpha or international number
Replies
Not assumed
Provider-assigned shared local sender
Best for
Managed one-way A2P traffic where the supplier chooses a local numeric or shared shortcode identity
What the recipient sees
The route-assigned local number or shared shortcode, which may vary
Replies
Not assumed
Provider-assigned inbound-capable local sender
Best for
Selected support, service and conversational use cases
What the recipient sees
The local number or shortcode assigned to that service
Replies
Available only when explicitly configured and tested
Dedicated 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 sender rewriting is accepted
A route-assigned local long code or shortcode rather than the submitted alpha or international number
Not assumed
Provider-assigned shared local sender
Managed one-way A2P traffic where the supplier chooses a local numeric or shared shortcode identity
The route-assigned local number or shared shortcode, which may vary
Not assumed
Provider-assigned inbound-capable local sender
Selected support, service and conversational use cases
The local number or shortcode assigned to that service
Available only when explicitly configured and tested
Dedicated 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 replies unless an inbound-capable local sender or shortcode service is expressly configured and tested. 8x8 and other provider pages describe two-way support through shortcodes and different route behaviours, which reinforces route-dependent planning rather than a universal sender model. A selected local 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 is normally 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 an inbound-capable local sender or shortcode 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 in the body.
Flowstates recommendation
Use a branded domain for links.
Flowstates recommendation
Keep promotional copy out of transactional templates.
Carrier or route policy
Test concatenation and the final Spanish encoding on the exact route and sender type before relying on either.
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
No Llame screening, Law 25.326 duties, narrow legal exceptions and supplier route policy.
Law / regulation
Law 26.951 creates the nationwide Registro Nacional No Llame for telephone services in all modalities, and official Argentine guidance describes it as covering unwanted advertising calls and messages.
Law / regulation
Businesses carrying out unsolicited advertising, offers, sales or gifts through telephone services must not contact registered numbers, subject to the law's exceptions.
Law / regulation
Obligated parties must consult the latest No Llame update at least every 30 calendar days and before unsolicited contact.
Flowstates recommendation
Screen the registry immediately before every campaign, or use the AAIP automated consultation service, rather than relying only on a monthly batch check.
Law / regulation
The framework applies where an Argentine advertiser or beneficiary outsources the campaign abroad — offshore sending is not an escape from it.
Law / regulation
The exceptions include genuine public-interest campaigns, emergencies, electoral campaigns, a current contractual relationship limited to the strict object of that relationship, and express permission from the registered user.
Law / regulation
For the current-contract exception, Decree 2501/2014 defines reasonable hours as Monday to Friday 09:00–21:00 and Saturday 09:00–13:00. Those hours belong to that exception; they are not a universal statutory SMS-marketing window.
Law / regulation
To contact a number already registered in No Llame under express permission, Decree 2501/2014 requires free, express and informed consent in writing or an equivalent form, and where a contract exists the permission must sit in a separate instrument.
Law / regulation
Law 25.326 Article 27 permits direct-marketing data drawn from unrestricted public documents, supplied by the data subject or obtained with consent, while giving the individual free access and the right to withdraw or block their name at any time. Consent is therefore not the only possible basis — but Article 27 never overrides No Llame or a direct objection.
Flowstates recommendation
Flowstates launch standard: retain timestamped, source-attributed, purpose-specific and SMS-channel-specific promotional permission unless qualified Argentine counsel documents another valid basis or exception and the selected route accepts it. Even then, screen No Llame and the internal suppression list.
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
Suppress promptly and across every sending system, not just the one that received the request.
Flowstates recommendation
Do not use purchased lists.
Flowstates recommendation
Schedule promotions by Argentine recipient-local daytime as our operational standard.
Carrier or route policy
Some supplier or operator paths impose separate route-specific promotional quiet hours. Those are confirmed privately during route assessment and must never be described as Argentine law.
Carrier or route policy
Use the agreed promotional route — category acceptance is confirmed privately during route assessment.
Argentina's No Llame, marketing and personal-data rules
Two separate Argentine frameworks matter for SMS marketing, and they answer different questions. Law 26.951 and Decree 2501/2014 govern who you may contact for unsolicited promotion. Law 25.326 and Decree 1558/2001 govern the personal data behind the campaign. Neither is the same as your provider's route policy.
Law / regulation
Law 26.951 applies nationwide to telephone services in all modalities and protects users from unsolicited advertising, offers, sales and gifts.
Law / regulation
Numbers registered in the Registro Nacional No Llame cannot be contacted for unsolicited promotion, subject to the exceptions the law sets out.
Law / regulation
The latest registry update must be consulted at least every 30 calendar days and before unsolicited contact.
Law / regulation
Campaign principals or beneficiaries and the outsourced callers acting for them can both be responsible; outsourcing the campaign abroad does not remove the obligation.
Law / regulation
The exceptions are narrow: genuine public-interest campaigns, emergencies, electoral campaigns, a current contractual relationship, and express permission from the registered user.
Law / regulation
The current-contract exception is limited to the strict object of the current relationship and to the reasonable hours defined by Decree 2501/2014 — Monday to Friday 09:00–21:00 and Saturday 09:00–13:00.
Law / regulation
Express permission for a registered line must be free, express and informed, recorded in writing or an equivalent form, and separate from the contract where one exists.
Flowstates recommendation
The decree's visible caller-identification wording is written for calls. Do not invent a statutory SMS sender-format requirement from it that would conflict with actual route rewriting.
Flowstates recommendation
Keep evidence of every registry screening and of the basis or exception relied on for each campaign.
Law / regulation
Law 25.326 requires personal data to be collected and processed lawfully, to be accurate, adequate, relevant and not excessive, to be used for compatible purposes, kept secure, and deleted when no longer necessary.
Law / regulation
Consent generally must be free, express and informed, recorded in writing or an equivalent method, subject to the exceptions the law provides.
Law / regulation
At collection, clearly explain the purpose, the recipients or classes of recipients, the identity and address of the controller, which fields are mandatory or optional, the consequences of providing or refusing data, and the rights of access, rectification and deletion.
Law / regulation
Article 27 permits direct-marketing data taken from unrestricted public documents, supplied by the data subject or obtained with consent, and the individual may request withdrawal or blocking from advertising databases at any time — Decree 1558/2001 allows blocking by a particular communication channel.
Flowstates recommendation
Do not say consent is always the only possible legal basis, and do not use Article 27 to bypass No Llame or a direct objection. The two duties run in parallel: registry screening and individual blocking.
Flowstates recommendation
Confirm with Argentine counsel whether your role in the campaign and your databases require registration with the Registro Nacional de Bases de Datos Personales. The No Llame framework treats advertisers and campaign principals as data users or controllers.
Flowstates recommendation
Keep OTP and service purposes and templates operationally separate from marketing purposes and templates.
Flowstates recommendation
Retain the notice version, the purpose, the data source, the permission or documented basis or exception, No Llame screening evidence, opt-out and objection handling, suppression records, campaign records and processing evidence.
Operational compliance checklist
What we expect to be in place before Argentine traffic goes live, and to stay in place afterwards.
Law / regulation
Normalise and store the ten-digit national mobile number without the domestic trunk 0 and without the mobile 15.
Carrier or route policy
Submit A2P SMS as +54 plus those ten national digits on the documented major paths.
Carrier or route policy
Do not add the voice/WhatsApp 9 by default, and confirm the exact normalisation with the selected supplier route.
Flowstates recommendation
Validate mobile status and the current operator; do not infer either from the area code or from the original range.
Flowstates recommendation
Record the source, purpose and permitted use of every recipient record.
Law / regulation
Provide clear Law 25.326 information at collection 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 basis or exception.
Law / regulation
Check the latest Registro Nacional No Llame before unsolicited promotional contact and at least every 30 calendar days, and retain evidence of the check.
Flowstates recommendation
Maintain an internal individual blocking and suppression list in parallel with No Llame.
Law / regulation
If relying on the current-contract exception, keep the message within the strict object of the relationship and inside the applicable legal hours.
Law / regulation
If contacting a registered line under express permission, retain the separate free, express and informed permission evidence.
Flowstates recommendation
Identify the brand and the message purpose in the body.
Flowstates recommendation
Support BAJA, SALIR, CANCELAR and NO without claiming a universal keyword mandate.
Flowstates recommendation
Suppress promptly and across every sending system.
Law / regulation
Honour access, rectification, withdrawal or blocking, and deletion or suppression requests.
Flowstates recommendation
Do not use purchased lists.
Flowstates recommendation
Schedule campaigns by Argentine 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 route quiet hours and category acceptance privately with us during route assessment.
Flowstates recommendation
Retain template, notice, basis or permission, No Llame check, opt-out, campaign, suppression and route-approval records.
Encoding and delivery
Argentine Spanish copy changes segment maths more often than teams expect, and the number format is the most common cause of silent non-delivery.
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 characters such as á, í, ó and ú, 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. ñ alone does not necessarily force UCS-2, so test rather than assume.
Carrier or route policy
Twilio marks UCS-2 as supported on its dynamic alphanumeric, international numeric and shortcode routes, but behaviour remains route-specific.
Carrier or route policy
Test the final Spanish copy end to end on the actual sender type and on the Claro, Personal and Movistar-branded destinations you have purchased.
Law / regulation
Normalise destinations as +54 plus the ten national digits: 011 15-XXXX-XXXX becomes +54 11 XXXX XXXX, 0XXX 15-XXX-XXXX becomes +54 XXX XXX XXXX and 0XXXX 15-XX-XXXX becomes +54 XXXX XX XXXX. Remove the 0 and the 15.
Carrier or route policy
The 9 after +54 is a voice and WhatsApp convention. Do not add it to SMS destinations unless the selected supplier route expressly requires it.
Flowstates recommendation
Run a live mobile and current-operator lookup before sending, because portability is active and the 2026 operator transition makes brand or original range an unreliable routing proxy.
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 provider 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 an Argentine sender will be rewritten, or that a promotional list must be screened against No Llame, 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 Argentine 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 Argentine 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 Argentine 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 is rewritten.
A quick operational read on Argentina. 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. National number normalisation: Argentina uses country code +54 and the national mobile number carries ten digits — remove the domestic trunk 0 and the mobile 15 when normalising numbers or using the ENACOM lookup. SMS submission format: On the documented major A2P SMS paths, submit +54 plus those ten national digits and do not add the voice/WhatsApp 9 by default — confirm the final format on the selected supplier route. Alphanumeric senderID: Local networks do not preserve dynamic alpha on common routes; it is normally replaced by a route-assigned local long code or shortcode.
Which sender ID options work for SMS in Argentina?
Argentine sender presentation is decided by the route, and providers describe it consistently enough to plan for rewriting. Rewritten international A2P sender — Best for: Fast launch of one-way OTP and transactional traffic where sender rewriting is accepted. Provider-assigned shared local sender — Best for: Managed one-way A2P traffic where the supplier chooses a local numeric or shared shortcode identity. Provider-assigned inbound-capable local sender — Best for: Selected support, service and conversational use cases. Dedicated local shortcode — Best for: Selected scale programmes requiring a consistent numeric identity.
What are the consent and opt-out requirements for SMS in Argentina?
Two separate Argentine frameworks matter for SMS marketing, and they answer different questions. Law 26.951 applies nationwide to telephone services in all modalities and protects users from unsolicited advertising, offers, sales and gifts. Numbers registered in the Registro Nacional No Llame cannot be contacted for unsolicited promotion, subject to the exceptions the law sets out. The latest registry update must be consulted at least every 30 calendar days and before unsolicited contact.
How many characters fit in an SMS to Argentina?
Argentine Spanish copy changes segment maths more often than teams expect, and the number format is the most common cause of silent non-delivery. 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, regulator and portability wording follows ENACOM. No Llame and Law 25.326 wording follows official Argentine law and AAIP sources. The operator-transition note follows the June 2026 competition decision. Provider pages describe only their own route behaviour, and where they conflict we keep the language route-dependent.
States that pre-registered and dynamic alphanumeric senderIDs are not supported by local networks and are delivered using a random shortcode, that international long codes are supported but not preserved, that domestic longcode is a network capability Twilio does not offer as a standard Argentine sender, and that shortcodes, two-way SMS and concatenation are supported, MMS is converted to SMS with a URL, portability is available and landline SMS is unsupported.
Defines the reasonable hours for the current-contract exception and the requirements for free, express and informed permission recorded separately from a contract.
Source for the concise operator-transition note; conditional approval with structural remedies intended to preserve three competitive mobile operators.
States that alphanumeric senderIDs are overwritten to a random local long code or shortcode. Its page displays an incorrect dial code; the correct country calling code is +54.
States that alphanumeric senderIDs are unsupported or overwritten, that numeric senders are unsupported unless supplied through its two-way service, that generic senders are prohibited by its route policy, and that the 9 should not be included for SMS.
Describes two-way support through shortcodes and route behaviour that differs from other providers, which is why sender behaviour stays route-dependent here.
Change log
1 August 2026 — Initial publication; separated Argentina's SMS number format from voice/WhatsApp conventions and distinguished No Llame, Law 25.326 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 or exception, message purpose and customer setup. Flowstates confirms the live path during onboarding.
