Est. reading time: 9 minutes
Most brands learn their SMS program has a compliance problem when a demand letter arrives, and by then the exposure is already sitting in the send logs. The pattern we see in accounts is consistent. Quiet hours are switched on somewhere in the flow builder, campaigns get scheduled by hand against the marketer’s own clock, the signup disclosure was copied off another brand’s site two years ago, and nobody has confirmed that an opt-out typed into the helpdesk ever reaches the sending platform.
None of that surfaces in revenue reporting. SMS keeps returning well, the program keeps running, and the risk compounds one send at a time.
Three mechanisms drive most of the exposure (when you are allowed to send, what your consent record has to prove, and how fast an opt-out has to take effect). Each has a rule behind it, and each one fails in a predictable place in the stack.
What the quiet hours rule restricts, and whose clock it runs on
The rule lives at 47 CFR 64.1200. Paragraph (c)(1) bars any telephone solicitation to a residential telephone subscriber before 8 a.m. or after 9 p.m., measured by local time at the called party’s location. Paragraph (e) extends those restrictions to telemarketing calls and text messages sent to wireless numbers, which is how a rule written for call centers ended up governing your abandoned cart flow.
The same section contains an exemption most brands have never read. Paragraph (f)(15) defines a telephone solicitation and excludes any message sent to a person with that person’s prior express invitation or permission. On that reading, a marketing text to a subscriber who opted in falls outside the quiet hours restriction. It is a serious argument. It is also a defense you raise after your company has been named in a complaint, so it belongs in your legal file rather than in your sending policy.
The operational failure is smaller and more mundane. The window runs on the recipient’s clock, not yours. A campaign scheduled for 9 p.m. Eastern lands at 6 p.m. for a subscriber in California and at 3 p.m. in Hawaii, all of it inside the window, while the same send moved to 9 p.m. Pacific arrives at midnight for everyone on the East Coast.
Klaviyo’s quiet hours setting defaults to the recipient’s phone number area code for United States and Canadian numbers, with an optional state-level setting that applies stricter state rules automatically. The eastern time zone option is the conservative alternative and costs you sending hours in exchange. Both apply to flow messages, and quiet hours can be enabled or disabled on each individual SMS in a flow, which is how one message in a five-step sequence ends up as the exception nobody remembers making.
Two mechanics inside that setting change what you see in reporting. Quiet hours are evaluated at send time and are checked before Smart Sending, so a message held overnight can be skipped the following morning if the subscriber received something else in the meantime. Recipients held by quiet hours also sit in a Waiting queue, where they pause their journey through the flow, so every split, delay, and email downstream of that SMS waits with them.
The consent record that has to survive a challenge
Prior express written consent has a definition at 64.1200(f)(9), and it asks for more than a checkbox. The agreement must be in writing, bear the signature of the person called (an electronic or digital signature qualifies), clearly authorize the seller to deliver advertisements or telemarketing messages using an automatic telephone dialing system or an artificial or prerecorded voice, and include the phone number those messages go to. The disclosure has to be clear and conspicuous, and it has to tell the person they are not required to sign as a condition of purchasing anything.
That last requirement is where DTC signup flows break. A phone field on the checkout page that enrolls the shopper in marketing texts because they entered a number for delivery updates does not produce consent to marketing. A single checkbox covering email and SMS together has the same problem, and so does a disclosure that sits behind a link two clicks away from the field. Everything upstream of this, from popup design to list growth incentives, deserves its own treatment.
The practical move is to treat consent as an artifact you can produce on demand, per subscriber, eighteen months after the fact.
What to store at the moment of opt-in
- Record the timestamp and the source, distinguishing between a form, a keyword, a checkout field, and an import.
- Store the exact disclosure text that was displayed, versioned, so you can show what a subscriber saw on the day they signed up rather than what your form says today.
- Capture the page URL and form identifier, which matters as soon as a brand runs more than one popup.
- Keep the confirmation reply where you use a double opt-in, since that reply is the cleanest evidence in the file.
Then re-check the live forms after every theme update, app install, or popup migration. Disclosure language disappears quietly during those changes, and the gap only becomes visible when someone goes looking for the record of a subscriber who joined during the window it was missing.
Opt-outs move faster than your integrations
Paragraph (a)(10) is written broadly. A subscriber may revoke consent using any reasonable method, and the rule treats stop, quit, end, revoke, opt out, cancel, and unsubscribe as reasonable per se when sent in reply to a text. Where a reply uses other words, the sender must honor it as a valid revocation if a reasonable person would understand those words to convey that request. All revocation requests must be honored within a reasonable time, capped at ten business days from receipt, and no sender may designate an exclusive means of opting out.
Exact-match keywords are handled for you by the platform and the carriers. The failures happen around them. A reply reading “please stop texting me” gets stranded in the helpdesk. A subscriber opts out of a second vendor’s shipping notifications and the suppression never reaches the marketing platform. A historical CSV gets re-uploaded before a promotion and reinstates numbers that opted out months earlier. Under (a)(11), a revocation sent by voicemail or email creates a rebuttable presumption that consent was withdrawn, which means the burden lands on you to show it was not conveyed reasonably.
One confirmation message is permitted. Paragraph (a)(12) allows a single text that confirms the revocation, carries no marketing or promotional content, and is the only further message sent. Send it within five minutes and it is presumed to fall inside the subscriber’s prior consent. Take longer and you have to show the delay was reasonable.
One piece of the revocation rule is on hold. The FCC has waived, until January 31, 2027, the portion of 64.1200(a)(10) that would require a sender to treat a revocation made in reply to one type of informational message as applying to all future robocalls and robotexts from that sender on unrelated matters. The order granting that extension states that it does not alter the status quo for any other rule or ruling on revocation, so the ten business day deadline and the any-reasonable-method standard both stand.
The damages math behind the demand letters
The number driving this activity is not a regulator’s fine. It is the private right of action in the statute. Under 47 U.S.C. 227, subsection (b)(3) lets a plaintiff recover actual monetary loss or $500 per violation, whichever is greater, with discretion for a court to treble the award where it finds the violation willful or knowing. The quiet hours and do-not-call rules sit under subsection (c), whose private right of action requires more than one call within any twelve month period from the same entity and carries the same up to $500 figure and the same trebling.
Per violation means per message. Two messages a week to a subscriber for a year, multiplied across a certified class, produces a number most brands settle rather than test in front of a jury.
Subsection (c) also gives you something to build toward. It provides an affirmative defense where the defendant has established and implemented, with due care, reasonable practices and procedures to effectively prevent violations of those rules. That defense is documentary. A written sending policy, dated consent records, a suppression process someone owns, and evidence that all of it was applied are what let you show practices rather than describe them.
The SMS compliance checks worth running this week
- Pull your last ninety days of sends against recipient time zone. Any message delivered outside 8 a.m. to 9 p.m. local is worth understanding before someone else finds it.
- Confirm which quiet hours model your account uses and whether state-level rules are on. Then check each SMS in your live flows for an individual override.
- Open every live signup form as a shopper would. Verify the disclosure is adjacent to the field, that SMS consent is separate from email, and that the not-a-condition-of-purchase language is present.
- Reply to one of your own messages with plain language rather than a keyword. Something like “take me off this list” should suppress the number, and someone should own the queue where it lands.
- Trace one suppression from every inbound source to the sending platform. Helpdesk, second vendor, and manual list edits all count, and each is a place where an opt-out goes to die.
None of this is expensive. It is a few hours of auditing and a written policy against a per-message liability figure that scales with the size of your list, which is the wrong thing to be scaling. If you would rather have someone run that audit alongside your team, we can take a look at the program with you.










