Does the Do Not Call Registry Apply to B2B Outreach?

You are about to call or text a list of business owners, and someone in the room says the words “do not call registry.” The question underneath the pause is simple and fair: if these numbers are on the National Do Not Call Registry, am I breaking the rule by contacting them?

The honest answer is more useful than the quick one, and it starts with a fact most explainers skip. The registry is one list governed by two different rulebooks — the Federal Trade Commission’s Telemarketing Sales Rule and the Federal Communications Commission’s rules under the Telephone Consumer Protection Act. Both are written around the consumer, not the business. That framing is the whole thing, and it is also why “the registry never applies to businesses” is the wrong way to say it.

This article is for the person running the outreach, not the person defending a lawsuit. What the registry actually covers, who it is written to protect, the one timing rule that trips up programs that think they are careful, and the difference between the government list and the list you are required to keep yourself. Every rule here links to the regulation it comes from.

One registry, two rulebooks

When people say “the do not call list,” they mean the National Do Not Call Registry the FTC began operating in 2003, which consumers add their own numbers to at donotcall.gov. The registry itself is a database. What makes it a rule is the two separate regulatory schemes that point at it.

The FTC enforces the Telemarketing Sales Rule under the Telemarketing Act. The FCC enforces its own do-not-call rules under the TCPA. A single telemarketing call can fall under both, one, or in some cases neither, and the two rulebooks do not use identical language. That is why two sources can look like they contradict each other when they are simply describing different halves of the same system. For the sender, the practical move is to understand what each one protects, because the exposure for getting it wrong is real: the TCPA’s do-not-call provision at 47 U.S.C. § 227(c) carries a private right of action, which means an individual, not just a regulator, can bring the claim.

Who the rule is written to protect

Start with the FCC side, because its language is the cleanest. The national do-not-call rule lives at 47 C.F.R. § 64.1200(c)(2), and it restricts telephone solicitations to a residential telephone subscriber who has registered. The protected category is the residential subscriber. A line that is genuinely a business line is not what that subsection is written about.

The FTC side points the same direction, and it is more explicit about business calls. The Telemarketing Sales Rule at 16 C.F.R. § 310.6(b)(7) exempts “telephone calls between a telemarketer and any business to induce the purchase of goods or services or a charitable contribution by the business” from the rule. There are two carve-outs written into the exemption itself, and both matter:

• The exemption does not cover the rule’s core misrepresentation prohibitions at § 310.3(a)(2) and (4). You can call a business to sell to it; you still cannot lie to it.
• It does not cover calls to induce the retail sale of nondurable office or cleaning supplies. That is a genuine, long-standing exception — if you are selling toner, paper, or cleaning products into businesses, the B2B exemption does not shield you, and the registry provisions apply to you the way they do to a consumer seller.

Put the two together and the shape is clear. Neither rulebook says a number loses its protection because the person answering runs a company. Both are written around the residential consumer, and the FTC adds an express exemption for genuine business-to-business selling. For most B2B appointment-setting and service offers — selling marketing, bookkeeping, lending, or software to a business — that is the regime you are operating in.

What this does not do is make the question disappear. It relocates it. The rule turns on whether the line is residential or business, and that is decided by how the number is used and held out, not by what you intended when you added it to a list. A cell phone a sole proprietor uses for both the business and the kids’ school pickup is exactly the kind of mixed-use number courts fight over. The full conduct test — the factors a court weighs to decide whether a mixed-use number is residential or business — is its own subject, and we walk through it in the TCPA compliance playbook. The short version for this page: do not assume every number on a “business” list is a business line.

The 31-day rule almost nobody gets exactly right

Here is the timing rule that catches programs that believe they are compliant. It is not enough to have scrubbed your list against the registry at some point. Both regulators require that the scrub be recent, and both put the number at 31 days.

On the FCC side, 47 C.F.R. § 64.1200(c)(2)(i)(D) makes a call to a registered number defensible only if the seller or telemarketer uses a process that employs a version of the registry “obtained…no more than 31 days prior to the date any call is made, and maintains records documenting this process.” The FTC’s Telemarketing Sales Rule carries the same requirement at 16 C.F.R. § 310.4(b)(3)(iv), which requires a process employing a registry version obtained “no more than thirty-one (31) days prior to the date any call is made.”

Two things in that text are doing the work, and both are requirements rather than conclusions:

• Recency. The copy of the registry you scrubbed against has to be no older than 31 days when the call goes out. A list cleaned in January and dialed in April has not met the condition, no matter how clean it looked in January. People age off and onto the registry constantly, so a stale scrub is not a scrub.
• Records. The rule does not just ask you to scrub; it asks you to maintain records documenting the process. The documentation is part of the safe harbor, not an optional extra. If the process exists only in someone’s head, it is very hard to demonstrate after the fact.

