ColdCalls.ai
All posts
Compliance

TCPA B2B Exemption: What It Does Not Cover

The TCPA do-not-call rules cover residential subscribers, so B2B landlines sit outside them. But 64.1200(a)(1)(iii) follows the number, not the business.

By the ColdCalls.ai team

August 2026 · 9 min read

Partly. There is no single "B2B exemption" that lifts the TCPA off business calls. The do-not-call machinery in the TCPA rules is written for residential subscribers, so a business landline is not protected by the national registry, the 8 a.m. to 9 p.m. window or the internal do-not-call duty. But the prohibition that carries the private lawsuits, 47 CFR 64.1200(a)(1)(iii), is keyed to the number being wireless, not to whether the person answering is at work. Call a prospect's mobile with an artificial or prerecorded voice and you need prior express consent, business card or not. The FTC's Telemarketing Sales Rule does have a real written B2B exemption, at 16 CFR 310.6(b)(7), with two carve-outs most people have never read.

This is one of the most confidently mis-stated rules in outbound sales. Half the advice says B2B calls are exempt from the TCPA, full stop. The other half says nothing is exempt and you need consent for everything. Both are wrong, and the gap between them is where the expensive mistakes live.

The accurate version requires separating two things that get mashed together: the FCC's TCPA rules in 47 CFR 64.1200, and the FTC's Telemarketing Sales Rule in 16 CFR 310. They are different regulators, different rules, and they treat business calls differently. Below is what each one actually says, quoted from the current text.

Does the TCPA apply to B2B calls?

Yes, but only parts of it, and the parts that apply are not the ones most teams worry about.

Read the operative paragraphs and you notice a word that keeps appearing. 47 CFR 64.1200(c) says no person or entity shall initiate any telephone solicitation to "(1) Any residential telephone subscriber before the hour of 8 a.m. or after 9 p.m. (local time at the called party's location), or (2) A residential telephone subscriber who has registered his or her telephone number on the national do-not-call registry".

The internal do-not-call obligation in paragraph (d) is drawn the same way. It bars initiating "any call for telemarketing purposes to a residential telephone subscriber unless such person or entity has instituted procedures for maintaining a list of persons who request not to receive such calls".

So the registry, the calling window and the company-specific suppression duty are all attached to residential subscribers. A call to a switchboard at a manufacturing company is not covered by any of the three. That is the grain of truth inside "B2B calls are exempt from the TCPA".

The problem is that this is not the paragraph that generates litigation.

Is there a TCPA B2B exemption?

Not as a named exemption, no. The FCC rules do not contain a sentence saying business-to-business calls are excluded. What exists is a set of rules whose scope happens to be residential, sitting next to a set of rules whose scope is not.

Here is how a single outbound call to a business contact actually breaks down.

RuleDoes it cover a B2B call?Why
National Do Not Call registry, 47 CFR 64.1200(c)(2)No, for a business lineWritten for "a residential telephone subscriber who has registered his or her telephone number"
8 a.m. to 9 p.m. calling window, 47 CFR 64.1200(c)(1)No, for a business lineApplies to "any residential telephone subscriber"
Internal do-not-call list, 47 CFR 64.1200(d)No, for a business lineApplies to telemarketing calls "to a residential telephone subscriber"
Autodialer or artificial and prerecorded voice to a mobile, 47 CFR 64.1200(a)(1)(iii)YesKeyed to "any telephone number assigned to a paging service, cellular telephone service, specialized mobile radio service, or other radio common carrier service". Nothing about residential
Revocation of consent, 47 CFR 64.1200(a)(10)Yes, wherever consent was the basis for the callA called party may revoke by any reasonable method and you may not designate an exclusive means
Wireless numbers generally, 47 CFR 64.1200(e)YesParagraphs (c) and (d) are made "applicable to any person or entity making telephone solicitations or telemarketing calls or text messages to wireless telephone numbers"
FTC Telemarketing Sales Rule, 16 CFR part 310Largely no, by written exemption16 CFR 310.6(b)(7) exempts calls "between a telemarketer and any business", with two carve-outs
State mini-TCPA statutesVaries, and several do not stop at residentialFlorida, Oklahoma, Washington and others impose their own consent and calling rules

