Back to Tools

Bulk DNC & TCPA Litigator Scrubber

Screen a US lead list against the DNC-related sources used by this workflow, including federal and state DNC, complainant, and TCPA litigator data. The account-based process keeps the run, status, and protected outputs connected for operational review.

United States only Call Center Data Platform

Call Center Data Platform access required

Sign in to use this tool, or start a verified trial.

Uploads and available history remain tied to the signed-in account.

Tool information

What it does

Screen a US lead list against the DNC-related sources used by this workflow, including federal and state DNC, complainant, and TCPA litigator data. The account-based process keeps the run, status, and protected outputs connected for operational review.

How it works

  1. Upload your bulk list file
  2. Run the DNC scrub
  3. Wait for processing to complete
  4. Download clean and suppressed exports when ready

Result and compliance context

A clean result means the configured screening sources returned no match for that record. It is not legal permission to call, a compliance guarantee, or legal advice. Your organization remains responsible for consent, calling-time, campaign, state, federal, and other applicable requirements.

How the bulk scrub works

Upload a CSV or XLSX lead file with phone numbers, then start the scrub from your verified account. The workflow validates the file, identifies the phone column when possible, normalizes usable US phone numbers, and processes the configured DNC-related checks as a tracked job.

Larger files can continue in the background. Processing status, source-level hit counts, and completed downloads remain associated with the job so operations teams do not have to manage an untracked browser-only result.

Outputs retained with the job

Completed runs provide separate clean and suppressed exports plus a full-result output for review. The clean export contains rows with no returned DNC match; the suppressed export contains records flagged by the workflow; and the full result preserves the source-level statuses used in the breakdown.

Generated files use the existing private storage and protected-download workflow. Job counts help reconcile the input, processed, clean, suppressed, invalid, and error totals before a file moves downstream.

Where bulk screening fits

Bulk screening is suited to call-center operations preparing campaign files, recurring lead deliveries, or dialer imports that need separated outputs and reviewable counts. Use a single-number check for an isolated record, suppression matching for internal or client exclusion files, and managed lead-list cleaning when a source file needs broader preparation before or after screening.

FAQ

What sources does the bulk scrub check?
The current workflow requests federal DNC, state DNC, DNC complainant, and TCPA litigator checks for usable US phone numbers.
Will I get separate outputs?
Yes. Completed runs provide clean, suppressed, and full-result outputs so operations teams can review statuses and reconcile counts.
Does a clean result mean I have permission to call?
No. Clean means the configured sources returned no match. It is not legal permission, a compliance guarantee, or legal advice.
Are uploads and outputs public?
No. Files use private storage, protected download paths, and the configured retention workflow.