TCPA Calling Hours (8am–9pm) and Texting

Who This Is For / Who It Is Not For

Who this is for: US businesses, compliance owners, marketing ops, and product teams that send or enable A2P SMS and need practical registration, consent, or troubleshooting guidance tied to 10DLC/TCR and TCPA concepts.

Who this is not for: Readers seeking invented fine amounts, guaranteed approval rates, or universal throughput figures; purely P2P consumer texting with no application layer; teams outside US A2P rules who need only foreign-regulator advice.

Short answer: Under 47 CFR § 64.1200(c)(1), telephone solicitations to residential subscribers may not be made before 8:00 a.m. or after 9:00 p.m. local time at the called party’s location. The rule is written for telephone solicitations—not as a standalone “SMS hours” statute. Whether your texts are treated like covered solicitations is fact-specific; many businesses still adopt 8am–9pm recipient-local policies as a risk control and must check stricter state rules.

Definitions

What the Federal Rule Says

§ 64.1200(c)(1) restricts initiating telephone solicitations to residential telephone subscribers outside the 8:00 a.m.–9:00 p.m. window, measured in the called party’s local time—not the caller’s headquarters time zone.

Key ideas:

• Telephone solicitation is a defined concept in the TCPA/FCC framework (generally purchase/rental/investment pitches, with exclusions such as prior express invitation/permission or established business relationship contexts as defined in the rules). Read the current definitions in § 64.1200 rather than marketing slang.
• Residential subscribers are the protected class named in this paragraph.
• Local time of the called party drives compliance—area-code heuristics help but fail after number portability; better to store timezone or postal locality when possible.

Use Cornell LII or the eCFR Subpart L for the living text.

Do Calling Hours Apply to SMS?

The regulatory text of (c)(1) addresses telephone solicitations, historically voiced around calls. Businesses and litigants sometimes dispute how timing theories apply to texts. This article does not invent a bright-line FCC “SMS must follow 8–9” sentence that is not clearly universal.

Practical risk management many programs use (policy choice—validate with counsel):

• Apply recipient-local quiet hours to marketing texts similar to voice solicitations
• Allow transactional/care messages under separate rules agreed with counsel (appointment reminders may be treated differently than promo blasts)
• Log timezone logic for audits
• Review state telemarketing laws that may impose earlier evening cutoffs or other limits

Building a Send-Time Control

Common Operational Mistakes

• Using company HQ time for a national list
• Assuming area code = timezone after porting
• Treating STOP compliance as a substitute for hour restrictions
• Sending “flash sale” texts at 6 a.m. local because the batch job started in UTC
• Ignoring state-level rules because federal 9 p.m. “felt fine”

Relationship to 10DLC Registration

Quiet hours are a TCPA/state timing issue. TCR/10DLC registration does not set your clock. You can have an approved Campaign and still create timing risk with off-hours marketing blasts.

Consent still comes first—see consent evidence trail and PEWC/opt-in drafts in this series. Tools on MyTCRPlus help with registration packaging, not courtroom timing strategy.

Examples (Illustrative Only)

• A national retailer queues promo voice calls using area-code timezone tables with a 30-minute buffer inside 8–9—still verify ported numbers.
• A clinic sends appointment reminders at 7:30 a.m. local under a counsel-approved informational policy separate from solicitation dialers.
• A lead-gen SMS tool blocks marketing robotexts outside 8–9 recipient-local by default; transactional OTP may use a different policy.

These stories are patterns, not safe harbors. Configure systems explicitly; do not rely on “everyone does 8–9 for SMS” folklore without counsel sign-off.

Documentation for Audits

Keep:

• Policy PDF stating windows by message class and state overlays
• System screenshots of timezone logic
• Change log when windows update after FR/state law changes
• Exception approvals (rare) with legal sign-off

Tie this file set to your broader TCPA consent program so timing and consent evidence live together.

Operating Model and RACI

Treat compliance as an operating system. Assign owners who remain accountable after launch:

When ownership is ambiguous, shadow IT sending tools appear and registered Campaigns drift from production copy. Reconfirm the RACI every quarter and after any CSP migration. Document escalation contacts for rejection codes and who may edit live templates during incidents.

Evidence Binder and Audit Readiness

Maintain a living binder with Brand submission payloads or console screenshots (secrets redacted); formation and EIN documents used during verification; dated archives of website, privacy policy, and SMS terms URLs; opt-in journey screenshots or recordings; Campaign description, message_flow, and versioned samples; CSP approval or rejection emails and reason codes; STOP and HELP response templates; and monthly exports of opt-out volume and complaint tags. These artifacts accelerate CSP remediations and support legal holds. Align retention with counsel because message logs are frequently discoverable. Index the binder by Campaign ID so on-call staff can find evidence in minutes.

Technical Controls Matrix

Engineering should treat Campaign-not-active as a hard failure, not a warning. Pair controls with runbooks that name the first three debugging steps for the most common CSP error codes.

Governance Cadence

Weekly: deliverability and error-code review; spot-check Brand identification and STOP language on random outbound messages. Monthly: consent QA for every new lead source; confirm privacy and SMS URLs still load without login. Quarterly: full Campaign-to-production alignment; refresh training; read the CSP 10DLC changelog end to end. Annually: reconfirm legal name, tax ID, and authorized representatives; renew vendor diligence. Publish a one-page leadership scorecard covering share of traffic on registered Campaigns, opt-out rate, open remediations, and time-to-suppress after STOP.

Vendor and ISV Diligence

If an agency, ATS, EHR, CRM, or ISV sends on your behalf, contract for your organization as Brand of record unless a deliberate reseller model applies; notice within an agreed window of Campaign rejection or suspension; shared dashboards or weekly status exports; STOP propagation into your system of record within minutes; prohibition on mixing unrelated customers onto your Campaign; and an annual security and compliance questionnaire. Many filtering events originate in reseller infrastructure. Diligence is cheaper than silent non-delivery during peak season. Keep a vendor inventory that lists every system capable of emitting SMS.

Legal Overlay (Not Legal Advice)

Registration and consent are related but distinct. An approved Campaign does not prove TCPA consent for a particular send; perfect consent records do not move unregistered traffic through carrier blocks. Coordinate with counsel on when prior express written consent is required, how revocation must be honored under 47 CFR section 64.1200 and related FCC guidance, which state mini-TCPA rules apply to your footprint, retention periods for consent artifacts, and vendor liability terms. Do not invent statutory penalty figures in training decks—cite primary sources and counsel memos instead. Revisit the overlay whenever marketing launches a new list source or message purpose.

Soft CTA

Prepare Brand packets, public SMS disclosures, and pre-submission diagnostics with MyTCRPlus tools at https://mytcrplus.com/tools/ and related microsite options. They help you organize evidence for your CSP—they do not guarantee approval, throughput, or legal compliance. Pair preparation with the step-by-step TCR registration guide at https://mytcrplus.com/how-to-register-with-tcr-the-complete-step-by-step-process-for-10dlc/ and troubleshooting pages for unregistered traffic blocks when deliverability collapses.

Change-Control Playbook

When templates, vendors, or CSP rules change: log the source URL and timestamp; classify impact across Brand, Campaign, consent UX, billing, and API; freeze related sends if resubmission is likely; assign one incident owner with a clear due date; notify support and marketing with non-speculative language; retest major US carriers after the fix; and write a short postmortem that updates the runbook. Controlled change beats reactive copy edits during an outage. Store playbook outcomes beside the evidence binder so audits show both prevention and response.

Launch and Scale Checklist

Do not skip the smoke test. A Campaign can show approved while a single MNO still has not provisioned the share, producing carrier-specific failures that look like random filtering to marketers.

Decision Framework Recap