Are business numbers on the national Do Not Call registry?

Business landlines are not protected by it. The registry is a registry of residential subscribers, and the FTC has consistently declined to police business-line registrations.

The complication is mobile numbers. A sole proprietor, a contractor, a real estate agent and a large share of ordinary employees use a cell number as their working number, and many of those numbers are registered on the national registry as personal ones. 47 CFR 64.1200(e) makes paragraphs (c) and (d) applicable to telemarketing calls to wireless numbers, and in practice the FCC treats a wireless number on the registry as presumptively residential. If your list came from a data vendor and you cannot tell a desk line from a personal mobile, you cannot lean on the residential distinction with any confidence.

That is the practical reason serious outbound teams scrub against the registry even for B2B campaigns. Not because the rule compels it for a switchboard, but because they cannot prove which rows are switchboards. The mechanics of doing that scrub properly are covered in our guide to do not call list rules for businesses.

The part that actually generates lawsuits

47 CFR 64.1200(a)(1) prohibits initiating any telephone call, other than for emergency purposes or with the prior express consent of the called party, "using an automatic telephone dialing system or an artificial or prerecorded voice" to the categories listed underneath. Subparagraph (iii) is the one that matters: "To any telephone number assigned to a paging service, cellular telephone service, specialized mobile radio service, or other radio common carrier service, or any service for which the called party is charged for the call."

Read what is absent. There is no reference to residential subscribers, no reference to consumers, and no reference to the purpose of the call. The trigger is the technology used and the type of number dialed. A prerecorded voice reaching a purchasing manager's mobile is inside this prohibition on exactly the same terms as one reaching a retiree's mobile.

Two things narrow it. The Supreme Court in Facebook v. Duguid (2021) held that an automatic telephone dialing system means equipment using a random or sequential number generator, which is why dialing from a stored list is generally not an ATDS. And prior express consent is a complete answer where you have it and can produce the record. But neither narrowing touches the artificial or prerecorded voice half of the sentence, which stands on its own and does not care how the number was selected.

The exposure is per call. Under 47 U.S.C. 227(b)(3) a private plaintiff can recover $500 per violation, rising to as much as $1,500 where the violation was willful or knowing. A modest campaign that dialed ten thousand mobile numbers with a prerecorded opener is a statutory-damages problem, not a compliance memo.

Does the Telemarketing Sales Rule exempt B2B calls?

Yes, and unlike the TCPA this one is a genuine written exemption. It is worth reading in full because the exceptions are narrow and strange.

16 CFR 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, provided, however that this exemption does not apply to: (i) The requirements of 310.3(a)(2) and (4); or (ii) Calls to induce the retail sale of nondurable office or cleaning supplies".

Two things survive the exemption. First, the misrepresentation prohibitions in 310.3(a)(2) and (4) still bind you: you cannot misrepresent material aspects of what you are selling, and you cannot make false or misleading statements to induce payment. The FTC did not hand anybody a licence to lie to businesses.

Second, and this is the clause nobody expects, calls selling nondurable office or cleaning supplies at retail are carved back in and remain fully subject to the rule. That is a legacy of a specific fraud pattern from the 1990s, where boiler rooms shipped overpriced toner and janitorial supplies to small offices. If that is your product, you are inside the TSR with everything it carries: the abandoned-call cap, the calling window, the record retention. The rule adds that 310.4(b)(1)(iii)(B) and 310.5 do not apply to sellers of nondurable office or cleaning supplies, which is a partial relief on the internal do-not-call and recordkeeping side, not a general one.

For every other B2B seller, the practical effect is that the FTC's three percent abandoned-call safe harbor, the 8 a.m. to 9 p.m. rule in 310.4(c) and the five-year record set in 310.5 fall away on genuine business-to-business calls. That is a real difference from consumer outbound, and it is the strongest argument for B2B being a lighter compliance environment.

What about AI voices on B2B calls?

This is where the two halves collide, and it is the question we get asked most.

In February 2024 the FCC confirmed that AI-generated voices used in calls are "artificial" voices for TCPA purposes. That ruling did not create a new rule; it clarified which side of an existing line the technology sits on. And the existing line is 64.1200(a)(1)(iii), the paragraph that follows the number rather than the business.

