Federal law prohibits telephone solicitations, including marketing text messages, before 8:00 a.m. or after 9:00 p.m. in the recipient's local time zone, under 47 C.F.R. § 64.1200(c)(1). Several states go further, most notably Florida, Oklahoma, and Maryland, which restrict sales calls and texts to 8:00 a.m. to 8:00 p.m. and cap contact frequency. This guide gives you the federal baseline, a state-by-state reference table, and practical scheduling rules for multi-timezone contact lists.
Disclaimer: This is general information, not legal advice. State telemarketing laws change frequently and interact with federal rules in complex ways. Have telecom counsel review your specific campaigns and calling windows.
The Federal Baseline: 8 a.m. to 9 p.m. Recipient Local Time
Under the FCC's rules implementing the Telephone Consumer Protection Act (TCPA), "no person or entity shall initiate any telephone solicitation to any residential telephone subscriber before the hour of 8 a.m. or after 9 p.m. (local time at the called party's location)" FCC calling-time rules, 47 CFR 64.1200(c)(1). The FCC has long treated text messages as "calls" under the TCPA, so marketing texts fall squarely inside these quiet hours.
Three details matter enormously in practice:
- It is the recipient's local time, not yours. A 9:30 p.m. send from your New York office to a contact in Los Angeles (6:30 p.m. their time) is compliant; the reverse is a violation.
- It covers solicitations. Purely informational or transactional messages to existing customers sit under different consent rules, but promotional content is firmly in scope.
- Violations are expensive. TCPA violations carry statutory damages commonly cited at $500 to $1,500 per message, and quiet-hours violations are among the most actively litigated claims TCPA quiet-hours litigation overview.
State Quiet Hours Reference Table
States may impose stricter windows than the federal 8-to-9 baseline. The table below reflects the most significant state overlays as of 2026. Treat "Federal default" states as 8:00 a.m.-9:00 p.m. recipient local time, and treat the listed states as requiring their stricter rule.
| State | Permitted solicitation window | Extra restrictions | Notes |
|---|---|---|---|
| Federal baseline (all states) | 8:00 a.m. to 9:00 p.m. recipient local time | None | 47 CFR § 64.1200(c)(1) |
| Florida | 8:00 a.m. to 8:00 p.m. (recipient's time zone) | Max 3 calls/texts per 24 hours on the same subject matter | Fla. Stat. § 501.616; amended 2021 (SB 1120) and 2023; covers calls, texts, and voicemail |
| Oklahoma | 8:00 a.m. to 8:00 p.m. | Max 3 calls per 24 hours; broad autodialer definition; registration and bonding requirements | Telephone Solicitation Act of 2022 (effective Nov. 1, 2022); $500 per violation, trebled if willful |
| Maryland | 8:00 a.m. to 8:00 p.m. commonly cited | Own written-consent and operational restrictions for calls, texts, voicemail under the Stop the Spam Calls Act | Compliance guides group MD with FL/OK on hours; verify current text with counsel state telemarketing law tracker |
| Washington | Federal 8 to 9 baseline applies; additional device rules | Restrictions on automatic dialing/announcing devices; registration in covered cases; own identity and termination rules | Check device-specific duties with counsel before dialing |
| All other states | 8:00 a.m. to 9:00 p.m. recipient local time | State DNC lists and mini-TCPA proposals continue to emerge | Default to the federal window and monitor state developments |
A practical warning: new state "mini-TCPA" bills appear every legislative session. West Virginia, Illinois, Georgia, and Missouri have all seen proposals with 8-to-8 windows or per-day contact caps in recent years. A table like this needs a quarterly review to stay reliable.
Why Quiet Hours Are a Scheduling Problem, Not Just a Policy
Knowing the rule is the easy part. Applying it across a 100,000-number list spanning four time zones is the hard part, and where most violations happen. The compliance failure is rarely intentional; it is a list with no timezone data being blasted at 8:30 p.m. Eastern, which is 5:30 p.m. Pacific (fine) and 7:30 p.m. Central (also fine)… . The real danger is the reverse: an 8:30 p.m. Pacific send hitting East Coast recipients at 11:30 p.m.
Build these controls into every campaign:
- Resolve recipient-local time per contact. Area code is a weak proxy, people keep numbers when they move. Use validated timezone data tied to the contact record, and treat unknown timezones conservatively (hold the message or use the narrowest overlapping window).
- Adopt a conservative house window. Many compliant senders use 9:00 a.m. to 8:00 p.m. recipient local time as their default, inside every U.S. rule at once, with margin for clock skew.
- Segment sends by timezone. Split the list into Eastern, Central, Mountain, and Pacific (plus Alaska/Hawaii) cohorts and schedule each cohort's send separately. Most bulk SMS platforms support timezone-based scheduling natively, see our bulk SMS API comparison.
- Respect the frequency caps. Florida and Oklahoma limit solicitations to three per 24 hours on the same subject matter, regardless of which number you send from. Centralize counting across all your sending numbers and vendors.
- Honor opt-outs immediately. Under the FCC's 2024 consent-revocation order, consumers may revoke consent through any reasonable means, and revocation must be honored within 10 business days. A STOP at 8:55 p.m. does not license one more 9:05 p.m. send.
Before any large send, run your list through bulk phone number validation workflow. Invalid and reassigned numbers are a separate liability category, and quiet-hours mistakes compound fast on dirty lists.
Quiet Hours for Transactional vs. Marketing Messages
The 8-to-9 (or 8-to-8) restriction targets telephone solicitations. Courts and the FCC distinguish these from purely informational messages, appointment reminders, delivery alerts, fraud warnings, which operate under different consent frameworks. But the line is thinner than it looks: add "and check out our weekend sale!" to a delivery notification and you have likely converted it into a solicitation subject to quiet hours.
The safe operating rule: if a message contains any promotional content whatsoever, schedule it inside quiet-hour-compliant windows. If it is purely transactional, you still benefit from daytime sending. Response rates and customer goodwill both favor it. Either way, keep your campaign registration honest about what each campaign sends; mixed content is also a 10DLC rejection trigger.
Frequently Asked Questions
Do SMS quiet hours apply on weekends and holidays?
Yes. The federal rule has no weekend or holiday exception for solicitations. Some senders voluntarily tighten further on Sunday mornings as a brand-safety practice, but the legal window is the same seven days a week.
What time zone counts if I don't know where the recipient lives?
You are still responsible. The rule is measured at the called party's location, so "we didn't know" is not a defense. Maintain timezone data per contact; for unknown locations, use a conservative window or suppress the send until resolved.
Does the 8 a.m. to 9 p.m. rule apply to texts I send manually one by one?
The rule targets telephone solicitations generally, and the FCC treats texts as calls. Manual one-to-one texts are far less likely to draw scrutiny than bulk sends, but the same legal framework applies, and bulk senders should assume full applicability.
Are Florida's 3-texts-per-day limits per phone number or per business?
Per the statute's structure, the limit applies to the seller/solicitor per consumer per 24-hour period on the same subject matter. Rotating through multiple sending numbers does not reset it.
Can a customer consent to receive texts outside quiet hours?
Prior express consent changes the analysis for many TCPA claims, but quiet-hours rules have been litigated aggressively even with consent in the picture. Do not treat consent as a blanket license for 2 a.m. promotional texts; consult counsel for your specific fact pattern.
How do I handle daylight saving transitions?
Schedule on recipient-local time computed at send time, not stored offsets. A contact record stamped "UTC-5" is wrong half the year in observing states. Resolve the timezone, then compute the offset fresh for each send.