Is business-to-business telemarketing covered by the DNC registry?

Last updated 2026-07-09

What does federal law actually say about B2B calls and the DNC registry?

Federal law does not require you to scrub business phone numbers against the national Do Not Call registry before you cold call those businesses. That exemption lives in the FTC's Telemarketing Sales Rule (TSR), at 16 CFR Part 310, which defines "telemarketing" in a way that deliberately leaves out calls between businesses. The TSR frames a telemarketing call as one made to induce a purchase of goods or services or a charitable contribution by a consumer, and the FTC reads "consumer" to mean a natural person acting outside a business context. ^[1]

The FCC's rules under the Telephone Consumer Protection Act (TCPA), 47 U.S.C. § 227, work the same way. The TCPA's do-not-call protections target residential telephone subscribers. The statute says it is unlawful "to initiate any telephone solicitation to... a residential telephone subscriber who has registered his or her telephone number on the national do-not-call registry." ^[2] The word "residential" carries the whole thing. A number registered to a business entity is not a residential subscriber number, so calling it doesn't breach the TCPA's DNC provisions on its face.

So a rep cold-calling the main switchboard of an LLC, a C-suite direct dial registered under the company name, or a plain business landline is working in a space the federal DNC registry was never built to police. The registry protects private households from unwanted sales calls. It was not designed to shield procurement managers from vendors.

The exemption is narrower than most sales managers think. Read the rest of this before you build a B2B dialing strategy on one sentence in a statute.

What is the legal basis for the B2B exemption and where does it come from?

The TSR's B2B exemption has been in the rule since the FTC rewrote it in 2003, the same year the national Do Not Call registry launched. In its Statement of Basis and Purpose for that rulemaking, the FTC explained that the rule does not reach business-to-business calls because such calls are not telemarketing within the rule's definition. ^[1] The reasoning: businesses have commercial relationships and negotiating power that make the paternalistic protection of a DNC list unnecessary.

The FCC took the same view in its TCPA orders. Its 2003 order establishing the national registry framed the rule around telephone solicitations to residential subscribers, leaving calls to businesses outside that scope. ^[3] The FCC has not reversed that position since, even as it tightened many other TCPA rules on autodialers.

No single statute says "B2B calls are exempt." The exemption is structural. The definitions of "consumer," "residential telephone subscriber," and "telephone solicitation" collectively leave business-to-business contact out. Lawyers call this a definitional exclusion, not an affirmative safe harbor. That difference matters in litigation. You're not waving a permission slip. You're arguing the law never applied at all.

The structure also tells you exactly where the exemption breaks. Change who you're calling, what number they use, or what you're selling, and you can walk right back inside the law's coverage.

Are there situations where B2B calls DO have to comply with DNC rules?

Yes, and this is where outbound teams get burned. The B2B exemption has four pressure points, and every one of them shows up on real call lists.

Cell phones registered to a business. A mobile number registered in an individual's name, even if they use it only for work, is almost certainly a residential subscriber number for TCPA purposes. Courts have held that whether a number is residential turns on how it was subscribed, not how it gets used day to day. If your rep autodials a VP's personal iPhone that is registered to that VP, the TCPA's autodialer rules and DNC rules apply, no matter that you're pitching a B2B product. ^[4] Check the mobile phone do not call list rules before you blast mobile numbers.

Products with dual consumer and business use. The FTC has warned that if the product could reasonably be bought for personal use, the TSR's consumer protections may apply even when you dial a business number. Office supply subscriptions. Software with personal tiers. Financial products. Insurance policies. Any of these can drag a call back into consumer territory depending on the facts.

Sole proprietors and home-based businesses. A plumber who works from home. A freelance designer. A trainer with a home studio. Their business line and their home line are often one number. The FTC has acknowledged this gray area: if a number belongs to a one-person business run from a residence, treat it like a residential number for DNC purposes. ^[1]

State DNC and telemarketing laws. Several states have telemarketing statutes broader than federal law that reach B2B calls at least partly. That gets its own section below.

The exemption is real, but it has edges. Building a program on a surface reading of it, without auditing your list for cell phones, sole proprietors, and state-specific numbers, is how companies end up writing settlement checks.

Does the TCPA's autodialer ban apply to B2B calls?