So an AI voice agent calling business landlines from a stored list is not doing anything the TCPA prohibits. The same agent calling mobile numbers on that list is placing artificial-voice calls to wireless numbers and needs prior express consent for each one. The B2B character of the conversation does not change the analysis, because the paragraph never mentioned it.

There is also the revocation rule, in force since April 11, 2025. Under 64.1200(a)(10), a called party may revoke consent "by any reasonable method", callers may not designate an exclusive means of revoking, and a request must be honored "within a reasonable time not to exceed ten business days from receipt". The rule lists per se reasonable methods, including an automated key-press or voice opt-out on the call itself and a reply text using words like "stop", "quit", "revoke", "opt out" or "unsubscribe". If you are running voice at volume, honoring an opt-out spoken mid-call is not a courtesy feature, it is the compliance path. Teams that map each of these obligations to a specific control they can evidence, rather than to a paragraph in a policy document, find audits and customer security reviews far less painful, which is the whole premise behind systems that track obligations and map them to controls.

The broader legal picture for AI outbound, including disclosure practice and the state layer, is set out in is AI cold calling legal, and how we build the controls into the product on TCPA compliant AI calling.

What still applies to every B2B call you make

Strip out everything the residential wording excludes and a short list remains. This is the floor, and it does not depend on who answers.

  • Caller ID. 47 CFR 64.1601(e) requires telemarketers to transmit caller identification information and prohibits blocking it. Where you substitute a number, it must permit a do-not-call request during business hours.
  • No artificial or prerecorded voice to mobiles without consent. 64.1200(a)(1)(iii), regardless of the B2B context.
  • Honor revocation. 64.1200(a)(10), by any reasonable method, within ten business days.
  • No misrepresentation. 16 CFR 310.3(a)(2) and (4) survive the B2B exemption explicitly.
  • State law. Several mini-TCPA statutes are not limited to residential lines, and they carry their own consent standards and private rights of action.
  • Your own suppression list. Not required by 64.1200(d) for business lines, but the cheapest insurance you will ever buy, since it is also the evidence that a repeat call was an error rather than a practice.

One more piece of context worth keeping in view: the Eleventh Circuit vacated the FCC's one-to-one consent rule in Insurance Marketing Coalition Ltd. v. FCC in January 2025. That decision removed a specific consent-formatting requirement. It did not remove the underlying need for prior express written consent where the rules call for it, nor the need to be able to produce the record.

How to run B2B outbound without guessing

The workable approach is not to classify your program as exempt or not exempt. It is to segment the list by number type, because that is the variable the binding rule turns on.

Split business landlines from mobiles at the data layer. Landlines can be worked with a dialer and a live or synthetic voice without the wireless prohibition applying. Mobiles need either a human voice, or prior express consent with a producible record, before an artificial voice is used. Scrub everything against the national registry anyway, because you cannot prove which mobile numbers are personal. Keep a suppression list and honor an opt-out on the call. Transmit real caller ID on a number somebody can call back.

Do that and the B2B question stops mattering very much, which is the point. The teams that get into trouble are not the ones that read the rule too strictly. They are the ones that heard "B2B is exempt", pointed a prerecorded voice at a list of cell numbers, and found out which paragraph was actually load-bearing. If you are building the program from scratch, the sequencing advice in AI cold calling for B2B covers the operational side, and are power dialers illegal answers the dialing-mode question that usually comes next.

This article summarizes federal rules as published in the eCFR and read on August 16, 2026. It is general information about how the rules are written, not legal advice, and it does not cover the state statutes that may apply to your program. Confirm your own position with counsel before launching a campaign.

See ColdCalls.ai book meetings

The AI SDR calls every lead, discloses it is an AI, qualifies, handles objections and books meetings into your calendar and CRM. Flat fee, no per-meeting cut, compliance built in.

Put your outbound on autopilot

ColdCalls.ai calls every lead, discloses it is an AI, qualifies, handles objections and books meetings into your calendar and CRM. Flat fee, no per-meeting cut, compliance built in.

AI disclosed & DNC scrubbed · Call, qualify, book · No per-meeting cut

AI disclosed on every call · real-time DNC scrubbing · TCPA and consent-aware.