Skip to main content

​
Argentina CCM/AFIP Rules

Argentina’s Ente Nacional de Comunicaciones (ENACOM) regulates telecommunications, including the communications networks and services used for SMS and voice delivery. Argentina’s data-protection and direct-marketing posture also requires you to respect the recipient’s right to object and the Registro Nacional No Llame (National Do Not Call Registry) for covered marketing calls. Treat the regime as an opt-out posture: identify the recipient, give a clear way to stop, and honour a stop before the next send. The sender must be identifiable. For an Argentina launch, keep your legal business identity and CUIT / AFIP evidence aligned with the sender identity that you submit to a carrier or registry. Orbit provides the sender, consent, suppression, and evidence surfaces; the tenant owns the legal posture, including the decision to send and the evidence it keeps.
This page is documentation, not legal advice. ENACOM, the Argentine data protection authority, and the National Do Not Call Registry can investigate or sanction non-compliant communications; carrier filtering and sender rejection are additional operational consequences. Have counsel confirm whether your traffic is marketing, which recipients are covered, and which CCM/AFIP or carrier documents your business must provide. Orbit does not certify a tenant’s compliance or impose a global Argentina gate.

​
Argentina obligations mapped to Orbit

Use the live country row and your own legal review together. The table below maps the evidence you control to the surface where Orbit stores or checks it.

​
Sender and KYC posture

The AFIP/CUIT identity is part of the business evidence a tenant may need to assemble for an Argentine sender. Do not put a tax identifier in message content unless your legal or carrier requirements call for it. Instead:
  1. Use a sender name or number that the recipient can associate with your legal business.
  2. Assemble the requested company registration, CUIT/AFIP evidence, brand authorization, and contact details in Documents & KYC.
  3. Submit the sender through Sender-ID Registration when the live row or your carrier marks registration as recommended or required.
  4. Keep the approved sender, legal entity, and tenant organization aligned. A sender approved for one entity is not evidence for another tenant.
  5. Re-check the live row after a regulator or carrier change. Do not infer registration status from this page’s snapshot.
If a carrier asks for a CCM document or an AFIP/CUIT record, treat that as an identity-verification requirement for the tenant’s sender application. Keep the submitted document and its approval outcome with the sender record; Orbit does not make the carrier’s approval decision.

​
Send-time posture

Argentina’s opt-out and registry obligations are tenant-owned. Before a marketing send, keep the unknown-marketing policy conservative and require an explicit consent record when consent is the basis for the campaign. A suppression entry or recipient objection always wins over a consent record. Read the live SMS row with this filter:
For voice, replace channel=sms with channel=voice and use the same country_code=AR filter. Confirm sender_types, registration, content_restrictions, stop_requirement, and last_reviewed_at before the send. If registration is required or recommended, do not treat an unregistered sender as launch-ready. For covered marketing calls, scrub the tenant’s audience with the Argentina filter and inspect the response freshness:
A DNC response does not replace your suppression check. Run both checks, keep the results with the campaign review, and stop when either surface says not to contact the recipient.

​
Worked pre-launch configuration

Use this sequence for an Argentina SMS campaign with an optional voice follow-up. Each decision is made by the tenant and remains auditable.
  1. Classify the traffic. Mark promotional messages and calls as marketing. Separate transactional notices from marketing content instead of assuming that a mixed message is transactional.
  2. Read the live rules. Fetch the AR rows for sms and voice. Record the sender types, registration level, stop requirement, restrictions, and review timestamp in the launch checklist.
  3. Assemble identity evidence. Upload the tenant’s legal-entity, CUIT/AFIP, brand-authorization, and any requested CCM documents through Documents & KYC. File the sender if the live row or carrier requires it, then wait for approval.
  4. Capture or verify consent. For every recipient whose campaign relies on consent, write a purpose-specific record and check it with the consent lookup endpoint. Record the source and disclosure version in the tenant’s evidence system.
  5. Configure the stop path. Publish a Spanish stop instruction, test its inbound route, and confirm that it creates a suppression entry with the intended scope. Export or inspect a test suppression before launch.
  6. Preflight the audience. Check the suppression ledger for every channel you might use. For voice, run the country=AR DNC scrub and retain its freshness fields. Remove every recipient that is suppressed, objected, or unresolved under your tenant policy.
  7. Approve the launch. Attach the country-rule response, sender approval, KYC evidence, consent coverage, suppression result, DNC result, and final message copy to the campaign review. The defensible posture is: an approved, identifiable sender; current tenant evidence for the chosen basis; a working Spanish stop path; a checked suppression ledger; and, for covered voice marketing, a fresh Argentina DNC scrub.