What it does in the flow
This gates step 1, lead in (and re-checks before step 2, dial). Connect your own TCPA Litigator List account — it's BYOK because federal DNC registry access is per-organization and legally non-transferable between tenants — and every incoming lead is checked against it automatically: clear, DNC hit, or known-litigator hit. The raw provider response is stored as evidence on the lead, timestamped, so you have a compliance trail if a scrub is ever questioned.
Leads aren't just scrubbed once. If a lead has been sitting in the queue more than 31 days, it's re-scrubbed before the dial attempt — the window the FTC's safe-harbor guidance treats as current for DNC purposes.
Current status: built, final verification in progress
The provider adapter, encrypted credential storage, intake-time scrub, and the 31-day re-scrub are all implemented and working in the app today. We're holding the Live badge for this integration until we've run a final verification pass against the real TCPA Litigator List API with live test numbers, confirming clear/DNC/litigator results all come back and get stored correctly.
FAQ
Why is DNC scrubbing bring-your-own-key instead of built into the platform?
Federal Do-Not-Call registry access (SANs) is issued per organization and can't legally be shared or resold between tenants. Connecting your own account keeps the compliance responsibility and the data access where it belongs.
What happens to a lead that hits the litigator list?
It's stored but marked ineligible with the specific reason (litigator_hit), and never enters the dial queue. The raw provider response is kept as evidence.
Do I have to use a DNC provider at all?
No — it's optional with warnings, not a hard block. Activating a campaign without one requires an explicit acknowledgment (recorded in the audit log), and after that you'll see a persistent amber badge until a provider is connected.