Informational

DNC scrubbing and Do-Not-Sell compliance

Two of the fastest ways a lead operation gets into trouble are calling numbers on a Do-Not-Call list and selling data after a consumer opted out. Both are solvable in the routing layer, if the system enforces them before a lead is ever delivered.

1 min readUpdated Jun 2026Lead Distribution

DNC scrubbing

Leads are scrubbed by phone before they're exported or handed to a dialer, checked against the Blacklist Alliance API, a commercial DNC and litigator blacklist, and an internal suppression table the platform maintains. Any number that matches is dropped from the set, so it never reaches a buyer or a dialer, and every scrub logs how many records went in and how many came out.

  • Optizmo suppression drops, imported daily from S3
  • Do-not-call outcomes seeded from past dialer campaigns (Gridspace)
  • Consumers who submit the site's own Do Not Sell My Info form

Exports scrub on phone; outbound batches scrub on phone and email, against whichever of those sources are selected for that run.

Do-Not-Sell (CCPA)

When a consumer exercises Do-Not-Sell, the system has to honor it, suppressing that record from sale going forward, not just flagging it.

That's exactly how it works here. The site's Do Not Sell My Info form posts to a do-not-sell endpoint that normalizes the number and writes it into the same suppression table the scrub reads, tagged as a do-not-sell request. From that point the number is dropped from every export and outbound batch, so the opt-out is enforced at delivery time rather than left as a flag someone has to remember to check.

FAQ

Do you scrub leads against DNC?
Yes. Against DNC lists and an internal suppression list, before routing.
Can you honor Do-Not-Sell requests?
Yes. Suppressed records are removed from sale at the routing layer.