The TCPA Basics Your SMS Program Needs Before You Send the First Text
Texting a customer is a lot more sensitive, legally, than emailing them, because the Telephone Consumer Protection Act treats an unwanted text more like an unwanted phone call than an unwanted email. A single non-compliant campaign can generate statutory damages per message, which adds up fast at any real list size.
This isn't legal advice. It's a runbook for the operational basics: consent, timing, opt-out, and recordkeeping, so your SMS program isn't relying on hope that no one complains.
Vendors Covered in this Article
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
Consent: what counts, and what doesn't
Express written consent is the standard for marketing texts under the TCPA, which generally means a clear, affirmative opt-in specific to receiving text messages, not a pre-checked box or consent buried in broader terms of service. A customer giving you their phone number for account security or order updates hasn't consented to marketing texts, even if you already have the number on file.
Get consent through a dedicated checkbox or keyword opt-in, such as a customer texting a word like JOIN to a short code, with the marketing purpose stated plainly at the point of opt-in, not implied. A common mistake is importing an existing email list's phone numbers, collected for a different purpose, directly into an SMS platform on day one. Every number needs its own dedicated opt-in trail, and a list that skips this step is a liability from the first send, not a growth shortcut.
Quiet hours and frequency: the limits most programs miss
Avoid sending outside roughly 8 a.m. to 9 p.m. in the recipient's local time zone, which means you need to track time zone by phone number or area code, not just send everything on your own clock. A program that sends a promotional blast at 7 a.m. Eastern is also sending it at 4 a.m. Pacific to part of the list.
Set a frequency cap and stick to it. A program that's texting daily because it converts tends to generate opt-outs and complaints faster than the short-term lift is worth, and complaint rates are one of the things regulators and carriers actually watch. Carriers can throttle or block a sending number that generates enough spam complaints, which means an aggressive frequency strategy can quietly damage deliverability for every future message, not just the ones that triggered the complaints.
Building an opt-out flow that actually removes people
STOP has to work immediately and completely: one reply should remove the number from every list it's on, not just the specific campaign that sent the message. A common failure is a STOP keyword that only unsubscribes from one segment while the contact keeps receiving texts from a different campaign or a different tool the marketing team also uses.
Confirm the opt-out with a final message, then send nothing further except transactional messages that are legally exempt, such as an order confirmation the customer already expects. Test this yourself on a quarterly cadence rather than assuming a platform configuration from a year ago still behaves the way you think it does, since tools and integrations change and a silent regression here is exactly the kind of gap that turns into a real complaint.
Keeping a consent record you can produce if asked
Record the timestamp, the exact language shown at opt-in, and the method (web form, keyword, in-store) for every phone number on your list, and keep that record as long as you're texting that number plus a reasonable retention period after. If a complaint or audit ever asks you to prove consent for a specific number, "we're pretty sure they signed up somewhere" isn't an answer that holds up.
A compliance automation platform such as Vanta or Drata can help you keep this kind of audit trail organized alongside your other compliance evidence, rather than scattered across spreadsheets and a marketing tool's export. Whatever system you use, make sure the record survives a platform migration: switching SMS providers without exporting the full consent history is a common way this evidence quietly disappears.
What to check with a lawyer versus what's settled
The requirement for express written consent, the STOP keyword standard, and the general prohibition on quiet-hours sends are well established and not really in dispute. What genuinely varies is how these rules interact with your specific list-building method, your industry (healthcare and financial services carry extra restrictions), and state-level laws that sometimes go further than the federal standard.
Have a lawyer review your specific opt-in flow and any state you have a meaningful customer base in before you scale an SMS program past a pilot. This is not a place where a marketing team's best guess should stand in for legal review, and the cost of that review is small compared with the cost of unwinding a non-compliant program after it's already reached thousands of numbers.
Before your first send, confirm each of these:
- Every number has express written consent that is specific to text messages and not buried in broader terms.
- Sends stay within roughly 8 a.m. to 9 p.m. in each recipient's local time zone.
- A frequency cap is set and followed, so no recipient is texted daily without a clear reason.
- STOP removes the number from every list and campaign, followed by one final confirmation message.
- Each number has a record of the timestamp, the opt-in language shown, and the method used.
- A lawyer has reviewed your list-building method, industry rules, and state-level laws.
What Good Looks Like
A compliant SMS program captures explicit, dedicated consent at opt-in, respects local quiet hours and a stated frequency cap, honors STOP immediately across every list, and keeps a timestamped consent record for every number on file.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
A platform like Vanta can help keep your SMS consent and audit records organized as part of a broader compliance evidence trail, though it's not a substitute for legal review of your specific opt-in flow.
Drata serves a similar role to Vanta for organizing compliance evidence, including SMS consent recordkeeping, as part of a wider compliance program rather than as a TCPA-specific tool.
Frequently Asked Questions
Do we need consent for order and shipping update texts too?
Transactional texts tied to a purchase the customer already made are generally treated differently from marketing texts and don't require the same opt-in standard. Check with your attorney before assuming a specific message qualifies, since the line between transactional and marketing content isn't always obvious.
Can we text customers who gave us their number for a different purpose?
Not for marketing, without separately obtaining consent specific to text messages. A phone number collected at checkout for delivery updates or account recovery doesn't carry consent to receive promotional texts, even though you technically have the number.
How quickly does a STOP request need to take effect?
Immediately, and it needs to apply across every list and campaign that number is on, not just the one that triggered the STOP. Confirm the opt-out with one final message and then send nothing further except legally exempt transactional messages.
About the numbers
This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.
Related Guides
Keeping Lifecycle Email Compliant as Rules and Volume Grow
A practical look at what privacy and email compliance actually requires for lifecycle marketing, and where small teams most often get it wrong.
Lifecycle Email Conversion Benchmarks: What 'Good' Actually Means
Generic conversion benchmarks don't fit lifecycle email. Here's how to set a realistic target for onboarding, post-purchase, and win-back flows.
Writing an Onboarding Email Sequence New Users Actually Read
How to structure a post-signup nurture sequence around what a new user needs to do next, instead of a fixed schedule of feature announcements.
Four Safeguards That Catch Churn Risk Before It's Too Late
Churn prevention often fails quietly, not dramatically. Four production safeguards that catch at-risk customers before a cancellation request arrives.
The SEO Checklist for a Company That Isn't a Content Team
A practical checklist for improving organic search visibility when marketing is one or two people, with the mistakes that waste the most time.
Coordinating Lifecycle Messages Across Email, SMS, and In-App
A practical runbook for coordinating retention messages across email, SMS, and in-app so channels reinforce each other instead of competing.