Purchased Lead File With Thin Consent Records
Solstice Solar buys consumer leads from an aggregator: 250,000 records for a spring campaign. The opt-in page said the consumer agreed to be contacted by selected home-improvement partners but did not name Solstice, and the aggregator cannot produce a timestamped consent record for roughly 40% of the file. Solstice has already loaded 18,000 records and placed 40,000 dial attempts. The internal do-not-call list matches 6,200 of the purchased records. The federal DNC scrub was run 45 days ago. One state where 22% of the file resides allows a private right of action and gives sellers 30 days to cure after notice. The call center works 8am-9pm across four time zones and applies a three-attempts-per-week rule. Two consumers have already emailed asking not to be called again; one was called the next day from a different campaign.
1. What would you do in the first 72 hours to contain risk? Be specific about the dialer, the suppressions and the records you preserve.
Read the worked answer
Treat this as a containment problem, not a marketing problem. Sequence matters.
Hour 1: pause the aggregator file in the dialer, keep the 18,000 loaded records inactive, and stop all campaigns that draw from it.
Hour 2: propagate the two opt-out requests across every campaign and channel, not just the campaign that received them. Revocation is not campaign-specific, and the cross-campaign callback is the clearest control failure in this fact pattern. Add both numbers to a global suppression list with a timestamp and an owner.
Day 1: run the internal DNC match against the entire 18,000 loaded records, not just the full file. The 6,200 matches suggest a meaningful number are already dialable and should be suppressed immediately. Re-run the federal DNC scrub because 45 days exceeds the typical 31-day cadence, and scrub again at the point of dialing rather than relying on an intake-time file.
Day 1-2: pull complete dial logs for the state with the private right of action, covering number, timestamp, agent, campaign, outcome and attempt count. Preserve consent records, the aggregator contract, the opt-in page capture and all suppression logs in litigation hold format.
Day 2-3: brief counsel, quantify exposure for that state, and verify calling windows in each time zone against each consumer's area code and known location. Document every action with a time and an owner.
2. What evidence of consent would you require before dialing, and how would you handle the 18,000 records already loaded?
Read the worked answer
Require evidence that ties a specific consumer to a specific disclosure at a specific moment. At minimum: the phone number as captured, a timestamp, the IP address or device identifier, the URL of the opt-in page, the exact disclosure text shown, a record that the box was not pre-checked, and a clear identification of who the consumer agreed to hear from.
A generic reference to selected home-improvement partners is weak on its own, especially where the seller is not named and the consumer cannot reasonably know who will call. Where the file sits in a state with a private right of action, I would apply the stricter standard rather than the average one.
For the 40% without any timestamped record: treat those as no consent. Do not dial them and do not send them to a re-consent campaign that looks like a sales call. If re-consent is pursued, it needs a separate, clearly disclosed opt-in with its own audit trail.
For the 18,000 loaded records, segment them into three buckets. Bucket one: full consent evidence and no suppression match, return to dialing after re-scrub. Bucket two: partial or ambiguous evidence, hold and request documentation from the aggregator with a deadline. Bucket three: no evidence or suppressed, delete from the dialer and retain the deletion record. Do not resolve ambiguity in favor of dialing to protect campaign volume; that is precisely the decision that creates liability.
3. Design a list intake and suppression standard operating procedure so this does not recur.
Read the worked answer
Build the SOP around gatekeeping, not cleanup after load.
Vendor qualification: before purchase, require a written data provenance statement, a sample of at least 500 records with consent fields populated, and the actual opt-in page text and capture. Reject files where the seller is not named or the consent language is generic. Contract for audit rights, notification duties if consent is later withdrawn, and indemnification.
Intake gates: every record must carry consent status, source, capture date and campaign identifier. Records failing validation do not enter the dialer. Run internal DNC and federal DNC scrubs at intake, then again at least every 31 days and at the point of dialing through a real-time API.
Suppression architecture: one global suppression table feeding every dialer and campaign, covering internal DNC, federal and state DNC, prior opt-outs, complaints and litigators. Revocations propagate within 24 hours, ideally in real time. Attempt caps are enforced centrally, not per campaign, and calling windows are checked against each consumer's local time.
Operational controls: monthly audits recomputing scrubs from raw data, quarterly vendor reviews, and a change log for consent language and dialer settings. Assign a single owner for list governance with authority to stop a campaign. Report suppression match rates and revocation propagation times to leadership monthly. Test the system with seeded records to prove it works before you need it to.