1. Confirm you are sending US A2P over local 10DLC (vs toll-free or short code).
2. Map each template to marketing or operational purpose.
3. Assemble accurate Brand identity and public website evidence.
4. Write Campaign narratives and samples that match production truth.
5. Submit through your CSP and wait for Brand eligibility before Campaign create.
6. Attach numbers only after Campaign approval and provisioning.
7. Enforce STOP globally and monitor error codes.
8. Audit consent artifacts and sample drift on a fixed calendar.
9. Escalate CSP reason codes with evidence—not guesses.
10. Keep TCPA counsel in the loop for new message purposes.

This framework applies whether you run healthcare reminders, staffing shift fills, nonprofit fundraising, or retail promotions.

Operating Model and RACI (continued 10)

Treat compliance as an operating system. Assign owners who remain accountable after launch:

When ownership is ambiguous, shadow IT sending tools appear and registered Campaigns drift from production copy. Reconfirm the RACI every quarter and after any CSP migration. Document escalation contacts for rejection codes and who may edit live templates during incidents.

Evidence Binder and Audit Readiness (continued 11)

Maintain a living binder with Brand submission payloads or console screenshots (secrets redacted); formation and EIN documents used during verification; dated archives of website, privacy policy, and SMS terms URLs; opt-in journey screenshots or recordings; Campaign description, message_flow, and versioned samples; CSP approval or rejection emails and reason codes; STOP and HELP response templates; and monthly exports of opt-out volume and complaint tags. These artifacts accelerate CSP remediations and support legal holds. Align retention with counsel because message logs are frequently discoverable. Index the binder by Campaign ID so on-call staff can find evidence in minutes.

Technical Controls Matrix (continued 12)

Engineering should treat Campaign-not-active as a hard failure, not a warning. Pair controls with runbooks that name the first three debugging steps for the most common CSP error codes.

Governance Cadence (continued 13)

Weekly: deliverability and error-code review; spot-check Brand identification and STOP language on random outbound messages. Monthly: consent QA for every new lead source; confirm privacy and SMS URLs still load without login. Quarterly: full Campaign-to-production alignment; refresh training; read the CSP 10DLC changelog end to end. Annually: reconfirm legal name, tax ID, and authorized representatives; renew vendor diligence. Publish a one-page leadership scorecard covering share of traffic on registered Campaigns, opt-out rate, open remediations, and time-to-suppress after STOP.

FAQ

Is it illegal to call at 9:30 p.m. local?

Initiating a telephone solicitation to a residential subscriber after 9:00 p.m. local (or before 8:00 a.m.) conflicts with § 64.1200(c)(1). Non-solicitation calls may fall outside that paragraph—classify with counsel.

Does 9:00 p.m. mean I can start a call at 8:59?

The rule prohibits initiating outside the window. Do not cut it close; systems should use inclusive safe buffers.

What about texts at 10 p.m.?

Treat marketing texts as high scrutiny; adopt conservative quiet hours and confirm with counsel whether additional theories apply. Do not claim a universal SMS exemption from all timing risk.

Whose clock if the customer travels?

Best efforts using the number’s associated locale/preference; document your method. Perfect knowledge is hard—policies and counsel guidance matter.

Do nonprofits get different hours?

Consent and solicitation definitions include specialized provisions elsewhere in § 64.1200; do not assume a blanket hours exemption without reading the rule with counsel.

Key Takeaways

• Meet both carrier registration duties and consent/legal duties—neither replaces the other.
• Keep Brand identity, website evidence, Campaign samples, and production traffic aligned.
• Document who messages are for and how consumers opted in; honor STOP quickly.
• Use CSP reason codes and primary sources when remediating—not rumor threads.
• Avoid inventing fees, fines, or throughput guarantees in policies or marketing.
• Audit quarterly for consent drift, template drift, and vendor sprawl.
• Escalate legally sensitive launches to qualified counsel.
• MyTCRPlus tools can help organize evidence; they do not guarantee approval or delivery.

Disclaimer

This article is for informational purposes only and is not legal advice. FCC rules, state laws, and case law change. Confirm calling and texting hour policies with qualified counsel before setting production windows.