Does the TCPA Apply to B2B Text Messages? Yes

One of the most persistent myths in business texting is that the Telephone Consumer Protection Act only protects consumers, so messages sent "business to business" are exempt. Teams repeat it to each other, sales tools imply it, and it costs real money in litigation, because the myth is mostly wrong.

Here is the accurate one-sentence answer: the TCPA (47 U.S.C. 227) protects telephone numbers and their subscribers, not consumer status, so a text sent to a cell phone is regulated the same way whether the person carrying that phone is a homeowner or a procurement director.

This article explains where the B2B confusion comes from, which narrow rules actually distinguish business contexts, and how to run a compliant B2B texting program.

Where the "B2B Exemption" Myth Comes From

The TCPA contains two distinct sets of restrictions, and the myth survives because people blur them together.

1. The autodialer and prerecorded-voice rules (47 U.S.C. 227(b))

Section 227(b) restricts calls made using an automatic telephone dialing system or an artificial or prerecorded voice to cell phones without the called party's prior express consent. Courts and the FCC treat text messages as "calls" under this section. Critically, nothing in Section 227(b) asks whether the recipient is a consumer. It asks what kind of number you dialed and how. If the number is a wireless number, the restriction applies, full stop, even if the number appears on a company website, a business card, or a purchased B2B lead list.

For marketing messages, the FCC requires the higher standard of prior express written consent under its implementing rules at 47 CFR 64.1200. A business title does not substitute for consent.

2. The do-not-call rules (47 CFR 64.1200(c))

This is where a genuine, but narrow, business distinction lives. The National Do-Not-Call Registry protections apply to "residential telephone subscribers," and the FCC has extended a presumption that wireless numbers are treated as residential for DNC purposes. Calls or texts that are solicitations to a number used strictly as a business line may fall outside the DNC framework. That is the kernel of truth behind the B2B exemption talk.

But notice how little that kernel covers. The DNC carve-out does not touch the autodialer and prerecorded-voice rules in Section 227(b). A cold marketing text blasted from a platform to a list of "business" cell numbers can be perfectly consistent with DNC rules and still generate liability under Section 227(b) if consent is missing.

The Rules at a Glance

Two things stand out from that table. First, the only row where B2B status meaningfully helps is the DNC row, and even there the wireless presumption cuts against you. Second, the statutory damages provision, $500 per violation and up to $1,500 for willful or knowing violations, applies to texts received on cell phones regardless of why the recipient carries that phone. The economics of a class action do not care about your ideal customer profile. We break down how those numbers stack up in our guide to TCPA violations and penalties.

Why B2B Numbers Are Riskier Than They Look

Several practical realities make B2B texting more exposed than teams assume:

• Most business contacts are reached on personal cell phones. Remote work and BYOD policies mean the "work number" in your CRM is often a personal wireless line, exactly what Section 227(b) protects.
• Reassigned numbers. The business contact who gave you a number two years ago may have left the company or changed carriers. The FCC maintains a Reassigned Numbers Database precisely because texting the number's new holder without their consent creates liability.
• Lead lists do not carry consent. Purchased or scraped B2B contact lists almost never include TCPA-grade consent that names your organization. Consent must come from the current subscriber or customary user of the number.
• Facebook v. Duguid narrowed the autodialer definition, not the risk. The Supreme Court's 2021 decision held that an automatic telephone dialing system must use a random or sequential number generator. That helps some platforms, but prerecorded and artificial-voice rules still apply, many states passed their own mini-TCPA laws with broader definitions, and plaintiffs continue to file DNC and consent-based claims.
• State laws fill the gaps. Florida, Oklahoma, Washington, Texas, and other states regulate commercial texting with their own consent standards and private rights of action, and most do not carve out B2B messages cleanly either.

What Actually Is Exempt

To be fair to the myth, some categories of B2B communication carry lower risk:

