A2P 10DLC and TCPA Compliance for Collections Texting
Texting is the highest-converting channel in collections, and the hardest to get right. Here is how to pass carrier registration and stay inside TCPA and Reg F.
You launched texting because the math was obvious. Consumers ignore letters, screen calls, and pay from their phones. Then the messages started disappearing. Payments did not move. Somewhere between your platform and your consumer's handset, a filter you never signed a contract with decided your traffic looked like spam.
Collections texting answers to two authorities that do not talk to each other. Federal regulators decide whether you are allowed to send the message. Wireless carriers decide whether it arrives. You can be flawlessly compliant and still get filtered into silence, or fully registered and still exposed to a TCPA claim. Both systems are knowable, and they overlap more than they conflict.
Two Rulebooks, One Message
The legal layer is enforceable in court. The Telephone Consumer Protection Act (TCPA) governs consent to send automated messages to a wireless number, with the FCC writing the implementing rules. The Fair Debt Collection Practices Act, implemented through the CFPB's Regulation F, governs how a debt collector may communicate about a debt, including by text. Violations here produce statutory damages, class actions, and exam findings.
The carrier layer is commercial and enforced by throttling. AT&T, T-Mobile, and Verizon require every business sending application-to-person traffic over standard 10-digit numbers to register through The Campaign Registry (TCR), applying the CTIA Messaging Principles and Best Practices as their standard. There is no hearing and no appeal. Noncompliant traffic is filtered, throttled, or blocked.
“Regulators can penalize you for a message you sent. Carriers can quietly stop the message from ever being delivered. A collections texting program has to survive both.”
A2P 10DLC: What Registration Actually Requires
Registration happens in two stages. First you register your brand, the legal entity behind the traffic. TCR verifies the identity you submit and assigns a trust score, generally on a 0–100 scale, based on how cleanly your information matches authoritative records.
- Exact legal business name as it appears on your EIN registration — a mismatch as small as "Inc." versus "Incorporated" commonly fails vetting
- EIN or Tax ID, business type, and registered address
- A live website with your identity, contact information, a privacy policy, and published messaging terms
- Industry vertical and an authorized vetting contact
Second, you register each campaign — the specific use case and content. This is where collections programs stumble, because the submission must describe how consumers consent, what they will receive, and how they opt out. Vague opt-in language is the most cited rejection reason. "Receive updates from us" does not survive review. The description has to name the sending entity, state plainly that the consumer is agreeing to receive text messages, describe the message type, and disclose frequency and message-and-data-rates language.
Your trust score then determines throughput — how many messages per second each carrier will accept. An unvetted or low-scored brand may be limited to roughly a single message per second per carrier, while a well-vetted brand can send substantially more. That is the difference between working a morning file in an hour and watching it trickle out all day. Treat vetting as a capacity decision, not paperwork.
Why Collections Campaigns Get Rejected
Debt collection sits in a restricted category alongside payday lending and credit repair. Campaigns here get extra review at registration and remain subject to content filtering after approval. Approval is not immunity. It is permission to be watched closely.
- Opt-in description that does not match how consent is actually collected in your workflow
- Shortened or shared-domain links, which filters score as spam — use a branded domain you control
- Missing STOP and HELP language in sample content or the campaign description
- A website that does not exist, does not mention SMS, or has no privacy policy
- Content that reads as a threat, an ultimatum, or anything scoreable as pressure
- Brand identity that does not match the entity on the consumer's account
Filtering is scored on content patterns, not compliance intent. Short, plain, identity-forward messages routing to a clean self-service portal outperform clever ones. Restraint is a deliverability strategy.
See how this works for your operation
Book a 20-minute strategy call with a Hyventur specialist.
TCPA: Consent Before the First Message
The consent standard depends on what the message does. Purely informational collection messages — balance notices, payment confirmations, plan reminders — generally require prior express consent, which may be written or oral. The stricter prior express written consent standard applies to telemarketing content. That line is easy to cross by accident: the moment a message promotes a refinance offer or an unrelated service, you have arguably moved into telemarketing.
Consent also has to be traceable. Whether it came from a credit application, a servicing portal, or an original creditor's records, you need the timestamp, the channel, the language shown, and the number it attached to. Placement agreements should require the creditor to warrant consent and deliver the evidence with the file, not assert it in a schedule nobody tests. That documentation is among the first things reviewed during an exam or portfolio audit.
Revocation: The Rules That Changed
The FCC's revocation framework took effect April 11, 2025, and it materially widened how a consumer can say stop. Consent may be revoked by any reasonable means that clearly expresses the desire not to receive further messages. You may not require a specific keyword or a designated channel as the only path out.
- STOP, QUIT, END, REVOKE, OPT-OUT, CANCEL, and UNSUBSCRIBE all count when sent in reply to a text
- Revocation is equally valid through a website or phone number you provide for that purpose, or a key-press option on a call
- Requests must be honored within a reasonable time not to exceed 10 business days of receipt
- You may send one confirmation message to clarify scope; absent clarification, stop all messages requiring consent
- A free-form reply — "please stop texting me" — is a valid revocation even though no keyword fired
That last item is where most operations break. Keyword handling is automated at the platform level. Free-form revocations arrive as ordinary inbound messages and sit in a queue until a human reads them. If nobody works that queue daily, the clock runs against you.
One related requirement is still pending. The broader "revoke-all" provision in 47 C.F.R. § 64.1200(a)(10) — which would treat a revocation on one topic as applying to all future calls and texts on unrelated matters — has been extended again, most recently to January 31, 2027, while the FCC reviews the rule. Nothing else about revocation changed with that delay, and building one cross-channel suppression list now is the safer posture regardless of where the rule lands.
Regulation F: The Layer Carriers Never Check
Carrier approval says nothing about the FDCPA. Regulation F sets conditions specific to debt collectors that no TCR review will catch, and § 1006.6(d) provides a bona fide error safe harbor for texting only when specific procedures are followed. Reg F's broader digital rules are covered in our compliance checklist.
- Text the number only where the consumer recently used it to contact you about the debt, or where you have direct prior consent to that number
- Confirm through a complete and accurate database — such as the FCC's Reassigned Numbers Database — that the number has not been reassigned, within the rule's timeframes
- Include a clear and conspicuous statement describing a reasonable and simple opt-out method in every electronic communication, per § 1006.6(e)
- Never charge a fee or demand information beyond the opt-out preference and the number
- Send only between 8:00 a.m. and 9:00 p.m. local time, measured when you send, not when they read
- Write content so a third party glancing at the screen learns nothing about the debt
Reassigned-number checking is the step teams most often skip, and it creates FDCPA and TCPA exposure at once — a wrong-party text is a third-party disclosure problem and a consent problem in a single send. The full sequence is in our guide to Reg F's digital communication rules.
Build the Suppression List First
If you take one operational step from this article, make it this: consent state and opt-out state belong in one system of record, applied across every channel and placement, before the message queue is built. Most compliance failures are not decisions. They are synchronization gaps.
Your dialer, texting platform, email tool, payment plan engine, and agent desktop should all read the same suppression record, and any of them should be able to write to it. Free-form replies get triaged the same day. Every consent and revocation event is logged with source, timestamp, channel, and exact language — because the ability to reconstruct the record is what turns a threatened claim into a closed file. Once the messages are landing, our text-to-pay implementation guide covers what to do next.
Frequently asked questions
Do I need A2P 10DLC registration if I only send a few hundred texts a month?
Yes. Registration is required for any business sending application-to-person messages over standard 10-digit U.S. numbers, regardless of volume. Unregistered traffic is subject to filtering and blocking by the major carriers, and unregistered-traffic surcharges may apply. Low volume affects your throughput allocation, not whether you must register.
Is a phone number on a credit application enough consent to text a consumer?
It can support prior express consent for informational collection messages, which is the applicable standard for non-telemarketing content. But it does not satisfy Regulation F on its own — you still need to meet the § 1006.6(d) conditions, including reassigned-number verification, and include an opt-out notice in the message. If the message contains promotional content, the stricter prior express written consent standard applies.
If a consumer replies "stop calling me" to a text, does that stop texts too?
Treat it as a revocation for that channel at minimum, and honor it within 10 business days. Under the FCC's framework, a consumer may revoke by any reasonable means that clearly expresses intent to stop receiving messages; no specific keyword is required. The broader rule extending one revocation across all channels and topics has been delayed to January 31, 2027, but suppressing across channels now is the lower-risk approach.
My campaign was approved but messages still aren't delivering. What happened?
Approval and delivery are separate gates. Carriers filter approved traffic on content signals: shortened or shared link domains, missing STOP and HELP language, pressure or deadline phrasing, high opt-out rates, or sudden volume spikes. Debt collection is a restricted category that receives ongoing scrutiny after approval. Start by switching to a branded link domain, simplifying copy, and checking your opt-out rate before assuming the problem is registration.
Ready to recover more, with less friction?
Give consumers a payment experience they'll actually finish — and give your team the clarity to see it working. Talk to a Hyventur specialist about your receivables operation.