DNC Scrubbing for Cold Calling Lists Runs on Three Clocks

TL;DR: DNC scrubbing for cold calling lists is three separate clocks, not one file wash, and a list that passed a scrub can still be uncallable because a different clock expired. The FTC safe harbor at 16 CFR 310.4(b)(3)(iv) and the FCC safe harbor at 47 CFR 64.1200(c)(2)(i)(D) both require a registry version obtained no more than 31 days before the call, and both condition the safe harbor on maintaining records documenting that process. Under 47 CFR 64.1200(d)(3) an internal do-not-call request must be recorded at the time it is made and honored within a reasonable time that may not exceed ten business days. Under 47 CFR 64.1200(d)(6) that request binds you for 5 years, and under 16 CFR 310.5(a) telemarketing records are kept 5 years, including a per-call record that names the calling number, called number, date, time, duration, and disposition. Those numbers are not trivia, they set the rescrub cadence, the opt-out service level, and the retention floor your dialer has to clear. Most teams pass the 31 day check and break the ten business day one, because a rep hears “take me off your list” and writes it in a note field no suppression process ever reads. Build the check and the record into the dialer, assign reason codes instead of a pass or fail flag, quarantine failed lookups rather than defaulting them to callable, and have counsel set the retention and jurisdiction policy.

Your vendor sent the file back marked clean. That is a statement about a file on a particular afternoon. It is not a statement about a phone number.

DNC scrubbing for cold calling lists is the process of screening numbers against do-not-call records and other suppression data before reps dial them. It is a real control. It is not a verdict that every surviving number may be called, and the gap between those two things is where teams get into trouble.

So where does the gap come from? Three clocks, running at different speeds, on different systems. Miss one and the scrub result stays green while the list goes stale underneath it.

This is operational guidance, not legal advice. Have qualified counsel decide which rules apply to your campaigns and the jurisdictions you call into.

What DNC Scrubbing for Cold Calling Lists Actually Proves

A scrub result describes the checks that ran, against the sources configured, at the moment they ran. Nothing more.

That sounds obvious until you watch how it gets used. What does a clean file actually certify? The checks that were configured, against the sources that were wired up, on the day somebody ran them. A list vendor stamps the file “pre-scrubbed” and it goes straight into a campaign without anyone asking what that label covered. A provider checks the national registry faithfully and never sees your company’s own opt-outs, because nobody wired the internal list into the request. A file screened on the first of the month gets dialed for six weeks. In each case the scrub was real and the list still drifted.

So treat the result as a dated receipt, and make it answer five questions: which sources were checked, when each check ran, which rules and jurisdictions were in scope, how matches and errors and exceptions were handled, and whether anything changed the record after screening. If your screening output cannot answer those five questions on demand, then what you are holding is a label rather than a control, and the distinction will matter precisely once, at the worst possible moment.

For what the registry is and which rules apply to a given call, start with how the National Do Not Call Registry works. This article is about what your list workflow has to do about those rules and what it has to leave behind.

The 31 Day Clock on Your DNC Registry Version

Both federal regimes name the same number, and both make it conditional.

The FTC’s Telemarketing Sales Rule safe harbor at 16 CFR 310.4(b)(3)(iv) asks that a seller or telemarketer use “a version of the ‘do-not-call’ registry obtained from the Commission no more than thirty-one (31) days prior to the date any call is made, and maintains records documenting this process.” The FCC’s parallel provision at 47 CFR 64.1200(c)(2)(i)(D) uses the same 31 day limit and the same recordkeeping condition.

The registry version itself comes from the FTC’s telemarketer portal at telemarketing.donotcall.gov, which is restricted to organizations complying with 16 CFR Part 310 or 47 CFR 64.1200 and to organizations accessing it solely to avoid calling registered numbers. Where your copy came from is part of the record.

