TCPA Quiet Hours: When You're Legally Allowed to Text Customers

It's 6:30am. Your "spring tune-up" text blast goes out to 400 past customers. By 8am, three people have replied STOP, one has replied something unprintable, and one has filed a complaint with their carrier. Your texting number is now flagged. All because the campaign went out 90 minutes too early. Quiet hours aren't a technicality — they're the line between a campaign that books jobs and one that burns your number.

This is part of Pillar A: Capture Every Lead — the legal companion to the complete missed-call text-back setup guide. This is general information, not legal advice. Texting law is real law with real penalties; when in doubt, talk to an attorney who knows the TCPA.

The core rule: 8am to 9pm, recipient's local time

The TCPA (Telephone Consumer Protection Act) restricts marketing texts to 8:00am–9:00pm in the recipient's local time zone. Three parts of that sentence matter:

• Marketing texts. The quiet-hours rule targets promotional messages — campaigns, offers, tune-up blasts. Purely informational/service messages (appointment confirmations, "your tech is en route") live under different consent rules, though carriers increasingly enforce quiet hours on everything automated.
• 8am–9pm. Not your 8am — theirs. If your shop is in Tennessee and a past customer moved to California, their 8am is your 10am.
• Recipient's local time. Your texting tool should handle timezone-aware scheduling — verify that it does before you schedule a multi-timezone campaign. If it doesn't, segment by area code or state.

What counts as consent (the part that actually protects you)

Quiet hours are only half the TCPA. The other half is consent — and this is where contractors usually get confused:

• Conversational/service texts: a customer who called you, booked service, or texted you first has given implied consent for related messages. Your missed-call text-back replying to someone who just called you? That's a conversation they started. Appointment reminders for a booked job? Expected.
• Marketing texts: tune-up campaigns, win-back blasts, promotional offers — these need prior express consent. In practice for contractors: the customer gave you their number during a service relationship (booking, invoice, website form with a consent checkbox). A number you got from a list broker or scraped from somewhere is not consent.
• The gray zone: the annual check-in text to a past customer. It's arguably relationship-based, but it reads like marketing. Treat it as marketing: only send to customers with a real service history, include opt-out language, keep it inside quiet hours, and honor every STOP instantly.

State variations: where federal law isn't the whole story

Several states have their own telemarketing/texting laws that go further than the TCPA — different quiet hours, additional consent requirements, or private rights of action that make violations expensive. Florida, Oklahoma, and others have been particularly active. The practical takeaway for a contractor:

• Know your state's rules if you text customers across state lines or operate near a border. Your texting tool's compliance docs often summarize state variations.
• Default to the strictest rule that applies to your list. If one state on your list requires stricter consent, apply it to everyone — simpler and safer.
• This post doesn't track every state law — they change. Your tool's compliance resources and a telecom attorney are the current sources of truth.

The practical setup: scheduling that stays compliant

Theory is nice; here's the actual configuration:

• Campaign sends: 9am–5pm recipient local time. Give yourself margin inside the 8am–9pm window. Nothing good happens at 8:02am that couldn't wait until 9.
• Automated responses: always on. Missed-call text-backs, booking confirmations, and reply handling are conversational — they fire when the customer acts, at any hour. The customer who calls at 11pm wants the 11pm text.
• Opt-out language in every first automated text. "Reply STOP to opt out." Non-negotiable.
• STOP handling: automatic and instant. Your tool must process opt-outs without human intervention. Test it: text STOP from your own cell and confirm you're suppressed.
• Keep consent records. Where did each number come from? Your CRM or texting tool should track opt-in source. If you can't prove consent, you don't have it.

The five violations contractors actually commit

• The 6am blast. Scheduling a campaign "for the morning" and having it go at 6am. Fix: schedule for 9am+ local.
• Texting the old list. Blasting everyone who's ever been in the CRM, including people from 2019 who never opted in. Fix: only text contacts with a documented service relationship or explicit opt-in.
• Ignoring STOPs. Usually a tool misconfiguration — the opt-out keyword isn't wired to suppress. Fix: test it monthly.
• No opt-out language. "We forgot to include it." Fix: it's in every template in this blog series. Use the templates.
• Assuming "they're my customer" = "I can text anything." Being a past customer supports service messages, not unlimited marketing. Fix: treat campaigns as marketing and get it right.

Already been texting wrong? The cleanup checklist

If this post made you realize your past campaigns weren't fully compliant, don't panic — fix it forward:

• Audit your last 90 days of campaigns. Pull the send logs: what time did they go out, in whose timezone, and did every first text include opt-out language? Note every gap honestly.
• Suppress anyone who opted out — retroactively. Search your replies for STOP, "stop texting me," "take me off," and every misspelling. Make sure every one of those numbers is suppressed in your tool today, not just going forward.
• Rebuild your list from provable consent. Going forward, only campaign to contacts with a documented source: service history, website form opt-in, or written consent. Archive the rest — a smaller compliant list outperforms a big risky one.
• Document the fix. Write down what changed and when: the new send window, the timezone handling, the opt-out testing cadence. If a question ever comes up, "here's our compliance process" is a very different conversation than "we didn't have one."

None of this is legal advice — but "we found the gap and fixed it" is always the right posture. And once the cleanup is done, you're texting from a foundation that can't get you in trouble.

Related guides in this series

The setup this protects: the complete missed-call text-back guide (Pillar A). The registration prerequisite: the 10DLC walkthrough. When texts don't arrive at all, the deliverability troubleshooting guide.

The done-for-you version

This post is System 1 from the Leveraged Owner Starter Pack — the done-for-you version with the full compliance checklist, every script with opt-out language built in, and screen-by-screen setup instructions for all 8 systems.

This post is general information about texting regulations, not legal advice. Regulations change — verify current requirements with your texting tool's compliance docs or a telecom attorney. No industry statistics were used.

Keep building your systems

Related guides from the Leveraged Owner blog: