This is a question checklist, not legal advice
Messaging requirements depend on the jurisdiction, content, relationship and service. We do not determine whether a specific campaign is lawful or supply a universal consent statement. Before sending, establish the applicable merchant, carrier and legal requirements with the appropriate sources and qualified advice. Do not use a generic website checklist as a substitute for that determination.
Make the proposed use specific
Describe who will send, what kinds of messages are proposed, how often they may occur and how a recipient can stop or change preferences. Keep marketing, service updates and unrelated purposes distinct. A contact’s presence in an old system does not answer these questions. If your evidence is incomplete, hold that record rather than stretching its meaning to fill a campaign audience.
Assign responsibility for changes
Someone must own preference changes, complaints and disputed records. Identify the authoritative system and the process that prevents a later import from undoing a person’s choice. An integration label alone does not establish that behavior. Do not upload a live list to test it casually; use an appropriately authorized, controlled workflow and confirm the resulting state.
Keep planning data small
Our planning tools need counts and fictional descriptions, not names or numbers. Use them to reveal missing decisions before personal data moves. The eventual sender may require evidence or review, and the merchant’s documented import process should be followed. If the proposed use cannot be explained clearly enough for review, it is not ready merely because a file can be uploaded.
Respect the complaint signal
The FCC provides a consumer information and complaint route for unwanted texts. Treat an unwanted-message report as a reason to investigate the audience record and the sending process, not simply as an engagement statistic. That resource is not campaign approval or a substitute for advice about your own obligations. Keep an unresolved audience out of a pilot while the relevant questions are answered.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- TXT180 pricing — Merchant documentation · txt180.com · Merchant-controlled · checked 2026-10-02
- TXT180 feature documentation — Merchant documentation · txt180.com · Merchant-controlled · checked 2026-10-02
- FCC unwanted calls and texts resource — Regulatory guidance · consumercomplaints.fcc.gov · Publisher independence not verified · checked 2026-10-02