Do You Need Consent to Cold-Call Argentina?

DNC LATAM · Compliance guides

No — Argentina does not require a company to obtain consent before the first call to a number that isn’t registered with the Registro Nacional No Llame. Like Mexico, Argentina runs an opt-out system under Law 26.951: a number is fair game until a consumer registers it or tells the caller directly to stop. But Argentina adds a piece Mexico’s model doesn’t have — a documented consent override that can beat a registration, and a specific standard for what that record needs to contain. That override is where most of the confusion for US outbound teams actually sits.

Opt-out first, override second

The baseline is the same shape as Mexico’s: consumers register mobile or fixed lines for free, registration stays active until withdrawn, and an unregistered number carries no consent requirement for a first call. Our Argentina Do Not Call guide covers the registry mechanics in full. Where Argentina diverges is what happens after a number does show up on the registry. A registration isn’t automatically the end of the conversation — a company that can produce documented prior consent for that specific number can still call it, registration notwithstanding.

That’s a materially different question than the one Mexico’s model raises. In Mexico, consent mostly matters as a backstop for existing customers, addressed briefly in do you need consent to cold-call Mexico? In Argentina, the same override sits inside the formal review process a regulator runs once a complaint is filed — which means the record needs to hold up to more than an internal policy check.

What the review actually asks

As covered in Argentina No Llame: how complaints become sanctions, a complaint review comes down to two questions, asked in sequence: was the number registered at the time of the call, and if so, did the company have documented prior consent that overrides that registration? The second question only gets asked once the first comes back “yes” — which is why teams that treat consent as a nice-to-have general practice, rather than a per-number record built for exactly this question, tend to have nothing to produce when it’s actually asked.

What “documented” needs to mean

A consent override isn’t a blanket claim that “we have a relationship with this customer.” The standard that holds up is the same one covered in what a screening record is and what auditors ask for: a specific, dated record tied to that specific number, not a general statement about the account. For a consent override in Argentina, that means being able to point to when consent was obtained, for what kind of contact, and for which number — separate from whatever screening record shows the registry check itself. A company that maintains a customer relationship but never logged a dated consent event for the phone number in question is in the same position as a company with no consent claim at all, once a specific call is under review.

Where this catches foreign teams off guard

US teams expanding into Argentina tend to bring one of two wrong assumptions with them. The first is treating Argentina like a pure opt-out system with no override path at all, which leads to abandoning a number the moment it appears registered — sometimes unnecessarily, if a real documented consent record exists for it. The second, more common mistake is the opposite: assuming an existing customer relationship is self-evidently enough to keep calling a registered number, without ever having logged the specific consent event that would actually support that call under review. As detailed in TCPA vs. Mexico and Argentina DNC rules, this is a broader pattern — assuming a consent framework or a customer relationship that works one way domestically transfers unchanged across the border. It doesn’t, and Argentina’s specific two-question review is exactly the kind of detail that assumption skips past.

There’s a structural reason this matters more in Argentina than it might elsewhere in the region: each call to a registered number without a valid override can be treated as its own infringement under Law 26.951, with sanctions escalating for repeat offenders. A company relying on an undocumented consent claim across a large customer file isn’t exposed once — it’s exposed on every call the review would find unsupported.

What this means operationally

For a team calling into Argentina, the practical checklist is narrower than it looks:

1. Scrub every list against the current No Llame registry before dialing — this is the baseline compliance work regardless of consent status, and it’s the same current-registry standard covered in registering for Argentina DNC compliance.
2. Log consent as a dated, number-specific event at the moment it happens — not as a retroactive justification pulled together after a number turns up registered. If the override is going to matter later, the record has to exist before that.
3. Treat a registered number without a logged consent event as off-limits, even for an existing customer, rather than assuming the relationship itself is sufficient cover.
4. Honor a direct opt-out immediately, independent of registry timing or any consent record on file — a live “stop calling me” overrides everything else the moment it’s said.

The practical takeaway

If you’re cold-calling into Argentina, you don’t need consent on file to dial an unregistered number — you need a current registry scrub and a policy that stops calling the moment a number registers, unless you can point to a specific, dated consent record for that exact number. DNC LATAM maintains the required Argentina registry access and attaches a dated screening record to every check, so the scrub half of that record exists automatically; the consent half still has to be logged by whoever owns the customer relationship, at the moment consent is actually given.