Read the second half of that sentence again. What earns the safe harbor under either rule? Not scrubbing on its own. It is earned by scrubbing and being able to show you scrubbed. A process with no surviving evidence is, for safe-harbor purposes, uncomfortably close to a process that never ran, because the thing being evaluated after a complaint is the documentation rather than your memory of the workflow.

Now apply it to a real campaign. A six-week outbound push that gets screened once on day one is, by the final week, dialing against a registry version that is 42 days old, which means every number added to the registry in the intervening six weeks is invisible to the file your reps are working. The file never changed. The clock did.

The 10 Business Day Clock on Internal DNC Requests

This is the clock most teams actually break, and it has nothing to do with a vendor.

Under 47 CFR 64.1200(d)(3), when someone asks your company not to call again, you must record the request and place the name and number on your do-not-call list at the time the request is made. Honoring it must happen “within a reasonable time from the date such request is made,” and that period “may not exceed ten (10) business days from the receipt of such request.”

Two separate obligations sit in that rule. Record it now. Honor it inside ten business days. Which one do teams miss? Almost always the first.

Here is the failure mode. A rep gets a live answer, hears “take me off your list,” and types it into the call notes because that is the field in front of them. The note is accurate. It is also invisible to the suppression process, the next list import, and the campaign the number gets loaded into on Thursday. Nobody acted in bad faith, nobody ignored a rule they knew about, and the number stays callable anyway, because the request was captured as prose in a field that no downstream process reads. It never became data.

So the diagnostic question is not whether your reps know the rule. Where does a verbal opt-out land, how does it reach the suppression list, and how long is that trip? If the answer involves someone reading call notes, you do not have a ten business day service level. You have a hope.

Ten business days is a ceiling, not a target. Internal suppression should propagate in minutes, because unlike the registry version it is entirely inside your own systems.

The Five Year Clock on DNC Requests and Call Records

The third clock outlives the campaign, the CRM migration, and usually the rep.

A do-not-call request “must be honored for 5 years from the time the request is made” under 47 CFR 64.1200(d)(6). Separately, 16 CFR 310.5(a) requires a seller or telemarketer to keep telemarketing records “for a period of 5 years from the date the record is produced unless specified otherwise.” Note that the FTC amended this section effective May 16, 2024, so older write-ups quoting a 24 month retention period describe superseded text.

What has to be in those records is specific. Under 16 CFR 310.5(a)(2) the record of each telemarketing call includes the telemarketer that placed it, the seller it was placed for, whether the call was outbound, whether it used a prerecorded message, the calling number, called number, date, time, and duration, and the disposition of the call, including whether it was answered, connected, dropped, or transferred.

So what do the two five year clocks mean together? Put them next to each other and the operating consequence is plain. A suppression request you took in 2026 still binds you in 2030, and the evidence that you honored it has to survive the same stretch. That is a retention requirement, not a reporting preference, and it should be the first question you ask about any system holding your call data.

So the number that matters is not how fast your scrub runs. It is whether a record from five years ago is still retrievable with its disposition intact.

DNC Scrubbing Belongs in the Dialer, Not the Spreadsheet

Both safe harbors ask for the same two halves: a process that prevents calls to suppressed numbers, and records documenting that process. Spreadsheets are bad at both. They get copied, filtered, emailed, re-uploaded, and merged with a newer export, and any one of those steps can quietly restore a number somebody already suppressed without leaving a trace of when it happened or who did it.

The halves belong where the call happens. Kixie’s National DNC compliance capability checks calling lists against the National Do Not Call Registry and applies suppression workflows, and Kixie’s own documentation is explicit that customers remain responsible for their calling practices and should get legal guidance for their programs. Treat that boundary as correct. The tool runs the check and keeps the evidence. It does not decide whether your campaign is lawful.

The second half is the one teams forget to shop for. Which half does your current setup actually cover? Because call outcomes and dispositions log automatically into the CRM alongside calls, texts, and recordings, the per-call fields 16 CFR 310.5(a)(2) names are produced as a byproduct of dialing rather than reconstructed later from memory. That is the difference between having a record and building one after a complaint arrives.

