Why you should never load the full federal DNC list into VICIdial

It seems logical at first: load the full federal Do-Not-Call list into VICIdial's Internal DNC table so the dialer automatically blocks those numbers before it dials. The problem is that this approach breaks the system and fails the legal test at the same time. Neither outcome is acceptable.

Why it breaks VICIdial

VICIdial's internal DNC list is designed for company-specific do-not-call requests — numbers that individual consumers have asked your company not to call. In a typical operation, that list holds a few thousand to a few tens of thousands of numbers.

The federal DNC registry contains over 209 million phone numbers. Loading that volume into the internal DNC table creates a database object so large that every dialing operation requiring a DNC check grinds to a halt. The Predictive dialing engine checks each number before placing a call. With 209 million rows to scan, those checks stop completing in any usable time frame. The dialer stops functioning properly.

Why it also fails the legal test

Even if the system could handle the load, a local copy of the DNC file goes stale immediately. The FTC requires you to filter against the current registry — the official download from the FTC portal — at least once per month. A copy you loaded six weeks ago is not the current registry. Numbers added to the DNC list after your last download are not in your local copy, which means you can still dial them and face penalties.

The FTC also requires that filtering happen as part of a documented compliance process with records retained for 5 years. Filtering inside VICIdial via the internal DNC table produces no such audit trail in the format regulators expect.

The correct approach

flowchart LR
  A[FTC DNC portal] -->|Monthly download| B[External scrubbing tool or DNC.com]
  C[Raw lead list] --> B
  B --> D[Matched numbers removed]
  D --> E[Clean lead list]
  E -->|Load via lead-loader| F[VICIdial campaign]
  G[Internal DNC table] -->|Company opt-outs only| F

Filter your lead lists externally before they ever touch VICIdial. Download the DNC file from the FTC portal using your Seller account credentials, run your raw lead list through a comparison tool or a commercial scrubbing service, and import only the numbers that passed the filter into VICIdial via the Lead loader.

VICIdial does integrate with DNC.com, which provides automated scrubbing and litigator identification. If you use that service, the filtering still happens before leads enter the dialer — DNC.com sits in front of your import process, not inside it.

Keep the internal DNC table for what it is built for: recording opt-out requests that come in during calls. When an agent sets a disposition that triggers the Campaign DNC flag, that number gets added to the internal list and will not be dialed again within your campaigns. That is a few hundred or thousand records — a scale the system handles well.

**Gotcha:** If you are inheriting a VICIdial system from another operator, check the internal DNC table row count before anything else. A previous admin may have attempted the bulk load. A bloated internal DNC table will silently degrade dialing performance across every campaign even if the original load was years ago.

For the complete picture on how federal DNC compliance works in practice, see the VICIdial compliance overview. For the step-by-step pre-load filtering workflow, see how to filter your leads against the federal DNC list before loading.

Want a managed VICIdial environment where your setup is reviewed for performance and compliance issues before you go live? See VICIfast pricing.