REACH vs. Hindi: TCPA Consent Scope Battle Over SMS Quiet Hours

Picture this: it’s 9:03 p.m. and your phone lights up with a text from a brand you swear you opted into. You’re not mad exactly… but you’re also not thrilled. Now picture the same moment through the eyes of the brand’s compliance manager, who just felt their soul leave their body because they’ve heard of “quiet hours” lawsuits and they enjoy sleeping at night.

Welcome to the surprisingly spicy debate over the TCPA’s “quiet hours” rule for marketing messageswhere two camps are staring at the same legal text and seeing two very different things. On one side: business groups like the Ecommerce Innovation Alliance (EIA) and an organization called Responsible Enterprises Against Consumer Harassment (R.E.A.C.H.), arguing that if a consumer gave consent to receive marketing texts, the “quiet hours” restriction shouldn’t apply. On the other: plaintiffs’ attorney Jibrael Hindi and allies, arguing that consent can be limitedand “yes, text me” does not automatically mean “text me whenever your discount schedule gets lonely.”

This article breaks down what “quiet hours” actually are, why the consent language matters so much, how REACH and Hindi frame the fight, and what smart businesses can do nowbefore the FCC (or the courts) make the rules clearer… or messier.

What Are “SMS Quiet Hours,” Exactly?

The rule in plain English

The FCC’s “quiet hours” restriction lives in the federal telemarketing rules and says that telephone solicitations can’t be initiated to residential subscribers before 8 a.m. or after 9 p.m.local time at the called party’s location. In other words: don’t telemarket when people are likely eating breakfast, getting kids to bed, or trying to pretend they don’t have emails. That’s the baseline rule. (And yes, the phrase “called party’s location” is where the plot thickens.)

The definition that changes everything

Here’s the twist: the rules also define “telephone solicitation” as a call or message encouraging the purchase of goods or services, but it does not include a call or message sent to someone with that person’s prior express invitation or permission (or an established business relationship, or for nonprofits). So the entire fight becomes: When you have consent, are you still in “telephone solicitation” territoryor are you outside it?

That sounds nerdy until you realize it’s the difference between “we should’ve time-gated this campaign” and “we’re being sued because someone got a coupon after bedtime.”

Consent: The Most Overworked Word in Marketing Compliance

“Prior express invitation or permission” vs. “prior express written consent”

TCPA compliance often involves multiple layers of “consent,” and mixing them up is how businesses accidentally wander into legal quicksand.

• Prior express invitation or permission is tied to whether a message counts as a “telephone solicitation” under the rules. If a message is sent with prior express invitation or permission, it may be excluded from “telephone solicitation” for certain purposes.
• Prior express written consent is a more specific concept that shows up in telemarketing rules for certain autodialed or prerecorded telemarketing calls/texts. It typically requires a signed written agreement with clear disclosures and an identified seller and number.

Why does this matter? Because the EIA/REACH camp largely frames the “quiet hours” lawsuits as targeting messages that were already consented toand therefore shouldn’t be treated like prohibited “telephone solicitations” during quiet hours. Meanwhile, Hindi argues the relevant standard for quiet hours is invitation/permissionand that invitation/permission can be limited by time.

The “limited consent” idea: can someone say yes… but not at night?

Hindi’s argument leans on a common-sense (and common-law) idea: consent isn’t always unlimited. People can consent to some contact, but not all contact, or contact under certain conditions. That means “sure, send me promos” might not automatically include “send them at 9:45 p.m.” unless the consumer specifically agreed to that timing or the overall context clearly implies it.

If you’ve ever told a friend “call me anytime” and then silently judged them for actually calling you at 6:00 a.m., congratulationsyou understand the emotional logic of limited consent. The legal question is whether the TCPA rules treat “general” permission as permission for messages outside 8 a.m.–9 p.m., or whether quiet hours remain a default boundary unless timing permission is explicit.

REACH and Hindi: Two Stories About the Same Rule

REACH’s framing: “abusive litigation” and a commonsense read

REACH positions itself as speaking for direct-to-consumer marketing and related industries and argues that quiet-hours lawsuits have become a high-volume litigation machinecostly for businesses and courts. Their core pitch: the FCC should adopt a “commonsense interpretation” that messages sent with prior express written consent fall outside the “telephone solicitation” bucket, meaning the quiet-hours restriction shouldn’t apply to those consented messages.

To put it bluntly, REACH is saying: “If someone opted in, this isn’t a cold solicitation. Stop treating it like one.” They also describe a wave of template-style lawsuits and ask the FCC to restore sanity to what they see as a system being exploited.

Hindi’s framing: the law is unsettled, and the FCC shouldn’t erase quiet hours

Hindi argues that the law is not as settled as petitioners suggestand that if it were, they wouldn’t need an FCC petition at all. He warns against a broad FCC ruling that would effectively override the idea that consumers can place limits on consent. He also argues that a sweeping waiver for wireless numbers would essentially wipe out quiet hours for most people, since a large share of “residential” use is now wireless.