The same logic applies to list velocity. If reps work a list through a PowerDialer session rather than hand-dialing, the volume per hour goes up and the stale-list window gets proportionally more expensive, which is an argument for tighter rescrub intervals, not looser ones.

Here is the test. Can a rep reach a number your company suppressed last Tuesday? If the suppression lives in the dialer, no. If it lives in a file somebody maintains, probably yes.

DNC Scrubbing Workflow for Cold Calling Lists

The order matters more than the tooling. Why? Each step exists because skipping it reintroduces a record you already excluded, usually through a merge or an upload that looks routine.

Document the list source. Record who supplied it, when it arrived, which campaign it feeds, and what the supplier claimed about consent or prior screening. A vendor’s “pre-scrubbed” label is an input to your process, not a replacement for it.

Normalize the numbers. One consistent format, extensions split out, placeholders removed, malformed entries flagged. Keep the original value so the trail back is intact.

Deduplicate without losing restrictions. Decide whether duplicates resolve by number, contact, account, or household, then merge so the most restrictive status wins. The classic bug is quiet and mechanical: a fresh marketing record overwrites an older opt-out purely because it carries a newer timestamp, and the merge logic was written to prefer recency rather than restriction.

Preserve the metadata. Lead source, acquisition date, jurisdiction indicators, consent details, campaign assignment, prior contact history. A bare phone number cannot be evaluated and cannot be audited.

Run the checks your policy names. Federal, state, internal, and campaign-specific suppression, as scoped by counsel. State requirements change and vary, so review them rather than freezing them in a spreadsheet, and see telemarketing laws by state for how much that layer can differ.

Assign reason codes, not a pass or fail flag. Internal opt-out, registry match, invalid number, duplicate, missing evidence, provider error, manual review required. A single boolean destroys the one thing you will need later, which is why a record was excluded.

Quarantine the ambiguous ones. Failed lookups, conflicting data, and incomplete records should never fall through into the callable pool. Route them to a named owner with a resolution path.

Export approved records only. The screened output becomes the controlled source for the campaign. Ad hoc uploads that bypass suppression are the single most common way a clean process produces a dirty dial.

Store the trail. Screening timestamp, source version or provider response, applied policy, result, reason code, and every later status change, retained per the policy counsel approved.

Batch and Pre Dial DNC Scrubbing for Call Lists

No single pattern fits every team. The right design follows list velocity, campaign length, and how fast your internal opt-outs move.

Batch screening runs the file before it enters a campaign. It is simple, it makes exception review easy before activation, and its weakness is exactly the 31 day clock: the longer the campaign runs, the more the original check ages.

Scheduled rechecks rerun active records on an interval. This suits anything that outlives a single calling session. Set the cadence from the rules, the source update schedule, and campaign risk, not from a number you read in a vendor article.

Event-based checks fire when a lead is created, imported, reassigned, or added to a sequence. Good for stopping ineligible records early, though you still need coverage for changes between the event and the call.

Pre-dial checks evaluate the record close to the moment of contact. They shrink the screening-to-dial gap to almost nothing, and in exchange they introduce a set of operational questions you now have to answer on purpose rather than by default, covering provider availability, latency, failed responses, caching behavior, and where the result gets stored. Decide explicitly whether a timeout blocks the call or routes it to review. A timeout must never default silently to approval, because that converts an outage into permission.

Most mature setups layer these. Batch at intake, internal suppression applied immediately, and additional screening for long-running campaigns. The architecture should make the most restrictive current status visible to the dialer at dial time.

When to Rescrub DNC Cold Calling Lists

There is no universal cadence worth copying from a vendor page. But the 31 day registry limit gives you a hard outer bound, and your campaign length tells you whether that bound binds.