This recency-and-records pattern should feel familiar if you have read anything here about provenance. The same instinct that makes you store where every phone number came from is the instinct that makes you store when you last scrubbed and against which version. The argument about whether a given number should have been contacted happens after someone has already complained — the records are what you have to answer it with.

The two lists people keep confusing

The single most common mistake in this area is treating the National Do Not Call Registry as the only list that matters. There are two lists, they come from different rules, and one of them does not care at all whether your calls are B2B.

The national registry is the government database. The internal, entity-specific do-not-call list is the record you are required to keep of the people who told your operation to stop. The FCC sets out those duties at 47 C.F.R. § 64.1200(d) — a written policy available on demand, training for the people who do the outreach, recording a do-not-call request when it is made, and honoring it. Those duties attach to a telemarketing program on their own terms.

The practical consequence is the one that saves you grief: build the internal list first and treat it as absolute. Someone who replies “stop,” “take me off your list,” or “not interested, don’t contact me again” goes onto a suppression list and is never messaged again, by any client, from any number, forever. That is required regardless of how you read the B2B question above, and it also happens to remove the people most likely to turn into a complaint. If you run outreach for multiple clients from shared infrastructure, suppress globally rather than per-client — the cheap answer is almost always the safe one.

What the B2B framing does not settle

It would be easy to read everything above as “the registry is a consumer thing, so I can ignore it.” That is the over-read the compliance rules here are written to prevent, and it is wrong for several concrete reasons.

Mixed-use and wireless numbers run against you to start. The FCC presumes, in its 2003 Order, that a wireless subscriber who registers on the do-not-call list is a residential subscriber. That presumption is the starting point, and it runs against the sender — so a cell number on the registry is treated as residential until shown otherwise.

Inadvertently registered business numbers are not automatically violations — but they are still litigated. The FCC said in a 2005 Order that the registry “applies to residential subscribers,” does not preclude calls to businesses, and that business numbers inadvertently registered are not violations. That paragraph is real and it helps. It does not mean the question never gets asked; it means you have an answer when it does, provided you can show the line was in fact a business line.

The do-not-call rule is only one of the rules. Scrubbing the registry does nothing about the autodialer question under § 227(b), which is a completely separate regime about how you dial rather than whom you reach — that is covered in what the TCPA says about autodialers. It does nothing about the carrier layer, where A2P 10DLC registration decides whether your texts even get delivered. And for the full arc of how these rules developed and have been tested, is B2B cold texting legal lays out the history.

States write their own rules. Several states run independent telephone-solicitation statutes, some with their own registries, their own hours, and their own private rights of action. Florida, Oklahoma, Maryland, and Washington are the ones most often cited, and a program that is comfortable federally can still touch a stricter state line. The federal picture is the floor, not the ceiling.

What a defensible approach tends to look like

This is not a compliance program and it is not advice for yours — it is a description of the choices that show up in B2B outreach operations built to hold up. Your counsel decides what applies to you.

1. Every number traces to a public business listing, with the source and date stored, so the “is this a business line” question has a documented answer.
2. Lists are scrubbed against a copy of the National Do Not Call Registry no older than 31 days before any call, and the scrub is logged.
3. An internal suppression list exists from day one, is treated as permanent, and is honored across every client and every number.
4. Stop requests are classified by intent, not by keyword — “take me off your list” counts the same as “STOP.”
5. There is a written do-not-call policy and a record that the people doing outreach were trained on it.
6. State rules are checked for the states you actually send into, not assumed away.
7. A qualified attorney has reviewed the program before launch.

None of this is exotic, and most of it is cheap. The expensive version is the one where a program scrubbed once, assumed “it’s all B2B anyway,” kept no records, and had no internal list — and then had to reconstruct all of that after a complaint rather than before one. The point of doing it in advance is that provenance and process are worth far more as something you already have than as something you are trying to assemble under pressure. Scrubbing is one line on a longer operating list; the full B2B SMS compliance checklist puts it in sequence with the other controls.

This is also, bluntly, why a lot of operators would rather have the outreach run on infrastructure that already does it. A done-for-you program that validates every number as a working line, stores where each one came from, scrubs on a schedule, and keeps a single global suppression list is carrying the record-keeping load the rules actually reward. TaskBlink is built that way on purpose. Whether you run it yourself or hand it off, the requirements are the same — and so is the one that outranks the others: have your own attorney look at your specific situation.

Frequently asked questions