This is a separate question from the DNC registry, and the answer is messier. The TCPA has two distinct sets of obligations. One covers telephone solicitations to DNC-registered numbers, the part we've been discussing. The other, at 47 U.S.C. § 227(b), restricts automatic telephone dialing systems (ATDS) and prerecorded voice messages. ^[2]

Section 227(b) applies to calls to any number assigned to a cellular telephone service without the prior express consent of the called party. It carries no residential subscriber limit. So even a clean B2B call to a business cell phone can violate Section 227(b) if you used an autodialer and had no consent, DNC exemption or not.

The Supreme Court narrowed the ATDS definition in Facebook v. Duguid (2021) to systems that use a random or sequential number generator, which cut some exposure for companies running predictive dialers off static lists. ^[5] The ruling did not erase the risk. Class action plaintiffs still argue that various dialing setups qualify under the narrower definition.

Here's the spread. A B2B call to a business landline, placed by a human working a static list, is the lowest-risk scenario there is. A B2B call to a business cell phone placed by an autodialer without written consent is high-risk even with the B2B exemption in hand. Know your equipment. Know your numbers.

Which states have DNC or telemarketing rules that cover B2B calls?

State law is where the B2B exemption turns into patchwork. Most states mirror the federal framework and exempt B2B calls from their state DNC lists. A handful go further, and those are the ones that catch people.

Florida's Telephone Solicitation Act (Florida Statutes § 501.059), amended heavily by SB 1120 effective July 1, 2021, and updated again in 2023, covers calls to Florida area code numbers for the purpose of selling goods or services. Its definition of "called party" reaches businesses in some contexts, and its limits on automated calls run broader than the federal TSR. If you dial Florida numbers, review the florida do not call list rules on their own. ^[6]

Indiana's Telephone Privacy Act (Indiana Code § 24-4.7) also pushes past the federal baseline. ^[7] The indiana do not call list is kept separate from the federal registry, and Indiana has a long record of aggressive enforcement against telemarketers who assume federal law is the ceiling.

Pennsylvania runs its own do-not-call list through the Pennsylvania Public Utility Commission, and the Pennsylvania Telemarketer Registration Act imposes registration duties that apply broadly. See the do not call list pa details before you call PA numbers at scale. ^[8]

Other states to check: Texas (Business & Commerce Code § 302.101), Colorado (Colorado Consumer Protection Act), and Oklahoma each have telemarketing statutes worth an individual read before you launch a large campaign into them.

Honest caveat: no single article can hand you a current, accurate 50-state breakdown, because these laws move. Before any large B2B campaign, check the specific statutes for every state you're dialing into heavily. Don't lean on the federal exemption alone.

State	Has separate state DNC list?	B2B calls covered?	Notes
Florida	Yes	Partially	Automated calls to FL area codes broadly restricted (SB 1120, 2021)
Indiana	Yes	Partially	Broad telemarketer registration requirements
Pennsylvania	Yes	Partially	Separate PUC-administered list; registration required
Texas	No (uses federal)	Generally no	Registration requirements apply to telemarketers broadly
California	No (uses federal)	Generally no	CPPA privacy rules add data obligations
Most other states	No (uses federal)	Generally no	Federal B2B exemption applies

What about internal company do not call lists for B2B contacts?

The national registry is one layer of the do-not-call framework, not the whole thing. The TSR and the FCC's TCPA rules also require telemarketers to keep their own company-specific do-not-call lists and honor opt-out requests. ^[1][3] That duty applies to B2B calls too.

If a business contact tells your rep "don't call us again," you have to record it and stop calling that number within 30 days under the TSR. The same rule runs under the TCPA framework for residential numbers, and good teams apply it to everyone regardless of business or consumer status. Ignoring a clear do-not-call request from a business is a legal risk and a sales management failure at the same time.

For B2B teams, an internal suppression list is non-negotiable. It should capture opt-outs at the number level and the company domain level, so a second rep doesn't dial a different number at the same company after a flat rejection. Tools that handle this automatically pay for themselves at any real dialing volume.

The do not call list report process at the FTC is mostly for consumers reporting violations, but businesses and their employees can file complaints too. Enough complaints about a B2B telemarketer can still trigger an FTC look, even if the underlying calls were technically exempt from the registry.

What are the actual penalties if a B2B call does violate DNC or TCPA rules?

