DNC scrubbing for final expense call floors: which lists, which exemptions, and what a vendor’s “scrubbed” label leaves to you

DNC scrubbing removes, before you dial, the numbers you may not call: those on your company do-not-call list, on any state list that binds you, and on the National Do Not Call Registry (checked against a copy no more than 31 days old) unless you hold signed written permission naming you or a business relationship of your own.

These are the federal rules as in force on October 22, 2026, with a few state examples, for licensed final expense agents, agency owners and call-center managers who buy leads, transfers or aged records. This is not legal advice.

What is DNC scrubbing, and which lists must a final expense buyer scrub against?

DNC scrubbing is a comparison run before dialing: each number on a call list is matched against the do-not-call lists that bind the business the calls are made for, and matches are removed. On a final expense floor that business is usually you. The FCC calls it the seller, “the person or entity on whose behalf a telephone call or message is initiated” (47 CFR 64.1200(f)(10)), so your lists apply whoever presses dial. Here a vendor is any business you buy leads, calls or scrubbing from; the FTC’s registry calls one that dials or scrubs for you a “TM/SP”, a telemarketer or service provider.

Selling insurance does not take a floor outside the registry rule. The FCC’s version opens “No person or entity shall initiate any telephone solicitation to”, lists no insurance exemption, and reaches sales calls and texts to cell phones as well as home lines (64.1200(e)). The FTC, which enforces the other federal rule, the Telemarketing Sales Rule (TSR), notes in its Q&A that “Some sellers are exempt from the FTC’s rules, but are required to access the registry under the FCC’s rules.”

The matrix covers five lists; only the first three are do-not-call lists set by law. As in force on October 22, 2026:

The scrub itself runs in six steps:

1. Download the registry data for your subscribed area codes under your own SAN.
2. Remove registered numbers, unless the record carries one of the exemptions below.
3. Remove every number on your company do-not-call list.
4. Apply each state list that binds you, by name.
5. Stamp each record with the registry download date.
6. Block dials more than 31 days after that date, and re-scrub against a fresh download.

A do-not-call scrubber, the software that runs this comparison, should run it under your SAN and log the download date and each list it applied. The steps apply to every source a floor dials, and matter most on aged segments you scrub before you dial, because a number can be registered in the months between the consumer’s inquiry and your first call.

How current must the national registry copy be, and whose registry access counts?

To keep either federal safe harbor, a registry copy must be no more than 31 days old on the day of each call, as the FTC also tells registry users, and the registry access behind it should be yours. When a vendor scrubs for you, check both.

The clock runs from the download, not the delivery

Both federal safe harbors use the same clock. The FCC’s needs “a version of the national do-not-call registry obtained from the administrator of the registry no more than 31 days prior to the date any call is made”, and the TSR’s uses the same 31 days (16 CFR 310.4(b)(3)(iv)). One vendor explainer, PossibleNOW’s, credits the clock to the TSR alone; for an insurance seller the FCC’s version carries the same 31 days, so the clock applies whatever the TSR’s reach.

The 31 days start when the registry data was obtained, not when a vendor delivered the list. A list scrubbed against a download three weeks old has about ten days left, whatever date it reached your CRM, and on a segment you work longer than that, the 31-day clock on an aged segment forces a re-scrub against a fresh download.

Your registry account, not the vendor’s

Registry access belongs to the business the calls are made for. The FTC’s Q&A says “the Seller must have its own subscription and SAN, separate from the Telemarketer's subscription and SAN”; a vendor that subscribes for itself gets “a SAN that can be used only by that company”, and one working under your SAN “will not have to pay a separate fee for that access.” The FCC’s safe harbor asks for a caller that “purchases access to the relevant do-not-call data from the administrator of the national database” and shares that cost with no one (64.1200(c)(2)(i)(E)), and the TSR makes a vendor accessing the registry for clients “provide each seller's unique account number” (16 CFR 310.8(e)).

A scrub run on a vendor’s own SAN therefore shows that the vendor reached the registry, not that you did. One scrub tool builds this in: Contact Center Compliance’s DNCScrub page says “A subscription to the National Do Not Call list is required to use DNCScrub®.” Ask each vendor whose SAN its scrub ran under, and check the answer under VIEW SAN SHARING in your own registry account (step 6 of the access steps below).

Which registered numbers may you call anyway? Business relationships by lead source, and written permission that names you