1. Manually dialed, individually typed messages from one person to a specific business contact, without an autodialer or prerecorded content, sit outside Section 227(b)'s core restrictions, though DNC and state rules can still apply to solicitations.
2. Messages to true landline business numbers avoid the cell phone provisions of Section 227(b), although prerecorded telemarketing calls to residential landlines have their own rules.
3. Non-telemarketing, transactional messages sent with prior express consent (for example, order updates to a business customer who provided their number for that purpose) satisfy the consent framework without needing written marketing consent.
4. Certain emergency-purpose communications are exempt by statute.

Notice that every one of these is a narrow, fact-dependent lane, not a blanket B2B pass. Other categories of callers and calls have specific exemptions too, which we catalog in who is exempt from TCPA rules.

How to Run a Compliant B2B Texting Program

The good news: compliant B2B texting is very achievable, and consent-based B2B messaging tends to perform better anyway because it reaches people who asked to hear from you.

• Collect consent at the point of capture. Add clear texting consent language to demo forms, contracts, onboarding flows, and event signups, naming your organization and describing message types.
• Use prior express written consent for anything promotional. If the message advertises or markets, get written consent that meets the standards of 47 CFR 64.1200 and the E-SIGN Act.
• Honor opt-outs immediately. Process STOP replies and any reasonable revocation method, and suppress the number across campaigns.
• Respect quiet hours. Send solicitations only between 8 am and 9 pm in the recipient's local time, and earlier cutoffs where state law requires.
• Scrub against the DNC registry and your internal list for any message that could be characterized as a solicitation, rather than litigating whether a number is "residential."
• Document everything. Timestamped consent records, message logs, and opt-out logs are your defense file.

A platform built for compliance makes these steps default behavior rather than manual discipline. FRANSiS handles consent capture, opt-out processing, and quiet-hour scheduling automatically, and its AI Powered Helper drafts on-brand replies while keeping conversations inside your approved guardrails.

This article is general information, not legal advice. Requirements vary by jurisdiction and change over time, so confirm your own obligations with qualified counsel or the relevant regulator.

Frequently Asked Questions

Is there a B2B exemption in the TCPA?

Not in the way most people mean it. The autodialer and prerecorded-message rules in 47 U.S.C. 227(b) apply to any cell phone number regardless of business context. The narrower do-not-call rules in 47 CFR 64.1200(c) protect residential subscribers, which is the only place a business-line distinction genuinely exists, and the FCC presumptively treats wireless numbers as residential for that purpose.

Can I text a prospect whose cell number is on their company website?

Publication of a number is not consent. If you use an automated platform to send that text, or the message is telemarketing, you need the subscriber's prior express consent (written consent for marketing). A number being publicly available does not change the analysis under Section 227(b).

Do TCPA damages apply when the recipient is a business?

Yes. Statutory damages of $500 per violation, up to $1,500 for willful or knowing violations, are available to the subscriber of a protected number. Employees who receive unsolicited automated texts on personal cell phones used for work have brought claims and class actions on exactly this basis.

Did Facebook v. Duguid make B2B cold texting legal?

No. The 2021 decision narrowed the definition of an automatic telephone dialing system to equipment using a random or sequential number generator. Prerecorded and artificial-voice restrictions, DNC rules, consent requirements for marketing under FCC rules, and state mini-TCPA statutes all remain in force, and litigation over texting platforms continues.

What consent do I need for B2B marketing texts?

Prior express written consent from the current subscriber or customary user of the number: a signed or electronically signed agreement that clearly authorizes your organization to send marketing texts to that specific number, with disclosure that consent is not a condition of purchase. Keep the record.

Text Business Contacts With Confidence

FRANSiS gives sales, outreach, and operations teams a two-way SMS platform with built-in consent tracking, automatic opt-out handling, and quiet-hour scheduling, so B2B texting stays on the right side of 47 U.S.C. 227. Contact us to see how the AI Powered Helper keeps every conversation compliant and human.