Call Opening Disclosures for Mexico and Argentina Calls

DNC LATAM · Compliance guides

Every telemarketing call into Mexico or Argentina needs to open with three things: who is calling, why they’re calling, and how the person can opt out — scripted for that country rather than copied from a US TCPA opener. That opening disclosure is a separate control from a DNC registry scrub: a list clean on REPEP or the Registro Nacional No Llame still needs a compliant opening on every call that goes out, and a perfect opening doesn’t excuse calling a registered number. Both controls have to hold at once.

A scrub and a script solve different problems

A DNC registry scrub answers one question: is this number already registered with the destination country’s official Do Not Call list, checked against current data from REPEP in Mexico or the Registro Nacional No Llame in Argentina. That check happens before the campaign is dialable, and how to scrub a calling list covers the mechanics of getting it right.

The opening disclosure answers a different question, live, on every single call: has this specific contact been told who is calling, why, and how to make it stop. A registry scrub can’t cover that moment, because it happens after the scrub has already passed the number as safe to dial. Treating the two as the same control is the gap — a clean list still needs a compliant opening, call after call.

What has to be in the opening

Three elements, every time, regardless of which script a floor is otherwise running:

  • Caller identity. State who is calling and on whose behalf, before the pitch starts. A vague or generic opener that never names the calling organization is the kind of detail a consumer complaint calls out first.
  • Purpose of the call. Say what the call is about in plain terms before asking a qualifying question. This is also what keeps a call inside or outside the scope question debt collection calls into Mexico and Argentina walks through: what the call actually offers, not what department placed it.
  • Opt-out method. Give the person a clear, immediate way to be removed from future calls — and mean it. Training agents to handle a live opt-out request covers what has to happen the moment someone uses that opt-out: acknowledge it, log it, and get it into the suppression list before the call ends, not as a note nobody downstream reads.

None of this is novel by itself. What trips up US outbound teams is assuming one script, written for a US floor, covers all three markets at once.

Why the US script doesn’t transfer

A TCPA-compliant opener is built around a US consent framework and US consumer expectations. Mexico and Argentina run different underlying models, and the opening has to reflect that difference even before the registry question comes up. TCPA vs. Mexico and Argentina DNC rules covers the broader pattern of US teams assuming a domestic standard carries over unchanged; the opening script is one of the places that assumption shows up first, because it’s the one piece of the call every agent says out loud on every dial, in whichever language the floor defaults to.

Running one script across a mixed Mexico-and-Argentina floor also risks the wrong default on the opt-out half of the opening. Mexico runs an opt-out model: a number is fair to call until it registers or the person asks to stop, so the opening doesn’t need to reference a prior consent record — it needs to make the opt-out path obvious and immediate. Argentina works differently once a number is already registered: a company can sometimes still call on a documented, dated consent override, but that override lives in a records system, not in anything the agent says at the top of the call. The opening script shouldn’t try to litigate consent status out loud either way — its job is the same three disclosures regardless of what the pre-dial scrub already determined about that number.

Build it into QA, not just a script document

A script that exists in a training deck and nowhere else doesn’t survive contact with a busy floor. The same way a live opt-out needs a logging step the agent can’t skip, the opening disclosure needs a QA checkpoint: call monitoring that specifically listens for all three elements, not just overall tone and conversion. A floor running nearshore call centers dialing both Mexico and Argentina from the same seats is the likeliest place for one script to get reused across both markets by mistake, since agent location has nothing to do with which country’s rules apply to the number being dialed.

The DNC compliance checklist for nearshore call centers already lists scripted, per-country disclosures as a standing checklist item alongside registry scrubs and consent logging — this is the detail behind that line item: what the three disclosures are, why a shared script is the failure mode, and where QA needs to actually listen for them rather than assume the training deck is enough.

Where this fits in the full program

Call opening disclosures are one pillar of a program that also includes the registry scrub itself, consent records where a country allows an override, and calling-hours discipline — see calling hours and contact rules for Mexico and Argentina for how the opening disclosure travels alongside scheduling as a second contact-rule layer that sits next to the hour itself. The Mexico Do Not Call registry and call center compliance pages cover how the scrub and the audit trail fit around it. None of this is legal advice — whether a specific script meets a given regulator’s expectations is a question for counsel familiar with that market. What’s operational, and what a compliance program can actually build and QA, is getting all three disclosures said on every call, in the right language, before the pitch starts.