A lead buyer can hold two registry exemptions, as the FTC calls them: written permission that names it, and an established business relationship of its own. The FCC’s third, a personal relationship with “any family member, friend, or acquaintance of the telemarketer making the call”, rarely fits a floor dialing bought leads.

Written permission that names you

The FCC wants an agreement, signed and in writing, in which the consumer agrees to be called by “this seller” and gives the number (64.1200(c)(2)(ii)). The TSR’s version must authorize calls “by or on behalf of a specific party”, and it accepts an electronic or digital signature that applicable federal law or state contract law recognizes. Permission given aloud and never recorded is neither signed nor written, and consent naming only the vendor or unnamed partners does not name you. Whether a recorded-voice or keypress agreement qualifies, or a place on a long partner list makes you “this seller”, is for counsel, judged from the exact consent language on the lead form.

The established business relationship exemption: a relationship of your own

Under the FCC’s TCPA rules, an established business relationship is one “formed by a voluntary two-way communication between a person or entity and a residential subscriber”, based on a purchase or transaction with that entity in the 18 months before the call, or an inquiry or application about its products in the three months before (64.1200(f)(5)). The TSR counts 540 days and 90 days (16 CFR 310.2(q)), and the FTC’s Q&A runs the 18 months “from the date of the last payment, transaction, or shipment between the consumer and the seller.” Three limits apply on a final expense floor:

• It stays with the entity. An inquiry relationship belongs to the business the consumer inquired with and “does not extend to affiliated entities unless the subscriber would reasonably expect them to be included” (64.1200(f)(5)(ii)). Nothing in the rule text or the FTC’s Q&A extends it to a later buyer of the record, so treat a bought record as carrying none.
• A do-not-call request ends it, “even if the subscriber continues to do business with the seller” (64.1200(f)(5)(i)).
• It is not robocall consent. Autodialed or prerecorded telemarketing to a cell phone, and prerecorded or artificial-voice telemarketing to a home line, still need prior express written consent (64.1200(a)(2)–(3)), so where a relationship is your only basis, keep autodialers and artificial or prerecorded voices off the call; dialing by hand is the simple way.

Registered numbers by lead source

“Possible” below means a source can carry the exemption; only the record’s consent text, signature and dates show whether it does. Where no rule text settles a cell, it says “ask counsel”, and until counsel answers, treat that cell as giving you no exemption. Pair the table with the one question to settle for each lead type before you pay.

How fast must a company-specific do-not-call request be honored, and how long is it kept?

A seller has to honor a do-not-call request within a reasonable time, no later than ten business days after receipt, and keep honoring it for five years. The FCC rule makes every business placing telemarketing calls keep a written policy “available upon demand”, train everyone engaged in its telemarketing and record each request “at the time the request is made”, and the five years run “from the time the request is made” (64.1200(d)(1)–(3), (d)(6)). States set their own periods too: Virginia’s law says a request “shall be honored for at least 10 years from the time the request is made” (Va. Code §59.1-514(A)), and the state-by-state post lists others.

The ten-business-day limit is recent. Until April 10, 2025, the same paragraph read “This period may not exceed 30 days from the date of such request”; the current text has applied since April 11, 2025 (89 FR 82518), so check that older scripts and vendor contracts no longer say 30 days.

The rule also settles who is bound:

• Every telemarketing call must name the caller, the business it is made for and a number or address for that business (64.1200(d)(4)), so a request can be aimed at you.
• A request reaches affiliates only where the consumer “reasonably would expect them to be included” given the caller’s identity and the product (64.1200(d)(5)).
• When a vendor or setter keeps the list, “the person or entity on whose behalf the call is made will be liable for any failures to honor the do-not-call request” (64.1200(d)(3)).

The TSR separately bars calls to anyone who has said they want no calls “by or on behalf of the seller whose goods or services are being offered” (16 CFR 310.4(b)(1)(iii)(A)), with no processing window of its own. The FCC’s company-list rule binds a final expense seller whatever the TSR’s reach. Where the TSR applies, a seller and its telemarketer may agree in writing which party keeps the do-not-call record, and without such an agreement both are responsible for it (16 CFR 310.5(e)).

What does a vendor’s “DNC-scrubbed” label leave to the buyer?

A vendor’s scrub label leaves four things with you: the 31-day clock, the registry account, your company do-not-call list and the exemptions. Read each claim against the rule it touches:

