DNC Scrubbing for B2B Cold Calling: What Actually Applies

Four thousand plumbers, dentists and HVAC contractors sit in your spreadsheet, a dialer is pointed at them, and nobody on the team wants to be the one to ask: does the do-not-call list apply to any of this? Search it and you get guides for people selling solar panels to households. Here is the version for someone calling businesses — what a DNC scrub actually is (three lists, not one), how the 31-day rule works, and the three places the business-to-business exemption quietly stops protecting you.

First, the obvious: none of this is legal advice. We build lead-generation software, not a compliance product, and no tool — ours included — makes a calling campaign lawful. Read this as industry background to take to a lawyer who knows your states, your dialing technology and your script.

What a DNC scrub actually is

A DNC scrub compares your calling list against do-not-call registries and suppresses every match before a rep or a dialer touches it. The name implies one action against one list. In practice you check at least three, with different owners, different access rules and very different failure modes.

1. The National Do Not Call Registry

The FTC has run the federal registry since 2003, enforced jointly with the FCC and state attorneys general. Registrations are permanent (the FTC removed the five-year expiry in 2008), and its biennial reports to Congress have put the registry above 250 million numbers in recent years.

Telemarketers reach it through telemarketing.donotcall.gov: open an account, get a Subscription Account Number (SAN), download the registry as per-area-code files refreshed daily. The first five area codes are free; after that the FTC charges an annual per-area-code fee with a cap for nationwide access — roughly $80 per area code and a nationwide cap in the low $20,000s in recent fiscal years. That schedule is revised each October, so pull the current one rather than trusting a blog post.

2. State DNC lists — a dozen states still run their own

Most states retired their registries and defer to the federal one. Roughly a dozen did not. As of 2026 that group includes Colorado, Florida, Indiana, Louisiana, Missouri, Oklahoma, Pennsylvania, Tennessee, Texas and Wyoming, several of which require separate registration and a separate download or license.

Two consequences: a federal-only scrub is not a national scrub, and several of those states wrote telemarketing statutes broader than the federal rules — which matters enormously if you call businesses.

3. Your own internal do-not-call list

The list nobody licenses or sells, and nearly everybody underbuilds. Any business or person who tells you to stop calling goes onto a list you maintain yourself. The FCC's rules require a written policy, staff training, a record of each request, and honoring it for five years; the FTC's Telemarketing Sales Rule attaches no expiry at all, which makes "forever" the only operationally sane answer. Under the FCC's 2024 revocation order, in force since April 2025, a request to stop has to be processed within ten business days.

Internal-list failures are the easiest claims to bring, because they require no argument about registries or exemptions. You called, they asked you to stop, you called again. That is a clean record with a date on it.

Does the do-not-call list apply to B2B calls at all?

Consumer-framed guides leave you stranded here, and it is the only question that matters if your list is local businesses. B2B cold calling laws are not one law with one answer — they are a federal rule with an exemption, a separate federal statute without one, and fifty state legislatures doing as they please. The honest short version: the national registry requirement mostly does not reach B2B calls, and the parts that do reach them carry the largest damages.

The B2B exemption in the Telemarketing Sales Rule

The FTC's Telemarketing Sales Rule (16 CFR Part 310) is what makes registry scrubbing mandatory in the first place. At § 310.6(b)(7) it exempts calls between a telemarketer and a business. If the TSR does not apply to your calls, its registry obligation does not either. That is the legal basis for the widely repeated line that B2B calling is exempt from the do-not-call list.

The exemption carries one carve-out, and it is oddly specific: calls to induce the retail sale of nondurable office or cleaning supplies stay covered. Paper, toner, janitorial consumables. If that is your product, the TSR treats you like a consumer telemarketer. Agencies, MSPs, SaaS vendors and home-services suppliers calling businesses sit outside it.

Where the exemption stops, part one: wireless numbers

The TCPA's prohibition on autodialed and prerecorded or artificial-voice calls to wireless numbers, at 47 U.S.C. § 227(b), is not scoped to residential subscribers and contains no business-to-business exemption. It does not care that the person answering owns a dental practice. If your dialer autodials, or you drop ringless or prerecorded voicemail, the fact that the callee is a business does not help you.