If a B2B call falls outside the exemption, the penalty structure matches any other TCPA or TSR violation. The TCPA gives a private right of action for $500 per violation, trebled to $1,500 for willful violations. ^[2] The FTC can assess civil penalties up to $53,088 per violation under the TSR, a ceiling that adjusts for inflation each year. ^[9]

The per-call math is what makes TCPA litigation dangerous. A company that autodials 50,000 numbers without checking whether any are residential cell phones on the DNC registry faces theoretical exposure of $25 million at the base rate, and $75 million if trebled. That is not a thought experiment. TCPA class actions routinely settle in eight figures. ACA International v. FCC and the cases after it reshaped how ATDS liability works, but plaintiffs keep filing aggressively. ^[10]

State penalties vary. Florida's 2021 law allows $500 per call for negligent violations and up to $1,500 for willful ones, nearly identical to TCPA private-action damages. Indiana's state enforcement runs up to $10,000 per violation.

The practical risk for most small B2B teams is not a class action. It's a state AG investigation set off by a cluster of complaints, or a single plaintiff's attorney who spots a cell phone number on your list that should have been scrubbed. Those cases settle in the $5,000 to $50,000 range for small operators. That still hurts. Getting the basics right costs far less.

How should a B2B outbound team actually set up a compliant calling process?

Here's what a defensible B2B calling process looks like in practice. Five moves.

Scrub your list for cell phone numbers first. B2B calls to business lines are DNC-exempt, but autodialing a cell phone without consent is a separate TCPA risk the exemption doesn't touch. Use a phone validation or carrier lookup service to flag mobile numbers and route them to human-dialed or consent-based workflows.

Second, check the dnc registry for any numbers that might be residential. If your lists include sole proprietors, home-based businesses, or small shops with a single line, those numbers can easily sit on the national DNC list. You reach the registry through the FTC's telemarketer access portal. The how do i get the do not call list guide walks through the subscription process for commercial callers.

Third, keep your own suppression list and make opt-out honoring automatic, not manual. Every CRM should have a "do not call" field that blocks future outreach from any rep, period.

Fourth, know your state exposure. If you dial heavily into Florida, Indiana, Pennsylvania, or Texas, read those state statutes or have counsel do it. Registering as a telemarketer where required (Indiana is one) before you start calling protects you in ways that are hard to fix after a complaint lands.

Fifth, train your reps on what the exemption does and does not cover. A sales manager who tells the team "we're B2B, DNC doesn't apply to us" is setting them up to get blindsided the day a prospect's attorney cites the TCPA.

LeadCompliant offers a free compliance kit and a DNC number checker that helps small teams audit lists before dialing. It's not a substitute for legal counsel on your specific setup, but it catches the obvious problems.

None of this is legal advice. If your call volume is significant or your lists are large, get a TCPA attorney to review your program. An hour of specialized legal review costs a rounding error next to even a small settlement.

Can a business register its own number on the national DNC registry?

Technically, yes. The national registry accepts any number, and there's no verification step confirming the registrant is a person rather than a business. But that registration almost certainly does not give a business the protections the registry was built to provide.

The registry's protections under the TSR and TCPA run to residential subscribers and consumers. A business that registers its number does not turn that number into a residential subscription. A telemarketer calling it and relying on the B2B exemption would still have a strong argument that the TSR and TCPA DNC provisions don't apply, even though the number shows up in the registry.

Some states run their own DNC registries that allow business registrations, or that don't split business and residential the way federal law does. In those states, a registered business number might carry more protection under state law than under federal law.

If you run a business and want the sales calls to stop, the sharper tool is a firm oral or written do-not-call request straight to each telemarketer, which triggers the company-specific list duty even for B2B callers. You can also report repeat offenders to the FTC through the do not call list report system or your state AG.

How does the DNC registry work for government and nonprofit callers in B2B contexts?

Political calls, survey calls, and nonprofit calls have their own exemptions under both the TSR and the TCPA, separate from the B2B exemption. ^[1][2] These exemptions turn on the purpose of the call, not on who's being called.

For B2B readers, the sharper question is whether a government entity calling your business has any special status. Government agencies are not covered by the TSR at all. The TSR applies to sellers and telemarketers in commercial transactions. A state agency calling businesses as part of a regulatory or compliance function simply sits outside the TSR's scope.

If your business gets calls from a supposed government entity trying to sell you something ("we're updating the federal business directory," that flavor of pitch), those calls are commercial even when the caller claims a government tie. The label doesn't buy them a pass. The government do not call list page covers how genuine government calls interact with the registry framework.

