A TCPA Text Demand Needs a Consent-and-Message File Before Any Reply
A TCPA text message demand letter response should preserve the demand, message history, consent source, opt-out records, vendor logs, and counsel deadline before anyone argues or offers payment.
A text-message demand should be reconstructed recipient by recipient before the business argues consent, blames a vendor, or discusses a settlement amount.
For a TCPA text message demand letter response, preserve the full demand and delivery proof, suspend the specific campaign or audience if messages may still be going out, export every message and status event for the named number, and trace the exact source, language, date, and scope of any claimed consent. Preserve STOP or other revocation messages, suppression activity, vendor logs, contracts, and the response deadline, then give the file to qualified TCPA counsel before replying.
Do not delete a campaign, recreate consent from memory, contact the recipient through another channel to debate the claim, or assume that a lead vendor owns the risk. The business needs the original records and a controlled chronology before it needs an argument.
The TCPA Text Message Demand Letter Response Kit adds editable demand intake, message ledger, consent map, vendor request, preservation notice, counsel brief, response controls, and follow-up tracking behind this free workflow.
Build seven evidence lanes before you reply
| Lane | What to capture | Question it supports |
|---|---|---|
| Demand control | Sender, law firm, claimant, number, alleged dates, legal theories, requested amount, deadline, attachments, and delivery proof. | What is actually alleged and when is action required? |
| Message history | Body, timestamp, time zone, sender ID, recipient, campaign, delivery status, replies, and platform export. | Which messages were sent and what did each one say? |
| Purpose and technology | Marketing, account, service, collection, confirmation, manual send, automation, dialing or messaging platform, and workflow trigger. | What rule set and factual questions may be relevant? |
| Consent source | Form, checkbox, disclosure, page version, submission time, IP or audit record, purchase relationship, and scope represented. | What evidence supports the claimed permission? |
| Revocation and suppression | STOP or other request, timestamp, inbound content, confirmation, suppression-list update, downstream sync, and later sends. | Was a revocation received and what happened next? |
| Vendor chain | Lead source, agency, platform, integrator, contract, campaign setup, data handoff, audit logs, and indemnity or notice terms. | Who controlled each step and what records still exist? |
| Response control | Counsel owner, preservation scope, insurer notice question, response authority, communication log, submission receipt, and next date. | Who may say what, through which channel, and by when? |
The FCC has explained that opt-out and revocation rules depend on the communication and current rule in force. Its 2024 TCPA consent order addressed honoring company-specific revocation requests and a one-time clarification message in limited circumstances. A later 2026 FCC order extended a waiver for part of the revocation rule. Do not reduce that moving framework to a generic ten-day promise or a canned defense. Counsel should verify the rule, effective date, message type, and jurisdiction that apply to the actual record.
Use four controls while the claim is active
The owner forwards one screenshot, says the lead opted in, blames the vendor, and offers money before exporting messages or finding the actual disclosure.
Each challenged message is matched to its consent source, purpose, platform event, opt-out history, vendor chain, record gap, and counsel question.
Copy this message evidence row
Message row
Demand item and claimant: [reference]
Recipient number: [masked internal reference]
Message timestamp and time zone: [date / time / zone]
Exact message and sender ID: [export / file]
Purpose and campaign: [marketing / service / other]
Platform and trigger: [system / workflow]
Delivery status and reply: [status / content]
Consent source and date: [form / purchase / other]
Disclosure or form version: [file / URL snapshot]
Opt-out or revocation event: [date / content / none located]
Suppression result and later sends: [details]
Vendor or lead-source records: [files / requested]
Conflicting or missing evidence: [list]
Preservation owner: [name / date]
Qualified-review question: [specific question]
Response status and next deadline: [status / date]
Send a narrow vendor preservation request
Subject: Preserve and export records for [campaign / recipient reference]
We received a claim concerning messages associated with [campaign or account] and the period [dates]. Preserve the original campaign configuration, message content, sender IDs, recipient events, consent-source fields, form or disclosure versions, inbound replies, opt-out and suppression events, delivery logs, user changes, integrations, and exports. Do not delete, overwrite, or recreate records. Please confirm preservation and provide the available native export plus a description of any retention limits by [date]. Direct claim-related communication to [response owner].
Have counsel tailor the request, contract notice, privacy handling, and preservation scope. Do not send a claimant's personal information to vendors that are not authorized to receive it.
Get the free Emergency Triage Sheet
The first three moves for any business emergency, plus one practical fix in your inbox each week.
No spam. Unsubscribe anytime.
Small business example
A hypothetical home-services company receives a demand listing six promotional texts sent over three weeks. The agency says the number came from a quote form, while the CRM shows two contacts with similar names. The owner pauses that campaign, exports the six messages, locates the form version used on the alleged submission date, and finds one STOP reply that did not sync from the messaging platform to the CRM suppression list.
The company preserves the mismatch, requests the agency's lead-source logs, records which later messages followed the failed sync, and gives counsel the demand, ledger, contracts, and system history. The example does not establish liability or a settlement value. It shows why one screenshot or a generic opt-in statement is not enough.
TCPA demand response checklist
- Save the complete demand, envelope or email, attachments, and delivery proof.
- Calendar the requested response date and any litigation, insurer, or contract notice questions.
- Verify the sender and claimant through an independent channel.
- Pause the specific disputed messaging lane when appropriate without deleting evidence.
- Export every challenged message, status event, reply, and campaign setting.
- Locate the exact consent source, language, version, date, and audit record.
- Trace every opt-out or revocation through platform, CRM, and suppression systems.
- Preserve vendor contracts, setup records, data handoffs, and access history.
- Record gaps and conflicts instead of filling them from memory.
- Use qualified TCPA counsel to assess federal, state, class, and response issues.
- Control who may communicate, negotiate, notify an insurer, or preserve authority.
- Save the final response, attachments, delivery receipt, and next date.
FAQ: should we reply that the customer consented?
Not until the business can identify the actual consent source, disclosure, version, timestamp, scope, and message purpose, and counsel has reviewed the record. A CRM field that says opted in may be a lead, not proof. State telemarketing and privacy rules may also matter. This is operational education, not legal advice.
Connect text compliance to daily customer messages
If the team sends operational updates, the service-delay text workflow now includes a consent and suppression checkpoint before templates are reused. If the claim involves a deceptive or missing privacy practice, use the small-business data breach response checklist to preserve systems and facts without assuming that every messaging complaint is a breach.
Free version vs. full kit
This article gives you the free version: the seven-lane evidence map, message row, vendor preservation request, worked example, and response checklist. The paid kit adds editable demand intake, message and consent ledgers, opt-out reconstruction, vendor requests, preservation controls, counsel briefing, response tracking, and prevention tools.
Get the TCPA Text Message Demand Letter Response Kit
The All-Access membership includes the complete kit library while membership is active. The one-time TCPA response kit remains the primary next step for this article.
Fix the next one before it starts.
Join the list for the free Emergency Triage Sheet and a new practical fix every week.
No spam. Unsubscribe anytime.