Separately, the FCC treats wireless numbers as presumptively residential for do-not-call purposes, and cell numbers routinely sit on the national list. A mobile number on a Google business listing therefore lands in the least comfortable position available: business enough to argue exemption, residential enough for someone to argue the other way.

So the first real step is not scrubbing — it is knowing which of your numbers are wireless. Our companion guide on verifying phone numbers before cold calling covers line type, carrier lookup, and why number portability killed the old area-code shortcut for good.

Where the exemption stops, part two: states that do not follow

A federal exemption is not a fifty-state exemption. Several states either omitted a clean business-to-business carve-out or defined "telephone solicitation" broadly enough that a call to a business line can land inside it. Florida's amended telephone solicitation act (2021, narrowed by legislation in 2023) and Oklahoma's Telephone Solicitation Act of 2022 are the two most heavily litigated state mini-TCPAs; Maryland and Washington also maintain restrictions that do not track the FTC's B2B carve-out.

Treat that paragraph — including having read it here — with suspicion. Mini-TCPA scope is contested in active litigation and amended most legislative sessions, and whether a given statute reaches your call turns on your script, your dialing technology and the state you are calling into. That is a question for counsel in the states you dial, not for a blog post.

Where the exemption stops, part three: the sole proprietor

A local-business list is full of one-person operations where the listed business number is the owner's personal cell, on a consumer plan, registered on the national list years ago. Legally that is the blurriest record you own. Operationally it is simple: treat listed mobiles at very small businesses as your highest-scrutiny segment. Manual dial, nothing prerecorded, and scrub them even if you have concluded your calls are exempt.

The wider penalty landscape for outbound — TCPA statutory damages, FTC civil penalties, the GDPR layer if any prospects sit in Europe — is mapped out in our guide to lead scraping for local businesses, so it is not re-litigated here.

How to scrub leads against do-not-call lists

Step 1 — Normalize and classify first

Every match is ultimately a string match. Standardize to E.164 before anything else, then attach line type so wireless separates from landline. A number that appears in four formats produces four scrub answers, and you will act on the wrong one.

Step 2 — Write your scope down once

Record, in writing, which lists you check and why: federal only, federal plus the state lists for states you dial, internal always. If you are leaning on the business-to-business exemption, this document is where that decision and its reasoning live. An informal understanding is worth little two years later; a dated memo is worth a lot.

Step 3 — Get registry access, or buy the check

Two routes to a do-not-call list check. Register with the FTC directly, pull the area-code files and match them yourself — cheapest, and reasonable if you dial a handful of area codes. Or use a scrubbing provider that already holds the licenses, aggregates federal, state and litigator lists, and hands back a scrubbed file or an API verdict.

Step 4 — Check the internal list first, and separately

Your internal list runs before the registries and independently of them. It applies to every call, including calls you have concluded are exempt, and it is the only list that grows out of your own activity. Log the date, the number, the business, and who took the request. If your leads land in Google Sheets, the low-tech version is a second tab in the same workbook that gets checked before every wave — which beats a perfect process nobody follows.

Step 5 — Key suppression to something more stable than a phone number

Suppression keyed to a phone number breaks the moment a business ports its line or swaps a landline for VoIP: the same business walks back onto your dial list under a new number. Key it to a stable business identifier instead, and treat the phone as an attribute of the record rather than its identity.

Step 6 — Log everything, because the logs are the safe harbor

The TSR's safe harbor at § 310.4(b)(3) does not forgive a pattern of calls; it forgives an isolated, unintentional error, and only if you can show the whole set: written procedures, trained personnel, a maintained internal list, a process for preventing registry calls that uses a registry version no more than 31 days old, and active monitoring and enforcement. Every element there is a record. Records you cannot produce did not happen.

The 31-day rule: why "we scrubbed the DNC list" is not an answer

The number to remember is 31. Both the FTC and the FCC condition their safe harbors on using a version of the registry obtained no more than 31 days before the call is placed. The FTC originally allowed three months and tightened it to 31 days effective January 2005.