Hindi’s version of the story is: “Quiet hours protect real privacy interests. Don’t let ‘general’ opt-ins become a free pass to ignore time boundaries.”

The Time Zone Problem: “Called Party’s Location” Sounds Simple Until It Isn’t

Why mobile phones make quiet hours weird

For a landline, “called party’s location” often aligns with the area code and the physical place the phone sits. For mobile phones, people travel. They move. They keep their numbers. They order tacos in Las Vegas with a Connecticut area code and then wonder why brands can’t read their mind.

EIA has argued that it can be practically impossible to know a mobile user’s real-time location reliably, especially if you don’t collect GPS data (and many companies don’t want to, for privacy and security reasons). So the petition asks for relief on how to determine local time fairly when the device could be anywhere.

NPA-NXX: the “area code” shortcutand the debate over how strong it should be

One proposed solution is using the phone number’s area code/prefix (often described as NPA-NXX) as a proxy for location. That’s not perfect, but it’s simple, scalable, and doesn’t require tracking someone’s GPS coordinates like you’re running a spy movie.

Hindi has suggested that if the FCC creates a presumption based on NPA-NXX, it should be rebuttablemeaning if a business has other reliable information (like a shipping address or a user-provided time zone), it shouldn’t be able to ignore it and hide behind the area code. In other words: “Use area code as a default, but don’t pretend you didn’t know better when you did.”

That’s the compliance tightrope: businesses want a safe harbor that’s practical; consumers and plaintiffs’ counsel want to prevent a safe harbor from becoming a loophole big enough to drive a midnight marketing campaign through.

Why This Fight Got Even Hotter After McLaughlin v. McKesson

Even if the FCC issues guidance, a big question is how much courts must follow it in private TCPA lawsuits. A major recent Supreme Court decision, McLaughlin Chiropractic Associates, Inc. v. McKesson Corp. (June 20, 2025), held that district courts are not automatically bound to adopt FCC statutory interpretations under the Hobbs Act in enforcement proceedings; courts must interpret the TCPA using ordinary statutory interpretation principles while giving the agency’s view “appropriate respect.”

Translation: FCC guidance still mattersbut it may not be the universal “game over” button businesses hoped it would be. That reality makes the REACH vs. Hindi debate feel higher-stakes, because even with an FCC ruling, litigation may continue with courts weighing how persuasive the FCC’s reasoning is.

What Businesses Can Do Right Now (Before the FCC Settles It)

1) Make consent language specific without making it creepy

If your opt-in language is vague, you’re inviting someone else to write your story for you in court filings. Consider adding clear timing disclosures in plain English, such as:

• “By providing your number, you agree to receive recurring marketing texts. Message frequency varies.”
• “Messages may be sent using automated technology.”
• Timing clarity: “You may receive messages during daytime and evening hours.” (If you want to be bold, define a window.)
• “Reply STOP to opt out.”

Don’t try to “lawyer-proof” it with a paragraph that reads like a spaceship manual. The goal is clarity a reasonable consumer would understand.

2) Build a quiet-hours gate anyway (yes, even if you think you’re exempt)

Even if you believe consented texts are exempt from quiet hours, adding time gating is often cheaper than paying lawyers to debate it. Many brands already schedule campaigns by time zone, and modern platforms can do it with rules like:

• Primary: User-selected time zone or address-based time zone (shipping/billing), if collected and permitted.
• Secondary: Device-provided time zone (if your system legitimately has it, and privacy policies support it).
• Fallback: NPA-NXX area code mapping.
• Final fallback: default to a conservative sending window (e.g., late morning to early evening) when uncertain.

Think of it as “defensive driving” for compliance: you can be in the right and still end up with a costly crash.

3) Separate message types like your legal budget depends on it (because it does)

Transactional and informational messages (order updates, security alerts, appointment reminders) are not the same as marketing promotions. If you mix them in the same stream, you make it harder to prove what the consumer agreed to, what the purpose was, and why the timing was appropriate.

Best practice: label, log, and route messages by category. If litigation happens, you want clean recordsnot a soup of “your package shipped” and “FLASH SALE 🥳” served in the same bowl at 9:31 p.m.

4) Keep receipts: consent logs, disclosures, and suppression lists

Document:

• When and how consent was obtained (form version, language, timestamp).
• The phone number, the specific seller, and the source page or keyword (for lead gen flows).
• Opt-out requests and how quickly they’re honored.
• Time zone logic used at send time.

If your compliance program is solid, your best friend is a spreadsheet you never thought you’d love.

What Consumers Should Know (and How to Set Boundaries)

If you opt into texts and later decide you don’t want evening messages, you don’t have to suffer in silence. Use the tools you already have:

• Reply “STOP” to unsubscribe (for most legitimate programs).
• Use the brand’s preference center if available (frequency, categories, time windows).
• If a brand is ignoring opt-outs or sending suspicious spam, report through your carrier tools and relevant consumer channels.

