Batch vs Realtime DNC Checks for Dialers
DNC LATAM · Compliance guides
Dialers fail DNC in the gap between "we scrubbed the file" and "the agent just added a lead." Batch checks clear a list before it becomes dialable. Realtime checks gate the call that is about to happen. Official LATAM registries still need both, because Mexico REPEP, Argentina No Llame, and Colombia RNE change on their own clocks, and your CRM does not wait.
This page is the operations split. Engineering walkthrough: dialer and CRM integration. Surface choice: API vs CSV.
Use batch when the list is the unit
Batch is the right default at campaign import. Thousands of numbers, one country field, one screening record, one decision: this file may go to the dialer. It is also the right default for a nightly or weekly re-check of a nurture pool that sits for weeks. Mexico's 15-day REPEP cycle makes a scheduled batch non-optional if the same records stay loaded across a release.
Panel CSV is batch. So is one API request with a large
phones array. The public product does not expose
provider-side chunks as partial customer results. The job succeeds or
fails as a unit.
Use realtime when a human or queue can surprise you
Click-to-call, preview, and predictive queues all create numbers that were not in this morning's export. A realtime check is a one-number (or small) array sent when the system is about to place the call. If the API returns prohibited, the dialer must refuse the call, not toast a warning and proceed.
Realtime does not replace batch. Running only single checks on a 50,000-row load is slower and burns the same quota in a worse pattern. Running only batch on a CRM where every rep can call anything leaves a hole the size of your inbound lead flow.
A working mix
| Moment | Check | Why |
|---|---|---|
| Campaign import | Batch | Nothing is dialable until the list clears |
| Agent clicks Call | Realtime | Lead may have arrived after the batch |
| Predictive pull | Realtime | Queue restocks continuously |
| Long-lived sequence | Scheduled batch | Registry status changes while the record waits |
Country routing still comes first
A realtime gate that always sends mx will miss an
Argentine mobile that entered the same lead object. Route on the
number, not the campaign nickname. Keep the registry identifier on
the stored result. A boolean "DNC clean" that merges three countries
hides which list fired.
Refresh rules differ. A 31-day US TSR habit leaves Mexico stale for half of every REPEP cycle. Argentina and Colombia want a current consult, not a monthly file. Country comparison.
What to store either way
Timestamp, country, registry context, counts on the screening record. Per-number classes on the Scrub Result you keep. Test before production: a known registered number must be blocked end to end, and the record must be retrievable. A log line that does not stop the call is monitoring, not compliance.
Platforms: DNC for dialer platforms. Privacy: zero-retention. Buy the country SKU, from $500/month at 10,000 checks, then choose batch and realtime on the same allowance.
Questions, answered
What is a batch DNC check? +
You send many phone inputs in one request (or one panel CSV) and get one complete result for that list against one country registry. Use it at list load and on a schedule for long-lived campaigns.
What is a realtime DNC check? +
A check that fires when an agent or dialer is about to place a call, so numbers added after the last batch cannot slip through. Typical in CRMs with click-to-call and predictive queues.
Does DNC LATAM support both? +
The public API accepts a country field and a phone array. Use a larger array for list load. Use a one-number array at dial time. Panel CSV is batch-only. See the API docs for v1 vs durable v2.
Is realtime a different SKU? +
No. Inputs consume the same per-country monthly allowance. Invalid inputs count. Choose the call pattern that matches the risk, not a second product.
When should a dialer platform buy? +
When tenants load LATAM lists or place live +52, +54, or +57 calls. From $500/month per country at 10,000 checks. OEM terms are separate.