Argentina No Llame: How Complaints Become Sanctions

DNC LATAM · Compliance guides

Argentina’s Do Not Call enforcement runs on consumer complaints, not routine audits: a consumer reports an unwanted call, the enforcement authority checks whether the number was registered and whether the caller can produce a record showing it consulted the registry before dialing, and each call that fails that check can be sanctioned as its own infringement under Law 26.951. There is no inspection cycle that catches an un-scrubbed campaign before the fact — the trigger is always a specific person reporting a specific call.

That complaint-driven model changes what “compliance” actually protects you from. It isn’t protection against getting caught during a periodic check; it’s protection against not being able to answer a specific complaint about a specific call, whenever it happens to land.

Where a complaint starts

A consumer who received a call after registering their number with the Registro Nacional No Llame — or who never consented to marketing contact in the first place — can file a complaint with the enforcement authority. From the caller’s side, this means the first sign of a problem is rarely a warning letter about a general practice. It’s a specific case: one number, one call (or a pattern of calls), one date.

This is different from how US teams sometimes picture international enforcement, expecting something closer to a scheduled audit of their calling program. As covered in TCPA vs. Mexico and Argentina DNC rules, Argentina’s regulator doesn’t work that way, and neither does Mexico’s — both rely on someone reporting the call that shouldn’t have happened.

What the review actually checks

Once a complaint is open, the review comes down to two questions the calling company needs to answer, not one:

  • Was the number registered with No Llame at the time of the call? This is why a scrub run against a stale copy of the registry doesn’t hold up — the relevant registry state is whatever was current on the call date, not whatever the company happened to have on file.
  • If the number was registered, did the company have documented prior consent that overrides that registration? A pre-existing customer relationship isn’t automatically sufficient; the company needs a specific, dated consent record for that number, separate from the scrub itself.

A company that can produce a dated certificate showing the number was checked against the current registry release before the call, or a dated consent record for that specific number, has an answer. A company that can only say “we generally scrub our lists” does not — see what a DNC compliance certificate actually needs to contain for the difference between the two.

Why one call is one infringement — and why that compounds

Argentina treats each call to a registered number as a separate breach of Law 26.951, not as one incident covering however many calls a campaign made to that number. A dialer that retries an unanswered number three times across a week isn’t one problem; potentially, it’s three. And because the sanction framework escalates for repeat offenders, a company with an open pattern of complaints faces materially worse exposure than a first-time violation — the same conservative per-call estimate used in our telemarketing fine calculator only reflects a single-infringement baseline, not what stacks up across a campaign or a pattern of them.

This per-call structure is also why volume matters more than most outbound teams expect. A campaign that dials tens of thousands of Argentine numbers and gets its scrub even slightly wrong — a stale registry copy, a missed re-check before a retry, an unregistered opt-out that didn’t get suppressed in time — doesn’t have one exposure. It has as many as there are calls that shouldn’t have happened, each one a potential complaint on its own.

What foreign companies get wrong here

The companies that end up exposed usually aren’t ignoring No Llame outright — they’re treating registration and scrubbing as a one-time setup step instead of a per-campaign requirement. As detailed in registering for Argentina DNC compliance, becoming an authorized company user requires a CUIT tax identity and local credentials that most foreign companies can’t obtain directly. Once that access exists, though, the harder part is sustaining it: downloading a current copy before every campaign, not just at onboarding, and keeping a dated record tied to each specific batch of numbers dialed.

Nearshore operations running mixed-country campaigns face a version of this that’s easy to miss: an Argentina campaign can sit right next to a Mexico or US campaign on the same floor, each with its own registry, its own refresh requirement and its own consent standard. Our DNC compliance checklist for nearshore call centers treats this as a standing per-market checklist rather than a single company-wide policy, precisely because “we’re compliant” isn’t a claim that transfers across borders.

Limiting exposure before a complaint lands

The practical takeaway is that the moment to be ready for a complaint is before it exists, not after. Two things matter most:

  1. A current registry check on the actual call date, not a cached result from a prior cycle — see the full regulatory picture in our Argentina Do Not Call guide.
  2. A dated record tied to that specific number and campaign, retrievable on request, rather than a general statement that the company has a compliance process.

DNC LATAM handles the Argentina-specific part of this by maintaining the required registry access and attaching a dated certificate to every check, so the record a complaint would ask for already exists at the moment the call is placed — rather than being something a team has to reconstruct after the fact.