For most outbound B2B teams, the government and nonprofit exemptions are background. What matters is your own compliance posture as a commercial seller.

What records does a B2B telemarketer need to keep, even under the exemption?

Relying on the B2B exemption doesn't mean you run with zero documentation. The TSR requires any telemarketer who relies on an exemption to be able to show why the exemption applies. That means records.

For B2B callers, the documentation that matters most: evidence that the numbers you dialed were registered to businesses and not individuals, records of your internal do-not-call list and how you maintain it, opt-out logs proving you honored suppression requests inside the 30-day window, and any consent records for cell phone numbers you dialed by autodialer.

The FTC can request these records in an investigation. A plaintiff's attorney can pull them through discovery in litigation. "We thought we were B2B exempt" is not a defense if you can't show you actually checked.

Keep call logs and consent records at least 24 months, consistent with TSR requirements. ^[1] Some attorneys push for 48 months given the TCPA's four-year statute of limitations on certain claims. ^[2]

If your team runs a CRM, set it to log call dates, called numbers, outcomes, and opt-out requests automatically. Manual spreadsheets beat nothing, but they grow gaps. A system that produces records as a byproduct of normal selling is far more defensible than one that leans on reps to update a do-not-call sheet by hand.

Frequently asked questions

Do B2B telemarketers have to register with the FTC or check the DNC list at all?

For calls to business lines, no federal registration or DNC scrub is required under the TSR or TCPA, because those calls fall outside the definitions of covered telemarketing. But if any numbers on your list might be residential (sole proprietors, home offices, personal cell phones), scrub those. Some states also require telemarketer registration regardless of whether calls are B2B. Check state rules before assuming the federal exemption covers everything.

What happens if I accidentally call a residential number while doing B2B outreach?

If that number is on the national DNC registry and you called it without an established business relationship or prior written consent, you've violated the TCPA. The $500-per-call private right of action applies, trebled to $1,500 for willful violations. The B2B exemption doesn't save you, because it's definitional: it only covers calls actually made to business subscribers. Scrubbing your lists for residential and cell numbers before dialing is the only reliable prevention.

Can I use an autodialer for B2B calls without getting consent?

For business landlines, the TCPA's autodialer restrictions in Section 227(b) don't apply the way they do for cell phones. But autodials to cell phones, even for B2B, require prior express consent under the TCPA regardless of the DNC exemption. After Facebook v. Duguid (2021), the ATDS definition is narrower, but the cell phone consent requirement stands. Using a human-operated dialer for business cell phones is safer than an autodialer without consent.

Are sole proprietors protected by the national DNC registry?

Yes, in practice. If a sole proprietor uses a number registered in their personal name, that number is almost certainly a residential subscriber number under the TCPA. Both the FTC and FCC have acknowledged that calling a home-based business or a sole proprietor's personal line looks more like calling a consumer than calling a corporation. If a sole proprietor's number sits on the DNC registry, treating the call as B2B-exempt is a risk you should avoid.

Does the B2B exemption apply to text messages and SMS campaigns?

SMS to business numbers sent by an autodialer is governed by the TCPA's Section 227(b) cell phone provisions, not the DNC registry provisions. Since most business contacts get texts on cell phones, the autodialer consent requirement applies. The B2B DNC exemption doesn't map cleanly onto SMS, because texts almost always land on mobile numbers. Treat B2B SMS as needing human sending or prior express consent, not as automatically exempt.

How do I know if a phone number on my list is a business or residential number?

Use a carrier lookup or phone intelligence service to check line type (landline, mobile, VoIP) and the registered subscriber name. A number registered to a company name is stronger evidence of a business line. A number registered to an individual at what looks like a home address is a red flag. No lookup is perfect, and for borderline cases, treating the number as residential is the conservative and defensible choice.

Does calling a business phone number that's on the DNC list expose me to liability?

Generally no, if the number is genuinely a business line and your call is a legitimate B2B solicitation. The DNC registry's federal protections don't apply to business subscribers. But if the business registered the number under an individual's name, or you're pitching a consumer-use product, the analysis shifts. Some state DNC laws also treat business numbers differently than federal law does.

What is an established business relationship and does it matter for B2B calls?

