DNC for Dialer Platforms Calling LATAM

DNC LATAM · Compliance guides

A dialer that only scrubs the FTC National DNC Registry will happily load a Mexico campaign. The numbers are not on that file, so they look clean. Official suppression for those destinations is Mexico REPEP (PROFECO), Argentina Registro Nacional No Llame (AAIP), and Colombia RNE (CRC). The platform that places the call is the natural gate.

Integration patterns: integrate DNC LATAM with a dialer, dialer or CRM API guide. Batch vs live: batch vs realtime DNC checks. Packaging: for platforms.

Three hooks, one contract

  1. List load. When a campaign CSV or CRM sync becomes dialable, run a batch check for that country. Do not mark the campaign ready until the result is back.
  2. Dial time. When an agent or the predictor is about to place a call, send a one-number check. Refuse prohibited. Do not warn-and-continue.
  3. Schedule. Re-check parked leads when Mexico publishes a new 15-day REPEP release, and on a current-consult cadence for Argentina and Colombia.

Same public body: country plus phones. Docs: API reference.

Product copy that does not lie

If the tenant toggle says "DNC on," say which list. A US-only gate labeled as global DNC is how nearshore BPOs fail audits. Offer destination checkboxes: United States (their existing vendor), Mexico, Argentina, Colombia (this API). Coming end of September: Spain, Australia, and Singapore. Keep those in a coming state, not a live checkbox.

Tenant evidence

Persist the screening record next to the campaign object. BPO and insurance tenants will ask for a dated official-registry artifact. You can store it even when v1 did not keep the phones. Zero-retention. DNC for BPOs.

When to buy

Buy when LATAM destinations are in the tenant model, not when the first complaint arrives. From $500/month per country at 10,000 checks. Inputs from batch and realtime share that quota. Annual billing charges ten months for twelve. No automatic discount for enabling three countries. OEM if you need to resell. CPaaS persona. Paid add-on: DNC add-on for CPaaS. Cost. How tenants should run a list by hand until you ship the gate: how to scrub a calling list. Official sources they will name on an RFP: REPEP, No Llame, RNE.

Questions, answered

Where should a dialer call the DNC API? +

At list load (batch), at dial time (realtime), and on a schedule for long-lived campaigns. A CSV export inside the tenant's ops team is not enough if agents can click-to-call.

Can we ship one DNC switch for every country? +

You can ship one integration. You cannot ship one registry. Route Mexico to REPEP, Argentina to No Llame, Colombia to RNE. Keep US National DNC on the vendor you already use for +1.

Does a blocked call still need a screening record? +

Yes. The record is evidence the check ran. Counts and metadata, no phones. Tenants who serve BPOs will ask for it after a complaint.

Self-serve or OEM? +

Self-serve if the platform or each tenant buys the public API. OEM if you need white-label, raw feeds, or the right to resell. See for platforms.

When should we buy? +

When any tenant campaign can dial +52, +54, or +57. From $500/month per country at 10,000 checks. Same allowance for batch and realtime inputs.