DNC-Clean Lead Lists Don't Cover Mexico or Argentina
DNC LATAM · Compliance guides
No — a purchased lead list marked “DNC-clean” by a US vendor has almost always only been checked against the US National DNC Registry, which has no visibility into Mexico’s REPEP or Argentina’s Registro Nacional No Llame. If that list includes +52 or +54 mobiles, the “clean” label tells you nothing about whether those specific numbers are safe to dial. Teams that buy lead lists for home-services, insurance, or financial-services outbound run into this gap constantly, because the vendor’s own scrub genuinely did its job — it just was never scoped to check a registry outside the US.
Why “DNC-clean” usually means one registry, not four
A US list vendor’s compliance process is built around the FTC’s National DNC Registry and the TCPA. That process scrubs +1 numbers against the registry it was built for. It was never wired to query REPEP, Registro Nacional No Llame, or Colombia’s RNE, because those are separate official registries run by separate government authorities (PROFECO in Mexico, AAIP in Argentina, the CRC in Colombia) with no shared database with the US system. A number can be fully clear of the US National DNC Registry and simultaneously registered on REPEP — the two facts are unrelated, because nothing links the two systems together. “DNC-clean” is a claim about which registry was checked, not a universal guarantee, and the default assumption should be that it means the US one unless the vendor says otherwise.
Where this actually breaks on a real list
The failure mode is rarely a vendor lying about their scrub. It’s a file that was never supposed to contain LATAM numbers getting mixed with one that does:
- Lead-gen vendors append mobiles from multiple countries into one CSV. The vendor’s US scrub runs against +1 numbers and passes everything else through untouched, because +52 and +54 numbers were never in that scrub’s scope to begin with — not cleared, just never checked.
- A “warm leads” file gets labeled clean after only the US portion was verified. Nobody on the buying side re-splits the file by destination country before it loads into the dialer, so the whole list inherits the “DNC-clean” label even though only part of it earned it.
- Click-to-call CRMs let reps dial any inbound lead the moment it lands, including a same-day form fill from a Mexican or Argentine number that arrived after the last batch scrub ran. A list that was clean at purchase time doesn’t stay clean as new leads get appended to it.
This is the same list-hygiene problem covered in our guide to robocalls and predictive dialers: the compliance gap isn’t intent, it’s that the registry doesn’t pause coverage while a purchased file catches up to it.
Country-of-destination, not country of the vendor, decides the registry
The registry that applies is set by where the number is registered, not by where the list vendor is based, where the call center sits, or which country the brand calls home. A US company buying a list from a US vendor, dialed by a nearshore floor in Colombia, into a Mexican consumer’s mobile, still has to clear that number against REPEP — three different countries are involved in that chain, and only one of them decides which registry applies. Our guide to Mexico’s Do Not Call list and Argentina’s Do Not Call list cover what each registry actually requires before the first dial, and our international DNC lists page covers the same destination-first logic for lists that mix in other countries beyond those two.
What to ask a list vendor before you buy
A short set of questions during vendor vetting catches most of this before the list ever loads into a dialer:
- Which registry was this list checked against, and for which numbers? “DNC-clean” without a named registry almost always means the US National DNC Registry only.
- Does the file separate numbers by destination country, or is it one mixed CSV? A file that doesn’t separate by country can’t be partially trusted — the whole thing needs re-scrubbing before use.
- How recently was the list scrubbed, and does that cover leads appended since? A one-time scrub at list creation doesn’t cover same-day inbound leads added afterward.
- Is there a dated record of the scrub, not just a vendor’s verbal assurance that the list is clean? Without one, there’s nothing to produce if a complaint comes in later.
None of these questions require the vendor to know Mexican or Argentine law — they just establish what was actually checked, so the buying team knows what still needs to happen before the list is safe to dial.
The practical fix
Treat a purchased list the same way regardless of what the vendor’s label says: split it by destination country, and run every non-US number through the registry that actually covers it before the first dial. How to scrub a calling list walks through that workflow end to end, and DNC scrubbing API integration covers wiring the check into a dialer or CRM so appended leads get caught automatically instead of depending on someone re-splitting the file by hand every time new numbers land. Mexico’s REPEP refreshes on a 15-day cycle, so even a correctly-scoped Mexico scrub goes stale fast if it isn’t repeated close to the actual dial date.
The practical takeaway
A “DNC-clean” lead list is only as clean as the registry it was checked against, and for most purchased US lists, that registry is the US National DNC Registry alone. Before a list with any Mexican or Argentine mobiles goes into a dialer, split it by destination country and scrub the non-US numbers against REPEP or the Registro Nacional No Llame directly — the vendor’s “clean” label on the file as a whole doesn’t cover them. Authorities can sanction per call, so the cost of assuming a purchased list’s clean label travels across borders is higher than the cost of re-scrubbing it at the border.