DNC Opt-Out Training: What Agents Need to Do

DNC LATAM · Compliance guides

When a consumer says “stop calling me” on a live call to Mexico or Argentina, the agent’s job is to acknowledge the request, place it on the account without arguing or asking for a reason, and log it immediately with the number, date, and channel — then confirm the number is suppressed before the call ends. That single moment is the part of DNC compliance that a registry scrub can never cover, because the person on the line may never register with any official system at all. Most compliance programs train agents on scripts for pitching and objection handling and leave this moment to instinct.

Why this is a training gap, not a records gap

A registry scrub happens before the campaign is dialed. It catches every number a consumer already registered through Mexico’s REPEP or Argentina’s Registro Nacional No Llame — see how Mexico’s and Argentina’s DNC rules differ from the TCPA for how those registries work. But a live opt-out is a different event entirely: it happens mid-call, it’s directed at the agent, and nothing in the pre-dial scrub process touches it. Managing an internal Do Not Call list covers what the resulting record needs to contain and how it has to propagate to every dialer and vendor. This post is the step before that record exists — what has to happen on the call itself so the record gets created correctly in the first place.

Teams that build a solid internal-list system still get burned here, because the system only works if the agent triggers it. A screening record and a suppression database are useless if the agent who took the request never logged it, or logged it in a way that doesn’t reach the dialer running tomorrow’s list.

What the agent needs to do, in order

Acknowledge without arguing. The request doesn’t need a reason, and pushing back (“can I ask why?”, “are you sure?”) is the fastest way to turn a routine opt-out into a complaint. Both Mexico and Argentina run opt-out systems where a direct request overrides everything else the moment it’s said — see do you need consent to cold-call Mexico? and do you need consent to cold-call Argentina?.
Confirm scope out loud. “Stop calling about this” and “stop calling me entirely” are different requests. If the agent doesn’t ask, the default should be the broader interpretation — a narrower opt-out that gets treated as blanket suppression is a safe mistake; the reverse isn’t.
Log it before the call closes, not from memory afterward. The entry needs the number, the date, the channel (in this case, a live call), and the scope. A note added an hour later, reconstructed from memory, is how details like “did they say this campaign or all campaigns” get lost.
Tell the consumer it’s done. A short confirmation (“you’ve been removed from our calling list”) closes the loop and gives the consumer a specific statement to point to if the number gets called again anyway.

None of this requires the agent to know registry mechanics. It requires a script that treats the opt-out as an instruction to execute immediately, not information to pass along.

Why “I’ll note it” isn’t enough

The failure mode isn’t usually agents ignoring requests — it’s agents handling them as informal notes instead of triggering the actual suppression entry. A note in a call-disposition field that nobody downstream reads isn’t the same as an entry in the canonical suppression list every dialer checks before placing a call. If the agent’s tools require a separate manual step to actually flag the number — switching screens, filing a ticket, remembering to tell a supervisor — that step gets skipped under call volume, and the request dies at the point it was received. Training has to cover the mechanical action, not just the verbal script: which button, which field, which system, every time, with no manual handoff in between.

Country context agents should have, briefly

Agents don’t need registry-level detail, but a short context layer helps them handle edge cases without escalating every one:

In Mexico, there’s no consent requirement for the first call to an unregistered number — the registry is the primary control, not consent. That means an agent shouldn’t treat “you never had my consent to call” as a special case requiring escalation; the relevant question is only whether the number is registered or the person is opting out now, either of which is handled the same way.
In Argentina, a company can sometimes keep calling a registered number if it holds a documented, dated consent record for that specific number — but that’s a back-office question, not something an agent resolves on the call. If a consumer says a number is registered and should not be getting calls, the agent’s job is still to log the opt-out request, not to argue that a consent record might exist somewhere.

Both models converge on the same agent-facing rule: when someone asks to stop, stop, log it, and don’t relitigate registry status on the call.

Building this into onboarding and QA

A training program that only covers this once, during new-hire orientation, tends to decay as staff turns over on a nearshore floor. Three things keep it operational:

Script it explicitly, the same way calling-hours and disclosure requirements are scripted per country — see calling hours and contact rules for Mexico and Argentina for how other per-country rules get built into agent workflows.
QA-sample opt-out calls specifically, not just pitch quality. A call where the agent logged the request correctly and closed politely should score as well as a call that converted.
Test the propagation, not just the training. Have QA confirm periodically that a logged opt-out actually stops appearing in the next day’s dial list, not only that the agent said the right thing. What auditors actually ask for includes whether a specific record can be produced on request — the same standard applies to proving an opt-out was honored, not just documented.

The practical takeaway

Registry scrubs and consent records handle the numbers a system already knows about. Agent training handles the number a system finds out about live, mid-call, from the one channel no pre-dial process can reach. A short, specific script — acknowledge, confirm scope, log immediately, confirm to the consumer — combined with a suppression flow that doesn’t require a manual handoff, closes the gap that scripts built around pitching and objection handling leave open. For a nearshore floor running campaigns into both Mexico and Argentina, that training is identical across both countries even though the underlying consent rules aren’t: the agent’s job is never to adjudicate registry status, only to execute the opt-out the moment it’s requested.