Also: if a brand’s texts feel like a needy ex who discovered coupons, it’s okay to end the relationship.

Where This Could Land: A Few Plausible Outcomes

Outcome A: The FCC endorses the “consent exemption” theory

The FCC could clarify that when a consumer has given prior express invitation/permission (or written consent in a form that satisfies the rule’s requirements), messages are excluded from “telephone solicitation” and quiet hours don’t apply. That would strengthen defense argumentsthough after McLaughlin, some courts may still litigate the interpretation rather than rubber-stamp it.

Outcome B: A safe harbor for location using NPA-NXX (possibly rebuttable)

The FCC might offer a workable compliance standard: use NPA-NXX as a presumption of location when you lack better data, but make it rebuttable if you have reliable evidence the consumer is elsewhere. This aims to reward good-faith compliance while discouraging willful blindness.

Outcome C: The FCC punts and courts keep sorting it out case by case

The FCC could decide the issue is best handled through litigation and evolving precedent. That would likely mean continued forum-by-forum inconsistency and more incentives for both aggressive suits and aggressive defenses.

Conclusion: Don’t Text Like a Stranger, Don’t Litigate Like It’s a Hobby

The REACH vs. Hindi battle is really about one question: how far does consent go? Businesses want predictable rules that let them communicate with customers who asked to hear from them. Consumers want privacy boundaries that don’t vanish the moment they sign up for a discount. And everyone wants “called party’s location” to stop sounding like a riddle written by a time-traveling lawyer.

Until the FCC provides clearer directionor courts converge on a standardthe smartest approach is practical: tighten consent language, implement time-of-day controls, use defensible location logic, and keep detailed records. Because in a world where one text can trigger a lawsuit, compliance isn’t just a legal function. It’s customer experience with a seatbelt on.

Field Notes: of Real-World-Style Experiences Around Quiet Hours and Consent

Experience #1: The “We Meant Well” Flash Sale
A mid-sized retailer runs a “limited-time” promotion that starts at 9:00 p.m. Eastern and is scheduled as a single blast. The marketing team assumes it’s fine because everyone on the list opted in. The next week, the company gets a demand letter claiming the campaign hit phones after 9 p.m. local time in multiple time zones. What surprised the team wasn’t the complaintit was how messy their data was. Half the users had shipping addresses; some had only an email and phone. The vendor’s default time zone was set to “account time,” not “recipient time.” The fix was boring but effective: campaigns became time-zone segmented, and their platform rules were changed so any “unknown” time zone defaulted to daytime sends. Sales dipped slightly, but the compliance team stopped flinching every time Slack pinged after dinner.

Experience #2: The Consent Form That Tried Too Hard
Another brand rewrote its opt-in language after hearing about quiet-hours litigation. The first draft was basically a novel: it mentioned every statute, every possible message type, and every technology term anyone had ever feared. Conversion rates fell off a cliff because the form looked like a contract for renting a spaceship. The second draft went the other direction: simple, human, and specific. It clearly disclosed marketing intent, automated technology, opt-out keywords, and that messages may be sent across normal daytime and evening hours. They also added a preference center option for “daytime only.” This one didn’t just help legal defensibilityit reduced customer irritation, which meant fewer complaints overall. The takeaway: clarity beats cleverness, and nobody opts into a paragraph.

Experience #3: The Area Code Trap
A subscription service relied on NPA-NXX mapping for timing. Then they discovered their most engaged customers were also the most mobile: college students, traveling nurses, remote workers. Suddenly, “local time” was not “area code time.” They didn’t want GPS collection (privacy, cost, and user trust), so they added a simple setting in the user account: “Choose your time zone.” The opt-in checkbox included a sentence encouraging users to set preferences to receive messages at comfortable hours. Their quiet-hours risk dropped, and surprisingly, engagement improved because people felt in control. It wasn’t fancyit was respectful design.

Experience #4: The Vendor Contract Wake-Up Call
A brand assumed its SMS vendor handled compliance. After a complaint, they realized the contract didn’t clearly allocate responsibility for time-of-day controls, record retention, or how opt-out suppressions propagate across short codes and campaigns. The company updated vendor terms to require: documented consent capture, auditable logs, suppression list sync SLAs, and explicit time-zone handling rules. The brand also required quarterly compliance reports and test sends to confirm “STOP” works end-to-end. It was the least glamorous project of the yearand the one that probably saved them the most money.

Experience #5: The “U Up?” Moment That Changed a Policy
Sometimes it’s not a lawsuit that drives changeit’s embarrassment. A founder received their own company’s promo text at 9:12 p.m. while trying to put a toddler to sleep. The next morning, “quiet hours” became a priority not because of litigation, but because customer empathy finally hit home. They instituted a simple rule: no marketing texts outside 9 a.m.–8:30 p.m. recipient-local time, regardless of what the strict legal minimum might be. Their unsubscribe rate improved, complaints dropped, and the brand’s tone felt more considerate. In a crowded market, that kind of respect can become a competitive edgeone that doesn’t require a court to tell you to behave.