Do Mexico and Argentina DNC Rules Cover WhatsApp Messages?
DNC LATAM · Compliance guides
Yes. Neither Mexico’s REPEP registry nor Argentina’s Registro Nacional No Llame carves out an exception for the app a marketing message travels through. A promotional WhatsApp Business message reaching a registered number is the same kind of contact a call or an SMS would be, and both registries already cover it under language that names “messages,” not a specific transport. Teams that scrub their calling and SMS lists but treat WhatsApp as a separate marketing channel outside the dialer’s compliance stack are drawing a line neither registry draws.
Why this question comes up specifically for Mexico and Argentina
In a US-only outbound program, WhatsApp marketing is a smaller piece of the channel mix than SMS or voice. Calling into Mexico and Argentina is a different picture: WhatsApp is the default messaging app for most consumers in both countries, and the WhatsApp Business Platform (the templated-message API Meta sells to companies, distinct from the consumer app) has become a standard channel for order updates, appointment reminders, and promotional outreach precisely because adoption is so high. That popularity is exactly why it gets added to a US company’s LATAM campaign stack early, and often through a different team than the one that owns the dialer — a marketing automation platform or a CPaaS vendor’s WhatsApp integration, provisioned separately from the voice and SMS scrub the outbound team already runs.
Once a channel is provisioned by a different team, on a different platform, the assumption that follows is usually the same one teams reach for with voicemail drops or AI voice agents: this is a new piece of technology, so maybe the old registry rules don’t quite reach it yet. Mexico and Argentina don’t define their scope narrowly enough to support that assumption for WhatsApp any more than they did for those other channels.
What Mexico’s REPEP actually covers
REPEP, the Registro Público para Evitar Publicidad administered by PROFECO, applies to marketing calls and messages across regulated commercial sectors, and PROFECO can sanction a company for each call or message reaching a REPEP-registered number. That standard is about a registered number receiving marketing contact, not about which app or protocol delivered it. A promotional WhatsApp Business message sent to a REPEP-registered number is a marketing message arriving at that number’s line in exactly the sense REPEP’s own language describes — nothing in the registry’s scope exempts contact that arrives through a messaging app instead of the SMS network.
What Argentina’s No Llame actually covers
Argentina’s Registro Nacional No Llame, created under Law 26.951 and administered by AAIP, is explicit that its rules cover messages and automated calls as well as live agents. A templated WhatsApp Business marketing message is a message in exactly the sense the law names — the statute doesn’t condition that coverage on the message arriving over SMS rather than through a messaging platform. The same reasoning already covers SMS text messages reaching a No Llame-registered number; WhatsApp doesn’t sit in a different category just because the delivery mechanism is newer.
What’s actually exempt: OTPs and transactional messages
The line isn’t unlimited, and it isn’t drawn by app either. One-time passwords, delivery notifications, appointment confirmations and other transactional messages sent over WhatsApp Business stay outside REPEP’s and No Llame’s scope for the same reason a transactional SMS or a fraud-alert call does: neither registry regulates account-servicing contact, only marketing and advertising contact. A bank sending a WhatsApp delivery confirmation isn’t making the kind of contact either registry was built to let consumers opt out of. The distinction is the purpose of the message, not the channel it rides on — a promotional WhatsApp template advertising a renewal discount is marketing contact regardless of how transactional the same company’s other WhatsApp traffic might be.
“It’s a messaging app, not SMS” doesn’t hold up here
The argument that a messaging-app platform sits outside a Do Not Call registry’s reach depends on the registry defining its scope narrowly around a specific delivery mechanism — the same kind of argument made, and rejected, for ringless voicemail drops and for robocalls and predictive dialers. REPEP and No Llame don’t define “message” with a transport requirement attached to it; both describe their scope as marketing calls and messages reaching a number. A WhatsApp Business template message fits that description the same way an SMS does, and the fact that WhatsApp runs over an internet connection rather than the SMS network doesn’t change which number it reaches or what the message is for.
Where this actually bites in practice
WhatsApp Business campaigns tend to get provisioned through a CPaaS or marketing automation vendor’s WhatsApp integration, set up once during onboarding and then left to pull contact lists from wherever marketing’s CRM export points, rather than from the same scrubbed list the dialer uses. That’s the same propagation gap already covered for SMS: a channel added after the core compliance stack is built doesn’t automatically inherit the scrub the rest of the program already runs, because nobody framed WhatsApp as “placing contact” the way a dial or a text clearly is.
What this means operationally
For a US-based outbound program running WhatsApp Business messaging into Mexico or Argentina alongside voice and SMS, the standard doesn’t change by channel:
- The same phone number list gets scrubbed once, before it’s split between a dialer, an SMS platform, and a WhatsApp Business integration, rather than assuming WhatsApp inherited a result scrubbed for a different channel.
- A WhatsApp Business vendor or module counts as part of the calling and messaging stack, not as a side channel outside the registry check, if it has a phone number and a destination.
- The screening record covers WhatsApp contact the same way it covers calls, SMS, and voicemail drops, since an auditor reviewing a complaint about a WhatsApp message will ask for the same dated evidence covered in how DNC scrubbing works.
The practical fix
The underlying problem isn’t a gap in REPEP’s or No Llame’s language; it’s that a WhatsApp Business channel usually gets provisioned by a team that owns marketing automation rather than the dialer, and gets treated as outside the compliance stack because it doesn’t look like a phone call. DNC LATAM checks a phone number against the current official REPEP or No Llame release regardless of which channel is about to contact it — live agent, SMS, WhatsApp Business, or voicemail drop — country in, phone numbers in, a clear prohibited-or-not answer out, with one dated record either channel can point to. The registry doesn’t ask which app sent the message, so the check in front of it shouldn’t either. The same question comes up again for RCS business messages, the carrier-native channel CPaaS vendors have started adding alongside SMS and WhatsApp.