Published September 1, 2026Editorially reviewed
Answer first
TL;DR
Automated plumbing texts need a documented consent basis, clear sender identification, usable opt-out handling, accurate records, secure vendors, and qualified legal review. Federal and state rules can differ, and marketing messages can face stricter requirements. Treat this checklist as an implementation aid, not legal advice, and review every campaign before launch.
What should be documented before sending?
Record the message purpose, recipient source, consent language, consent timestamp, number, sender, campaign, vendor, and planned retention. Separate operational messages from marketing campaigns.
How should opt-outs work?
Honor recognized opt-out requests promptly across connected systems. Confirm suppression sync, agent visibility, imported lists, number changes, and manual overrides through controlled tests.
Do timing and frequency matter?
Yes. Define permitted sending windows, frequency caps, follow-up length, and escalation rules with legal counsel. Account for the recipient's location and time zone.
What should vendor review cover?
Review data use, subprocessors, security, retention, access, incident terms, consent controls, suppression behavior, audit logs, number registration, and export or deletion procedures.
When is legal review needed?
Obtain qualified advice before automated marketing, purchased or shared lists, reactivation campaigns, recorded calls, sensitive information, new jurisdictions, or a material workflow change.
Source ledger
Which primary sources were reviewed?
Provider capabilities and prices are attributed to official pages. Company-published material describes what the provider documents and does not establish independent performance.
Buyer questions
Frequently asked questions
Is this a substitute for a controlled pilot?
No. Public documentation can establish available features. It cannot prove performance in a specific plumbing operation.
Who should own implementation?
Assign one operational owner and one technical owner. Name a backup and a person responsible for failed records.
How often should the workflow be reviewed?
Review it after product, script, campaign, staffing, legal, integration, or scheduling changes. Sample real records on a regular schedule.
What evidence should a buyer request?
Request current documentation, a live workflow demonstration, pricing terms, integration details, security materials, and a test using representative scenarios.
Improve this research
Have stronger evidence?
Submit a correction or an official source for editorial review. Evidence submissions are free and do not affect placement.
Submit evidence