An established business relationship (EBR) is a federal safe harbor that lets a seller call someone who purchased in the past 18 months or made an inquiry in the past 3 months, even if that person is on the DNC registry. For B2B calls, the EBR matters less because B2B calls are already DNC-exempt. The EBR matters most for B2C calls, or for B2B calls to numbers that turn out to be residential.

Are there any federal cases that confirm the B2B exemption is real and holds up in court?

Yes. Courts have consistently dismissed TCPA DNC claims where the called number was a business line and the call was a commercial B2B solicitation. The statute's definitional structure, requiring a residential telephone subscriber, has been recognized repeatedly as excluding business numbers. The harder litigation tends to involve cell phones and disputed line types, not clear business landlines.

Do I need written consent to call a business contact's cell phone for B2B purposes?

For autodialed calls, the TCPA's Section 227(b) requires prior express consent for calls to cell phones. This holds even when the purpose is B2B and even if the number sits on a business contact list. For human-dialed calls from a static list, the consent requirement is less clear after Facebook v. Duguid. As a practical matter, getting written consent for any mobile outreach, B2B or not, is the safest posture.

How often should I scrub my B2B calling list against the DNC registry?

The TSR requires that consumer lists be scrubbed against the national DNC registry no more than 31 days before a call is made. For B2B lists, there's no federal scrubbing mandate for pure business numbers, but scrubbing every 30 to 31 days is good practice for any numbers that might be residential or borderline. The do not call telemarketer list access system lets commercial callers download updated registry data monthly.

Can a business sue me under the TCPA for an unwanted B2B call?

A business entity cannot bring a TCPA claim as a called party for DNC registry violations, because the statute's DNC protections run to residential subscribers. An individual employee who received an autodialed call on their personal cell phone could potentially bring a TCPA Section 227(b) claim, even if the call's purpose was commercial. That distinction matters: the individual on the other end has standing, not the company.

What is the FTC's role versus the FCC's role in B2B telemarketing enforcement?

The FTC enforces the Telemarketing Sales Rule, which governs commercial sellers and telemarketers in transactions with consumers and, to the extent covered, with businesses. The FCC enforces the TCPA, which covers telephone solicitations to residential subscribers and autodialed calls to cell phones. Both agencies pursue egregious violators, and state AGs can enforce both frameworks. Most B2B enforcement involves state AG complaints or private TCPA litigation, not direct federal action against small operators.

Sources

1. FTC, Telemarketing Sales Rule (16 CFR Part 310): The TSR's definition of 'telemarketing' excludes B2B calls; the rule does not apply to business-to-business calls because such calls are not telemarketing within the rule's definition; company-specific do-not-call and opt-out obligations; 24-month record retention requirement
2. U.S. Code, 47 U.S.C. § 227 (Telephone Consumer Protection Act): TCPA prohibits telephone solicitations to residential telephone subscribers on the national DNC registry; Section 227(b) restricts autodialed calls to cell phones; $500 per-violation private right of action, trebled to $1,500 for willful violations; four-year statute of limitations for certain claims
3. FCC, Rules and Regulations Implementing the TCPA (47 CFR 64.1200): FCC established national DNC registry covering residential telephone subscribers; B2B calls outside scope of residential subscriber protections; company-specific do-not-call list requirements
4. U.S. Supreme Court, Facebook, Inc. v. Duguid, 592 U.S. 395 (2021): ATDS definition under TCPA requires use of a random or sequential number generator; narrowed the scope of what qualifies as an autodialer
5. Florida Legislature, Florida Statutes § 501.059 (Telephone Solicitation Act): Florida's amended telemarketing law restricts automated calls to Florida area code numbers; $500 per call for negligent violations, up to $1,500 for willful violations; broader coverage than federal TSR in some respects
6. Indiana General Assembly, Indiana Code § 24-4.7 (Telephone Privacy Act): Indiana maintains its own DNC list and has broad telemarketer registration requirements; penalties up to $10,000 per violation under state enforcement
7. FTC, Adjustments to Civil Penalty Amounts (16 CFR Part 1): FTC civil penalty ceiling for TSR violations is inflation-adjusted annually (roughly $53,000 per violation as of the most recent adjustment)
8. U.S. Court of Appeals D.C. Circuit, ACA International v. FCC, 885 F.3d 687 (2018): Court vacated parts of FCC's 2015 TCPA omnibus ruling on ATDS definition; shaped ongoing TCPA class action litigation landscape