Do DNC Rules Cover Robocalls and Predictive Dialers?

DNC LATAM · Compliance guides

Yes. Argentina’s Registro Nacional No Llame explicitly covers automated calls, not just live agents, and Mexico’s REPEP covers marketing calls and messages broadly enough that neither registry gives an autodialer, predictive dialer, or robocall platform a carve-out. Teams that assume “no human was on the line yet” keeps a call out of scope are reading a gap into the rule that isn’t there.

Why this assumption keeps surfacing

The confusion usually starts with a real distinction from a different jurisdiction: in the US, TCPA treats autodialed and prerecorded calls as a separate, more heavily regulated category than live agent calls, with its own consent standard. Teams that build compliance playbooks around that US framework sometimes carry the same channel split into Mexico and Argentina, assuming a predictive dialer’s abandoned call, or a fully automated IVR campaign, sits in a different compliance lane than a live cold call. Neither REPEP nor No Llame draws that line. Both registries regulate the contact — a registered number being reached for marketing purposes — not the equipment that initiated it.

What Argentina’s No Llame actually says

Argentina’s Registro Nacional No Llame, created by Law 26.951 and administered by AAIP, is explicit on this point: the rules cover messages and automated calls as well as live calls, including campaigns run from outside Argentina. See the Argentina Do Not Call list guide for the registry’s full scope. A predictive dialer that connects an agent only after a called party answers is still the entity placing the call for compliance purposes — the registry doesn’t treat the pre-connect dial as a different, unregulated event from the agent conversation that may or may not follow it. An IVR-only campaign that never transfers to a human is just as clearly in scope, since the rule names automated calls on their own, not only as a lead-in to a live call.

What Mexico’s REPEP actually says

Mexico’s REPEP, run by PROFECO, is worded slightly differently: the public registry rules apply to marketing calls and messages, and PROFECO can fine companies for each call or message reaching a REPEP-registered number. REPEP’s own published language doesn’t single out “automated” calls the way Argentina’s statute does — but it also doesn’t exempt them. The penalty structure is per contact event to a registered number, and nothing in that structure turns on whether a human or a dialer initiated the contact. A predictive dialer that reaches a REPEP-registered number has still placed a call to that number; the registry’s coverage doesn’t ask who or what dialed it.

That’s a real difference in how explicit the two statutes are, and it’s worth being precise about rather than papering over: Argentina’s law names the automated-call category directly, Mexico’s does not use that exact framing. But “not explicitly named” is not the same as “exempt,” and nothing on either country’s public registry language carves out dialer-initiated contact. Treating Mexico’s silence on the word “automated” as a loophole is the same kind of assumption-driven reading that doesn’t hold up for B2B numbers or for collections calls — the registry’s scope depends on what the contact is for, not on who or what technically placed it.

Where this actually bites

The gap shows up less in intent and more in list hygiene. A predictive dialer pulling from a live queue, rather than a pre-scrubbed static file, can place a call to a number that entered the queue after the last batch scrub ran — the dialer doesn’t know the number is REPEP- or No Llame-registered unless something checks it at dial time. An IVR blast built to reach a large list in a single run has the same exposure if the list behind it wasn’t scrubbed against the current registry release. In both cases, the automation isn’t what creates the compliance problem; it’s that automation moves faster than a manual, periodic scrub can keep up with, and the registry doesn’t pause its coverage while the dialer catches up. We cover the mechanics of keeping a live queue current in integrating DNC scrubbing into your dialer or CRM, including the specific failure mode of a predictive dialer pulling from a queue that was scrubbed before new numbers were added to it.

What this means operationally

For a US-based outbound operation running predictive dialers or automated IVR campaigns into Mexico or Argentina, the practical standard is the same one that applies to a manually dialed list: every number gets checked against the current REPEP or No Llame release before contact, regardless of what triggers the call. That means:

  • The dialer’s live queue gets checked at or near dial time, not just at list upload, so numbers added mid-campaign don’t bypass the scrub that ran before the campaign started.
  • An IVR-only campaign gets the same pre-send check as a live-agent campaign — there’s no lighter compliance tier for calls that never reach a human.
  • The screening record covers calls the dialer places automatically, not only calls an agent manually initiates, since an auditor reviewing a complaint about an abandoned or automated call will ask for the same dated evidence covered in how DNC scrubbing works.

This isn’t a different standard from the one covered in our call center compliance guide — it’s the same standard applied to a dialing method that moves fast enough to make the gap visible sooner.

The practical fix

The underlying problem with predictive dialers and automated campaigns isn’t legal ambiguity; it’s speed. A dialer that pulls from a live, constantly updated queue needs a check that keeps pace with it, not a periodic batch scrub run the night before. DNC LATAM checks a phone number against the current official REPEP or No Llame release at the point your system is about to place the call, whether that call is agent-initiated or placed automatically by a predictive dialer or IVR platform — country in, phone number in, a clear prohibited-or-not answer out, with a dated record either way. The registry doesn’t ask what placed the call, so the check shouldn’t either.