DNC for BPOs Running Mexico and Argentina

DNC LATAM · Compliance guides

A BPO that places marketing calls for a US brand into Mexico, Argentina, or Colombia will be asked for the destination registry file, not the FTC one. The brand owns the logo. The floor placed the call. Someone has to produce a dated screening record for that campaign. If the MSA is silent, the gap shows up in the client's compliance review.

Floor operations live on DNC for contact centers. This page is the commercial relationship. Nearshore seating: nearshore call centers.

Put the registry in the MSA

Before the first +52, +54, or +57 campaign, the contract should name:

  1. Which party runs the official check (BPO, client, or shared vendor).
  2. Which registries are in scope: REPEP / PROFECO, No Llame / AAIP, RNE / CRC.
  3. Who retains screening records, for how long, and who can export them.
  4. What happens when one program spans two destination countries.

"Vendor will comply with applicable DNC laws" is not a control. It does not say whether last cycle's REPEP file is acceptable, or whether Argentina needs a current AAIP consult.

What brand auditors actually open

  • Campaign name and first dial date.
  • Country field on the check (mx, ar, co).
  • Registry release or check context.
  • Counts: prohibited, safe, invalid.
  • Proof the dialer honored prohibited numbers.

They do not want a US DNC.com PDF. They do not want a screenshot of a Spanish portal. How-to: what auditors ask for.

Multi-client floors

One BPO often runs Client A's US book and Client B's Mexico expansion on adjacent teams. Those lists cannot share a suppression file. Quota is per country on DNC LATAM, not per brand. If two clients both dial Mexico, you still buy Mexico once per organization unless you have a reason to split accounts. Do not invent a per-seat license. Independent SKU, from $500/month at 10,000 checks.

Collections overflow: DNC for debt collectors. Counsel decides whether a given recovery script is in marketing scope. You still need a way to run the official list when it is.

When the BPO should buy

Buy when you are the party who must answer PROFECO, AAIP, CRC, or the brand's audit desk. API into the dialer if you already integrate. CSV if a campaign team still exports files. API vs CSV. Access you will not get yourself: foreign company access. Annual billing charges ten months for twelve. Coming end of September: Spain, Australia, and Singapore are not live API countries.

Questions, answered

Who owns the LATAM DNC scrub in a BPO relationship? +

Write it in the contract. Compliance attaches to the party making the call, but auditors still ask the brand. Name who pulls REPEP, No Llame, and RNE, who keeps the screening record, and what happens when a campaign spans countries.

Can we reuse our US DNC vendor for client LATAM books? +

No. FTC National DNC tools do not read +52, +54, or +57. Keep that vendor for +1. Add official destination checks.

What do brand auditors ask for? +

A dated screening record for a named campaign: country, registry context, counts. Plus the Scrub Result you retained. Not a slide that says the BPO scrubs lists.

How is this different from DNC for contact centers? +

Contact centers is the floor and destination-tag story. This page is the client-contract, multi-brand, who-holds-the-artifact story.

When should the BPO buy vs the client? +

Whoever must produce the LATAM record on 48 hours notice. Either party can hold the SKU. From $500/month per country at 10,000 checks. No all-countries plan.