Contact Us

UK +44 (734) 008 7301

USA +1 (737) 395 8587

Contact Us

UK +44 (734) 008 7301

USA +1 (737) 395 8587

Salesforce SMS Compliance: Consent, Opt-Outs and Quiet Hours (US)

July 15, 2025

Get your 100 Free SMS Credits for your Salesforce Org

salesforce sms complaince

This is general information, not legal advice. These rules shift often, so check the date and run anything important past a lawyer.

Nobody reads SMS compliance for fun. You’re here because someone asked “wait, did we get consent?” or because a campaign is about to go out. So here’s the plain version, written for people who send texts from Salesforce.

Three rulebooks run at the same time. Federal and state law can get you sued. Carrier rules can get your messages blocked. And your own records decide whether you can prove you followed the first two. Most teams only think about one.

Two Myths to Drop First

CAN-SPAM doesn’t cover text messages. It’s an email law. Texts fall under the Telephone Consumer Protection Act (the TCPA) and a growing pile of state laws. If a guide tells you to add CAN-SPAM-style footers to your texts, it’s mixing up channels.

The “one-to-one consent” rule is dead. You may have read that you’d need separate consent for every individual seller. The Eleventh Circuit struck that rule down in January 2025, right before it took effect. What remains is the older requirement: marketing texts sent with automated tools need prior express written consent.

Consent: What to Collect, What to Store

“Written” doesn’t mean paper. A person clearly agrees to get marketing texts from you at that number, and the wording around the checkbox or reply makes plain what they’re agreeing to. Under the federal E-SIGN Act (15 U.S.C. § 7001), an electronic action—like checking an un-checked box or replying “YES” via text—legally satisfies the “written signature” requirement for Prior Express Written Consent.

What doesn’t count:

  • A lead sitting in Salesforce.
  • An email opt-in.
  • A purchased list.

Is double opt-in required? No. Does it help? A lot. The confirmation text shows a real person with that phone said yes. Carriers also expect that first message to carry the basics: who you are, what you’ll send, how often, HELP and STOP instructions, and a “message and data rates may apply” line.

For each contact, store:

  • consent status
  • date and time
  • source (which form, keyword or QR campaign)
  • the number
  • the exact wording shown, or a version ID for it

That last item is the one people skip. When someone claims they never agreed, a ticked checkbox doesn’t show what the checkbox said.

Keep consent records for four years. Under the federal statute of limitations (28 U.S.C. § 1658(a)), consumers have up to four years to file a TCPA claim. If you cannot produce the exact timestamp and opt-in text audit trail from four years ago, you lose the case automatically.

Opt-outs: The Part That’s Changing Right Now

Here’s the timeline, because most guides get it jumbled.

Since April 11, 2025, you must honor an opt-out within a reasonable time, never more than 10 business days. Any reasonable method counts: a reply, an email, a call.

The “revoke all” piece got delayed twice, first to April 2026 and then to January 31, 2027.

Then the FCC rewrote it. It adopted a new order on September 30, 2026, It adopted a new order on September 30, 2026, and published it on October 26. With the FCC’s updated consent-revocation rules (FCC 26-67) taking full effect on November 25, 2026, here is exactly what changes for your operational strategy: 

  • Marketing opt-outs are broad. If someone opts out in response to a marketing text, that covers all your marketing texts, not just that campaign.
  • Informational texts can be narrower. An opt-out from, say, payment reminders can apply just to that category. Appointment reminders or fraud alerts don’t have to stop with it.
  • You can pick your opt-out method. You may designate a reply keyword, or a website or phone number you run, as the exclusive way to opt out. You must disclose it clearly in each text. For texts, one standard word like “Reply STOP to opt out” does the job.
  • But you must accept all seven words. Stop, quit, end, revoke, opt out, cancel, unsubscribe.
  • No designated method? Honor every reasonable way.
  • The 10-business-day ceiling stays. The FCC is also asking whether to shorten it (seven days is floated) and whether to require two-way texting. Comments are due on the same November 25.

What this means for a Salesforce org:

  1. Build one gate. The classic failure: someone opts out, the contact record updates, and a list-view send, an Apex job or a second tool still texts them. Every send path should read the same status field.
  2. Consider separate marketing and service statuses. The new category split makes that useful. It’s a design suggestion, not a legal requirement.
  3. Give your team a one-click way to record an opt-out. Opt-outs also arrive as emails to support or voicemail. A button or Flow on the contact record beats a Slack message that nobody acts on.
  4. Don’t plan around ten days. STOP replies should flip the status within seconds. Ten days is the legal ceiling for the slow cases.
  5. Send one confirmation text. No marketing in it. Then go quiet.

Your own opt-out wording matters too: see the opt-out text message examples.

When You’re Allowed to Send

Federal rules say 8 a.m. to 9 p.m. in the recipient’s local time. There’s an open fight over whether that window even applies to texts sent with consent. The FCC asked for comment in March 2025 and, as of May 2026, hadn’t ruled, and plaintiffs keep filing quiet-hours suits meanwhile.

Some states are stricter:

  • Florida: 8 a.m. to 8 p.m., and no more than three texts in 24 hours on the same subject.
  • Oregon: 8 a.m. to 8 p.m. for texts too, since January 1, 2026.
  • Texas: The Ecommerce Innovation Alliance successfully settled its federal lawsuit against the State of Texas on November 6, 2025. The resulting official state guidance explicitly confirms that brands texting customers via prior, affirmative consent are exempt from telemarketer registration statements and security bonds. Maintain documented consent to completely eliminate state-level enforcement risks.

A window of 9 a.m. to 8 p.m. local time (noon to 8 on Sundays) sits inside all of that. I only checked these states. Check yours.

One Salesforce headache: contacts have no standard time zone field. People move, and area codes lie. Capture a ZIP or state at signup and derive the zone from that.

What a Violation Can Cost

Under the TCPA, a person can sue for $500 per message, and a court can raise that up to three times ($1,500) for willful violations. Florida mirrors that structure. These figures multiply across a list, which is why the “$500,000 for one campaign” stories exist. Treat the numbers as a reason for care, not a scare tactic. 

Carriers are a Separate Rulebook

Carriers don’t care what your lawyer thinks. In the US, texting from standard 10-digit local numbers needs registration (A2P 10DLC). Per Twilio’s docs, unregistered traffic gets blocked whatever the volume. Registration is not consent. You need both.

A Pre-Launch Test That Takes Ten Minutes

From your own phone:

  1. Opt-in, and check the consent record and timestamp.
  2. Send a test from a list view and from a Flow.
  3. Reply STOP. Does the status flip within seconds?
  4. Send again from both paths. Did both get blocked?
  5. Reply START or YES to rejoin. Does it flip back?
  6. Email support asking them to stop. Can your team record that without calling a developer?

If step 4 fails, you’ve found your problem before a customer did.

Where Message Blink Fits

No software tool can replace legal counsel, but your CRM setup decides whether your team actually follows the rules. Message Blink is built natively on Salesforce to support your compliance workflow: it logs opt-in timestamps directly on Lead and Contact records, flips your opt-out checkbox automatically the second someone replies STOP (or any of the seven standard opt-out keywords), and lets you gate automated sends behind consent and time-zone checks in Flow.
 
If you want to run the ten-minute pre-launch compliance test above in a sandbox, you can:-
 

Post Tags :

Share :

Table of Content

Frequently Asked Questions