Read it as a ceiling on staleness, not a schedule. Nothing in the rule suggests a 30-day-old scrub is a good idea; it just means a 32-day-old one costs you the safe harbor. Cadences that hold up in practice:

• Continuous outbound: pull the daily delta files and scrub nightly. Most providers automate this. If yours does not, weekly is the realistic floor.
• Campaign waves: scrub at list load, then again within 24 hours of the wave going out. A list loaded in March and dialed in May was scrubbed sixty days ago, noticed or not.
• Purchased or inherited lists: scrub before the first dial, without exception, and treat any vendor's "DNC-scrubbed" stamp as undated until they show you the date.
• Recurring lead pulls: scrub the delta, not just the original file. Records that arrived last Tuesday arrived unscrubbed.

Registry membership is also not the only thing that shifts inside a 31-day window. Numbers get disconnected, ported and handed to somebody new — a different failure, same remedy: re-check rather than trust a snapshot.

Tools that actually do DNC scrubbing

Named options, by who they suit:

• PossibleNOW (DNCSolution) — the enterprise standard for multi-jurisdiction compliance: federal, state and internal lists, wireless identification and consent management in one system.
• Gryphon.ai — scrubs in real time at the moment of dial rather than in a batch pass over a file, closing the window between "the list was clean" and "the call went out." Framed around consumer telemarketing, but the architecture argument is sound.
• DNC.com (DNCScrub) — self-serve batch and API scrubbing priced per record; a sensible entry point for a small team.
• Your dialer — Convoso, Five9 and RingCentral RingCX among others ship scrubbing built in — cheapest path if you already pay for the dialer. Check which lists it covers and whether it timestamps each scrub, because the timestamp is the audit trail.
• Free scrubbers — ask what data they match against. A tool that never asks for your registry access, or for a file you downloaded yourself, is not checking the federal registry.

What LeadMarina does, and what it does not

Disclosure, since we are the ones publishing this: LeadMarina is our product, and it is not a DNC scrubbing tool. We hold no registry licenses, we do not scrub, and nothing we sell makes your calling lawful. For scrubbing you need one of the options above or your own registry access.

What we do sits one step earlier. LeadMarina finds local-business leads by niche and city from Google business listings data — up to 30 cities in one bulk search — and delivers every lead fully verified: up to three emails SMTP-checked as safe, risky or invalid, up to three phones tagged with line type (mobile, landline, VoIP, toll-free) and carrier, plus owner name where identifiable, socials, ratings, reviews and the full business profile.

The overlap with this post is narrow but real. Scrubbing decisions run on line type, because wireless versus landline decides how much scrutiny a record gets. Exports to Close, GoHighLevel, Google Sheets or an emailed file match on a stable Google business identifier, so a refresh updates the existing row instead of minting a second copy your suppression logic has never seen. And a search can be scheduled once, daily, weekly, monthly or yearly, so a weekly refresh sits alongside a weekly scrub instead of fighting it. The quick-start docs walk through a first search, and the free plan's 100 leads are enough to test line type against your own dialer.

A B2B DNC scrubbing checklist

• Normalize to E.164 and attach line type before you scrub anything.
• Decide and document your scope: federal, the state lists for states you dial, internal always.
• Build the internal list on day one and honor requests indefinitely, exemption or no exemption.
• Never let more than 31 days pass between the registry version you used and the call — and treat that as the outer limit, not the plan.
• Segment wireless numbers out and give them the strictest handling, especially at one-person businesses.
• Do not autodial or drop prerecorded messages to mobiles on the theory that B2B is exempt; that exemption does not exist in the TCPA's wireless provisions.
• Check state law separately for every state you dial into, with counsel, and re-check each legislative session.
• Keep the paperwork: written procedures, training records, scrub timestamps, request logs. The safe harbor is made of documents.

Scrubbing is not the hard part. Deciding what actually applies to a list of plumbers and dentists is — and the answer is rarely "nothing." The exemption quoted in every B2B sales forum is real, narrower than people think, and gone the moment your dialer automates a call to a cell phone. Get line type onto every record, build the internal list before you need it, date every scrub, and take the state question to a lawyer. No tool, ours very much included, does that last part for you.