SMS and Text Outreach Compliance in B2B Collections
Texting business debtors triggers federal rules consumer collections teams can skip.

Collections teams started texting business contacts for one simple reason: email stopped working. Inboxes are crowded, open rates are terrible, and a text message gets read in minutes, not days. That's the operational logic, and it's sound. The legal logic that usually comes with it (texting a business is different from texting a consumer, so the rulebook gets lighter) is not sound, and it's the single most expensive assumption in B2B collections today.
The assumption isn't baseless. The FDCPA and Regulation F, the two main federal laws built around debt collection, apply to consumer debt. They do not apply directly to commercial or B2B debt at the federal level. So a collections team that reads those two laws and concludes "we're mostly in the clear" isn't making that up, having stopped reading one law too early. The Telephone Consumer Protection Act, the TCPA, doesn't care whether the number on the other end belongs to a person or a business. It applies in full, regardless. That gap, where the TCPA applies completely but the FDCPA and Reg F only apply if a company chooses to follow them voluntarily, is the whole ballgame. Everything else in this piece builds from that one line.
The three-layer compliance stack that governs every business text sent for collections
Think of B2B collections SMS as a three-layer stack, where each layer can sink the program on its own, regardless of how well the other two are handled.
Layer one is the TCPA, a federal law enforced by the FCC. The TCPA treats a text message as a "call" for legal purposes. SMS gets the same consent rules as a phone call, business recipient or not. Penalties run up to $1,500 per willful violation, and because that number applies per message, one poorly configured automated campaign sent to a few thousand contacts can turn into six or seven figures of exposure before anyone notices the mistake. Two updates from 2025 and 2026 matter here. First, as of April 2025, a business has to honor opt-outs sent through any reasonable method, not just the word STOP, and has to process them promptly. Second, the FCC's one-to-one consent rule, which would have forced every single sender to collect its own consent directly rather than share it, got struck down by the Eleventh Circuit in January 2025 before it ever took effect, and the FCC formally scrapped it in September 2025. Multi-seller and lead-generator-shared consent remains legal at the federal level.
Layer two is the CTIA Messaging Principles, a set of industry standards. Carriers enforce these themselves, so breaking them brings something arguably worse than a fine: carriers filtering or blocking the messages. A text that never lands does as much collecting as no text sent. CTIA's October 2025 update covers consent documentation, opt-in and opt-out flows, how a sender identifies itself, content restrictions, and campaign registration, all of which apply to collections messages the same way they apply to a retail promotion.
Layer three is 10DLC registration, the carrier-level gate that decides whether a business text gets delivered. Carrier enforcement on this kicked in February 1, 2025. Texting from an unregistered number now means the message gets filtered or blocked before it reaches anyone. Every dollar spent on consent management, message drafting, and opt-out handling is wasted if the number sending the message was never registered.
These three layers stack on top of each other; none stands in for another. Passing one doesn't excuse failing another. A perfectly worded, fully consented text sent from an unregistered number still doesn't arrive. A registered number with a clean campaign still draws fines if consent was never properly collected.
The TCPA's ATDS definition and the gray zone it creates for account-based collections texting
The TCPA restricts an "automated telephone dialing system," an ATDS, and what counts as one decides which texting workflows need prior express written consent upfront and which sit in a gray zone. Duguid narrowed that definition considerably: a system only counts as an ATDS if it can use a random or sequential number generator. That detail matters for collections specifically, because collections texting doesn't dial random numbers. It works off a pre-loaded list of actual debtor accounts, which is about as far from random-number dialing as a system can get.
The practical read among people who work this area daily goes like this: manual, one-to-one texts sent to a publicly listed business number sit in genuinely uncertain territory. Automated blasts sent to a purchased or scraped contact list without consent are where the real TCPA exposure starts, gray zone or not.
That gray zone is smaller in practice than it looks on paper, because roughly a dozen states have passed their own mini-TCPA laws, and plenty of them are stricter than the federal standard. Where a state law sets a tighter rule, that state law wins. Virginia now requires opt-out records to be kept for 10 years, effective January 2026. Florida caps senders at three telephonic sales calls (calls or texts count the same) on one subject per recipient every 24 hours. Connecticut requires written consent for all telephonic sales outreach and backs it with real per-violation penalties. Arizona bars unsolicited texts to any number on its Do Not Call registry, with fines attached per violation.
A national collections portfolio can't pick and choose which state's rule to follow account by account. It has to run the tightest standard across every account in the book, because the ATDS gray zone offers no protection against a Virginia retention rule or a Florida frequency cap. Those operate independently of whatever the federal dialer definition says.
Regulation F's SMS provisions for commercial collections teams
Regulation F doesn't cover commercial debt. No part of it legally has to apply to a B2B collections program. And yet its SMS provisions have become the standard that serious collections operations hold themselves to anyway, partly because it's simply good practice, and partly because state laws keep drifting toward the same standards Reg F already set for consumer debt. Following Reg F voluntarily on commercial accounts is a bet that the rules are headed in one direction, and getting there early costs less than retrofitting later.
Reg F allows debt collectors to reach consumers by email and text, but it attaches real conditions. Every text needs an opt-out mechanism built in and has to identify who's collecting. No electronic communication, text or email, can go out between 9 PM and 8 AM in the recipient's own local time zone, not the sender's. One of the more demanding requirements: consent to text has to be renewed, or the phone number has to be checked against a reassignment database to confirm it hasn't changed hands, every 60 days.
Cross-channel frequency tracking creates real technical strain. Reg F's call-frequency rule, the familiar "7-in-7" limit, only counts phone calls toward that cap. Texts and emails don't count against it, though the FDCPA's general ban on harassment still covers every channel regardless. That sounds like a minor carve-out until a collections operation realizes what it actually requires: tracking consent and contact frequency across calls, texts, and emails as one combined picture, for every account, all the time. Most collections systems weren't built that way. They were built in silos: one platform logs the call, a separate one sends the text, a third handles email, and nobody's system talks to the other two. Accounts get traded between internal teams and outside vendors, and compliance records that should move with the account often get assumed to exist without being checked. At real portfolio scale, tracking all of that by hand is unrealistic, making automated, cross-channel tracking a basic requirement.
California SB 1286 and AB 1521
California passed the most significant expansion of B2B-specific collections rules on the books, and the obligation it creates isn't to watch the news, it's to sort every California account by category right now, because these rules are already active.
Governor Newsom signed AB 1521 on October 1, 2025. The bill defines "trade credit" in California law for the first time and makes clear that trade credit is not a "covered commercial debt" under SB 1286. In plain terms, a supplier collecting on ordinary goods-and-services credit extended business-to-business isn't covered by SB 1286. What is covered: commercial loans, merchant cash advance transactions, and finance leases below the statute's dollar threshold, where a natural person (not a corporate entity) personally guaranteed the deal. AB 1521 didn't expand SB 1286, it carved trade credit back out of it.
That leaves collections teams with a sorting job, account by account. For every obligor with a California address, the question is whether that obligor is a natural person who personally guaranteed a covered instrument (SB 1286 rules apply in full) or a corporate entity on a standard trade credit arrangement (SB 1286 doesn't touch it). There's no shortcut through this. It has to happen at the account level.
Texas moved on similar ground. Texas SB 140, effective September 2025, set new calling and texting windows for automated messages: 9 AM to 9 PM Monday through Saturday, and noon to 9 PM on Sunday. It also opened a private right of action under a state consumer protection statute. SMS violations in Texas can now be litigated by the people who received the texts, not just enforced by a regulator.
The consent and data-hygiene failures that turn compliant programs into TCPA liability
Most TCPA liability in collections texting doesn't come from someone deliberately ignoring the rules. It comes from consent records and contact lists that were never clean enough to stand behind.
Valid prior express written consent under the TCPA has four parts: a clear statement that the person agrees to get automated texts, the name of the actual company sending them, confirmation that saying yes wasn't a condition of doing business, and clear instructions for opting out. Verbal consent fails that test. Implied consent fails it. A pre-checked box on a web form fails it too, for marketing messages. None of those hold up if a program ever has to prove consent existed.
The one-to-one consent rule that takes effect in January 2026 adds another layer: consent gathered through a lead generation form or a third party can't be reused by a string of different downstream businesses. Any SMS database built on shared or purchased leads needs to be cleaned out and re-consented before another message goes out through it.
Reassigned phone numbers are a well-documented source of exposure. A number texted in good faith, with a legitimate consent record on file, can still generate liability if that number has since been reassigned to someone new who never agreed to anything. Checking the Reassigned Numbers Database isn't required by federal law, but it's strongly recommended, and doing so provides a safe harbor that a program without it simply doesn't have.
Outsourcing creates its own gap. When accounts move to a BPO or an outside collections agency, the consent record has to move with them, including the date it was given, the channel it came through, and the exact language the person agreed to. Opt-outs have to flow back to the original client in real time too, so both sides keep a matching suppression list. A program where the agency's list and the client's list drift apart is a program one dropped file away from a violation.
The April 2025 consent revocation rule raises the bar further. Opt-outs sent by email, left as a voicemail, or phrased informally all have to be honored promptly, not just the word STOP typed into a reply. Any system built to recognize only the keyword STOP is already out of compliance under that standard.
The FCC's Consent Revocation Rule and its 2027 extension
The FCC's Consent Revocation Rule would require a single opt-out from one program to stop every single communication across every program a company runs, all at once. The deadline for that rule was pushed to January 31, 2027, but the FCC then adopted a revised, narrower version of the rule on September 30, 2026, with a new effective date set at 30 days after it's published in the Federal Register, replacing the January 2027 date. That timeline shift hands collections operations an actual window to build the right infrastructure before the deadline lands, and most haven't started.
The one-to-one consent rule, which would have required each business to collect its own consent rather than share it, is a separate rule. That one got vacated by the Eleventh Circuit in Insurance Marketing Coalition Ltd. v. FCC and later formally repealed by the FCC itself. The Consent Revocation Rule is still on its own track, moving toward the narrower 2026 version.
Building for it now means three concrete things. First, universal opt-out infrastructure that can take in and act on a revocation signal from any channel, a reply text, an email, a voicemail, not just a STOP keyword. Second, a suppression list that updates across every program in real time, not in an overnight batch that leaves a few hours of exposure every day. Third, an audit trail that records the date, channel, and method of every single opt-out, held for however long the strictest applicable state law requires, which in Virginia's case is now an extended retention period as of January 2026.
Teams that build this now avoid a scramble when the 2027-adjacent deadline lands, and they build something that happens to satisfy half a dozen state retention and processing rules at the same time, because the infrastructure a universal opt-out system needs and the infrastructure state compliance needs turn out to be close to identical.
What a compliant B2B collections SMS program looks like
A compliant B2B collections SMS program is entirely possible to run. It just requires treating compliance as something built into the plumbing of the operation, not something a legal team signs off on once and forgets.
Consent acquisition sets the foundation. A web form with an unchecked consent box, a keyword opt-in, a signed paper form, or verbal consent for a purely transactional message, all of these can be valid, as long as the person took a clear affirmative step, the consent names the specific sender, and the record gets stored somewhere it can actually be pulled up later. For B2B accounts specifically, the smartest place to capture that consent is at the very start of the relationship, inside onboarding paperwork, a credit application, or a supplier agreement, well before any collections outreach ever gets sent.
Message construction carries its own fixed rules. Every marketing text needs the company's name, a working opt-out instruction, and a line confirming that saying yes wasn't required to do business. Every collections text needs to identify the collector and carry a functioning opt-out mechanism in that message itself, not just somewhere back in the first text of the thread. Quiet hours get measured by the recipient's own local time zone, never the sender's, which matters a lot for any portfolio spread across multiple states.
None of this is complicated in isolation. The TCPA sets the floor, CTIA and 10DLC decide whether a text arrives at all, Reg F sets the professional standard even where it isn't mandatory, and state laws keep raising the bar on top of it. A collections team that builds its SMS program around the tightest applicable rule, rather than the loosest one it can argue for, ends up with a program that works in every state it operates in, not just the ones nobody's checked yet.
Sources
- TCPA compliance: Requirements, rules and penalties
- Debt Collection Rule FAQs
- eCFR :: 12 CFR Part 1006 -- Debt Collection Practices (Regulation F)
- California SB 1286: What Debt Collectors Need to Know- Part 1
- New California Law Targets Unfair and Deceptive Commercial Debt Collection Practices
- California Expands Scope of State’s Fair Debt Collection Practices Act to Certain Commercial Debts
- California Enacts New Requirements Related to Collection of Commercial Debt in Amounts Less Than $500,000
- California SB 1286: What Debt Collectors Need to Know-Part 2