One scrub service, theDNCproject (home page read October 22, 2026), offers “all 10 state lists”, names them (“We cover Colorado, Florida, Indiana, Louisiana, Massachusetts, Missouri, Pennsylvania, Tennessee, Texas and Wyoming.”) and tells buyers to “Scrub against every state that runs its own list.” The ten leave out Oklahoma’s Attorney General registry, among other state lists the state-by-state post names, and count Wyoming, whose statute bars sales calls to numbers on the Direct Marketing Association’s private Telephone Preference Service list rather than a list the state keeps. Ask which list a “Wyoming” scrub uses.

Telemarketing leads test every row at once, because a call center dialed the consumer before you did.

Where do litigator and reassigned-number checks fit?

Litigator and reassigned-number checks sit outside the do-not-call scrub. A litigator list is a vendor product that no rule requires and neither safe harbor names, so run it after the required scrub, never instead of it, and treat it as a screen for frequent TCPA plaintiffs, not a legal defense. The Reassigned Numbers Database safe harbor protects a caller only from “the prohibitions in paragraph (a)(1), (2), or (3)” of 64.1200, the consent rules for autodialed and prerecorded calls (64.1200(m)), so it is no defense to a do-not-call claim; the aged dial plan covers when to query it.

How do sellers get registry access, and what does it cost?

Registry access is bought online by area code: in fiscal year 2027 the first five are free, each further one costs $85 a year, and access to every area code is capped at $23,425 (16 CFR 310.8(c)). The steps:

1. Create an account at telemarketing.donotcall.gov, the only way in, and register as a “Seller”, whether you dial yourself or a vendor dials for you.
2. Choose the area codes you will call.
3. Pay through Pay.gov. A credit-card payment gives immediate access; other payments generally “take between three to five full business days to clear.”
4. Get your Subscription Account Number. The annual period starts on the first day of the month you paid (16 CFR 310.8(d)).
5. Give the SAN to each vendor that scrubs or dials for you.
6. Check VIEW SAN SHARING (under Manage / Renew Subscriptions), which shows, for each vendor using your SAN, “the date of the last download that was completed by that TM/SP using their SAN”.
7. Add area codes mid-year as needed. Once your total passes five, each added one costs $85 in the first six months of the annual period and $43 in the second six (16 CFR 310.8(d)).

The annual registry fee in fiscal year 2027, by area codes accessed, computed from 16 CFR 310.8(c) as in force since October 1, 2026:

Where the TSR reaches your calls, a seller may not call “any person whose telephone number is within a given area code”, registered or not, until it has access to that area code, with any fee paid, unless it calls only people who gave written permission or have a business relationship with it and uses the registry for nothing else (16 CFR 310.8(a)). Whether the TSR reaches an insurance campaign depends, the FTC says, on the extent to which state law regulates insurance telemarketing; the FCC’s safe harbor needs registry access you bought yourself either way.

Of the 9,725 organizations that accessed the registry in fiscal year 2025, 7,182 took five or fewer area codes free, 709 accessed as exempt organizations and 1,834 paid, according to the FTC’s Do Not Call Registry Data Book.

Take fee figures from the Federal Register fee rule, which raised the fee “from $82 to $85 per area code” for fiscal year 2027; as of October 22, 2026, the FTC’s own Q&A still showed last year’s $82 and $41 add-on fees. Some state lists cost extra: Oklahoma’s Attorney General charges “$150.00 per quarter or $600.00 per year.”

Does a scrub protect you if a call still goes wrong?

A scrub protects you only as one part of a defense. The FCC’s safe harbor covers a call to a registered number when the caller “can demonstrate that the violation is the result of error” and that, as routine practice, it has:

• written procedures for the national do-not-call rules;
• trained its personnel “and any entity assisting in its compliance”;
• a recorded list of the numbers the seller may not contact;
• a registry copy no more than 31 days old at each call, and records that prove it;
• registry access it bought itself, with no cost-sharing arrangement, and a process that keeps registry data to compliance use only.

The TSR’s safe harbor adds that the seller, or someone acting for it, “monitors and enforces compliance with the procedures”, and that the call was an error “and not of failure to obtain any information necessary to comply with a request” not to be called (16 CFR 310.4(b)(3)). The scrub is one line in each list, and it is not consent.

A dated scrub run on your own SAN is evidence for the due-care defense to a consumer’s do-not-call suit under 47 U.S.C. §227(c)(5), not the defense itself; the same paragraph also sets who can sue, after how many calls and for how much.