So how long does your campaign actually run? A campaign shorter than the interval between scrubs is fine on one check. A campaign longer than it is not, and the fix is a recheck schedule rather than an optimistic note in a runbook.

Set two separate service levels. Internal suppression should propagate immediately, because the ten business day rule is a ceiling and the data is yours. External screening gets a named owner, a documented refresh schedule, and an escalation path for provider failures. Write down who gets paged when the screening service is down, because “the vendor was unavailable” is not the same as a passed check and should never be recorded as one.

DNC Scrubbing Mistakes in Cold Calling Lists

Trusting an old scrub. The result reflects its date, scope, and source data, not the conditions at dial time.

Checking one registry. National, state, and company-specific records do different jobs and fail in different ways.

Reading “not matched” as permission. A clean result says nothing about consent, call purpose, dialing method, timing, or jurisdiction.

Losing opt-outs during imports. A newer file should never overwrite a more restrictive status.

Letting the rep’s note be the system. A verbal opt-out typed into call notes is not on your do-not-call list, and the ten business day clock started running the moment the buyer said it.

Ignoring provider failures. An unavailable screening service is an unknown, and unknowns belong in quarantine.

Keeping thin records. A “scrubbed” flag with no sources, timestamp, or reason code cannot support the safe harbor that the flag was supposed to earn.

DNC Scrubbing FAQs for Cold Calling Lists

Does DNC scrubbing make a cold calling list compliant?

No single scrub establishes compliance. It is one control inside a broader process that also covers consent, internal opt-outs, call purpose, dialing method, timing, jurisdiction, and recordkeeping. The federal safe harbors treat scrubbing as one of several conditions, not as the whole test.

How often do I have to scrub against the national registry?

Both the FTC and FCC safe harbor provisions reference a registry version obtained no more than 31 days before the call is made. That is an outer limit for the safe harbor rule, so campaigns running longer than that window need a recheck schedule rather than a single screening at intake.

How fast must an internal do-not-call request be honored?

47 CFR 64.1200(d)(3) requires recording the request at the time it is made and honoring it within a reasonable time not exceeding ten business days. Because internal suppression is entirely within your own systems, most teams should target minutes and treat the ten business day figure as a ceiling.

How long do we keep DNC and call records?

A do-not-call request must be honored for 5 years under 47 CFR 64.1200(d)(6), and 16 CFR 310.5(a) sets a 5 year retention period for telemarketing records, including per-call details such as the calling number, called number, date, time, duration, and disposition. Counsel should approve the retention periods and access controls that apply to your organization.

What should we ask a DNC scrubbing vendor?

Ask which sources are checked and how often each refreshes, what the response looks like when a lookup fails, whether results are returned with reason codes or a single flag, how long screening evidence is retained, and whether the output can reach your dialer without a manual file step. Those answers decide whether the vendor supports the recordkeeping half of the safe harbor or only the checking half.

Sources

• Electronic Code of Federal Regulations, 16 CFR 310.4, Abusive telemarketing acts or practices, Telemarketing Sales Rule safe harbor and the 31 day registry version requirement. https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-310/section-310.4 Reviewed October 18, 2026.
• Electronic Code of Federal Regulations, 16 CFR 310.5, Recordkeeping requirements, 5 year retention and required per-call record fields, amended effective May 16, 2024. https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-310/section-310.5 Reviewed October 18, 2026.
• Electronic Code of Federal Regulations, 47 CFR 64.1200, Delivery restrictions, national registry safe harbor, internal do-not-call procedures, ten business day limit, and 5 year honoring period. https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-64/subpart-L/section-64.1200 Reviewed October 18, 2026.
• National Do Not Call Registry, telemarketer access portal operated for the Federal Trade Commission, organizational eligibility, subscription management, and phone number downloads. https://telemarketing.donotcall.gov/ Reviewed October 18, 2026.

Sources verified by the Kixie Research Team on October 18, 2026.