Do Mexico/Argentina DNC Rules Cover RCS Messages?

DNC LATAM · Compliance guides

Yes. Rich Communication Services (RCS) business messages reaching a REPEP- or No Llame-registered number in Mexico or Argentina count as regulated marketing contact, the same as a call, an SMS, or a WhatsApp Business message. Neither registry defines its scope around a specific messaging protocol, and RCS being carrier- and Android-native rather than app-based doesn’t change which number it reaches or why the message was sent.

Why RCS is showing up in LATAM campaigns now

RCS is the carrier and Google-backed successor to SMS — richer formatting, read receipts, verified sender branding, and the kind of interactive “rich cards” that made Apple’s eventual RCS support a notable platform shift. For businesses, RCS Business Messaging (sometimes called RBM, delivered through Google’s Business Messages or a carrier’s own RCS platform) looks a lot like a nicer SMS: higher open rates, a branded sender name and logo instead of a bare phone number, and buttons that trigger an action instead of plain text. CPaaS vendors that already route SMS and WhatsApp traffic — Twilio among them — have been adding RCS as a channel option, which means it often shows up in a US company’s LATAM messaging mix as a checkbox in an existing platform rather than a new vendor relationship.

That’s exactly the pattern that’s made every other new channel look exempt at first glance. A feature gets added to a messaging platform a marketing team already uses, nobody re-reads the Do Not Call registry’s scope before flipping it on, and the assumption that follows is the same one that showed up for WhatsApp Business messages, ringless voicemail drops, and AI voice agents: this is new enough technology that the old registry rules probably don’t reach it yet. REPEP and No Llame don’t define their coverage narrowly enough to support that assumption for RCS any more than they did for those 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 contact reaching a REPEP-registered number regardless of which channel carried it. A promotional RCS message — branded sender, rich card, call-to-action button and all — sent to a REPEP-registered number is a marketing message reaching that number in exactly the sense REPEP’s own language describes. The fact that RCS is delivered through the carrier network rather than an SMS gateway or a third-party app doesn’t change what the registry is checking: whether the number on the receiving end opted out of advertising contact.

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. An RCS marketing message is a message in the sense the law names, the same way SMS and WhatsApp messages already are. Nothing in the statute conditions that coverage on the message traveling over the traditional SMS protocol instead of RCS — the registry regulates the contact a registered number receives, not the technical standard that delivered it.

What’s actually exempt: OTPs and transactional messages

As with every other channel, the line isn’t drawn by protocol — it’s drawn by purpose. One-time passwords, delivery updates, appointment confirmations and similar account-servicing messages sent over RCS stay outside REPEP’s and No Llame’s scope for the same reason a transactional SMS or WhatsApp message does: neither registry regulates account-servicing contact, only marketing and advertising contact. A shipping carrier sending a branded RCS delivery update isn’t making the kind of contact either registry lets consumers opt out of. A retailer sending the same branded RCS card to promote a sale to that same number is.

“It’s RCS, not SMS” doesn’t hold up here

The argument that RCS sits outside Do Not Call coverage depends on the registry defining its scope around a specific protocol, which neither does. We’ve seen the same argument made, and rejected, for robocalls and predictive dialers, for voicemail drops, and for WhatsApp. REPEP and No Llame describe their scope as marketing calls and messages reaching a number, not as calls placed over a specific network or messages sent through a specific standard. RCS fits that description the same way SMS and WhatsApp do — richer formatting and carrier-level delivery don’t move the message into a different regulatory category.

Where this actually bites in practice

RCS often gets turned on as a feature inside a CPaaS platform a company already uses for SMS, which makes it easy to assume the existing SMS compliance process automatically extends to it. In practice, RCS campaigns are frequently configured as a separate messaging profile — a different sender ID, a different template library, sometimes a different internal owner evaluating the “rich” format for a specific promotion — pulling its contact list from wherever that campaign’s source data lives rather than from the same list the SMS platform scrubs. That’s the same propagation gap already covered for SMS and WhatsApp: a channel that looks like a feature toggle inside an existing platform doesn’t automatically inherit the scrub that platform’s other traffic already runs through.

What this means operationally

For a US-based program adding RCS to its Mexico or Argentina messaging mix, the standard doesn’t change by protocol:

  • The same phone number list gets scrubbed once, before it’s split between SMS, WhatsApp, RCS, and voice, rather than assuming a newly enabled channel inherited a scrub run for a different one.
  • An RCS campaign counts as part of the calling and messaging stack, not as a side feature exempt from the registry check, the moment it has a phone number and a destination.
  • The screening record covers RCS contact the same way it covers calls, SMS, and WhatsApp, since an auditor reviewing a complaint about a branded RCS 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 — both already cover “messages” broadly enough to reach a format that didn’t exist when the rules were written. The problem is that a new channel, enabled inside a platform a team already trusts, rarely gets re-checked against the registries that already apply to it. DNC LATAM checks a phone number against the current official REPEP or No Llame release regardless of which channel is about to use it — live agent, SMS, WhatsApp, RCS, or voicemail drop — country in, phone numbers in, a clear prohibited-or-not answer out, with one dated record any channel can point to. The registry doesn’t ask which protocol sent the message, and neither should the check that runs in front of it. This same discipline is the backbone of the contact center compliance standard outbound programs in Mexico and Argentina are already expected to meet.