The short version
Quick answer
Start with three things: save the full conversation with dates, preserve the original voicemail audio if there is any, and write down the exact opt-out and later contact. Keep originals separate from notes or redacted copies. You do not need to reply to a suspicious sender or disclose personal information to build an organized record.
A five-minute preservation pass
These are editorial organization suggestions, not a statutory evidence checklist or a guarantee of admissibility.
Save context, not just the latest message
Capture the conversation before and after an opt-out. Include visible dates, times, sender details and the receiving account or number in your private record. Use overlapping screenshots if the thread is long.
Keep the underlying file
Retain original messages where practical. If your app offers a voicemail export, save the original audio and separately capture its date, displayed caller information and duration. A transcript is a reading aid, not a replacement for audio.
Save the permission record
Keep any quote form, application, purchase confirmation or disclosure already in your possession. Record its URL and capture date. Do not resubmit a form just to reconstruct it; a current page may not be the version originally seen.
Make a separate chronology
For each event record date, time zone if known, message purpose, sender as displayed, exact request to stop, and the related filename. Mark an uncertain time or identity as uncertain.
Store privately
Keep an unchanged original and a separate redacted working copy if needed. Back up through storage you control. Do not publish other people’s details or send your records to this publication.
Why exact dates and exact words matter
The FCC’s covered revocation rule uses reasonable time with an outside ten-business-day limit, and recognizes specified reply words as well as other reasonable requests. Its confirmation rule distinguishes a limited nonmarketing response from promotional content.
Those distinctions make the original text, instruction, receipt evidence and later content more useful than a note saying only that a company ignored STOP. They do not make your own chronology a legal finding.
Source basis: 47 C.F.R. § 64.1200
Fictional example: keep observation separate from inference
A fictional thread contains a September 1 promotion, a September 2 STOP reply, a confirmation one minute later and a September 8 promotion displaying a different sender. Save each item in order.
An annotation can say: later promotion uses a different displayed sender; business named in the body appears the same. It should not say: proven same defendant. Keep the original visible identifiers privately and flag attribution for further investigation. The dates illustrate documentation, not a finding that a deadline was violated.
Source basis: 47 C.F.R. § 64.1200
Voicemail and caller identity
The FTC asks unwanted-call reporters for displayed caller information, any callback information, and the date and time when available. It also warns that caller ID can be spoofed. Record what appeared without treating the display as conclusive identity.
Preserve voicemail you already received. This checklist is not an instruction to record a live conversation. If live recording is contemplated, obtain advice specific to the circumstances rather than treating voicemail-preservation steps as permission.
Source basis: FTC Consumer Advice
Use safe reporting paths
For an unexpected text requesting sensitive information, avoid its links and verify the supposed business independently. The FTC lists in-app reporting, forwarding to 7726 and ReportFraud.ftc.gov as reporting paths.
Before using an app control, inspect whether it also deletes content or shares it with a provider. Keep what you need first. The printable checklist linked above can organize your private notes; it does not transmit them here.
Source basis: FTC Consumer Advice