TCPA Consent and Quiet-Hours Rules for Executive Assistant Scheduling

TCPA Consent and Quiet-Hours Rules for Executive Assistant Scheduling

by ExecutiveAssistantAgency Editorial Team · 7 min read

How TCPA consent, opt-out, identification, and calling-hour rules apply when executive assistants confirm meetings by text or phone.

In this article
  1. Scheduling messages are a regulated channel
  2. Separate informational messages from marketing
  3. Consent must be specific and recorded
  4. Autodialed and prerecorded calls have stricter rules
  5. Honor quiet hours and identification duties
  6. Revocation must be easy and fast
  7. Vendor platforms do not transfer the risk
  8. A practical policy for an executive office
  9. Records, audits, and escalation
  10. Conclusion

Scheduling messages are a regulated channel

An executive assistant confirms meetings by text more often than by any other channel. A quick message can move a board call, remind a guest about parking, or ask a vendor to shift a delivery. The convenience hides a legal question: does the recipient want these messages, and does the sender have permission to automate them? The Telephone Consumer Protection Act applies to calls and texts, not just to mass marketing campaigns.

The TCPA is enforced by the Federal Communications Commission and through private lawsuits. Statutory damages are set per violation and rise for willful or knowing conduct, which makes a small scheduling list a meaningful risk. The FCC consumer guide explains the basic protections in plain language. An executive office does not need a marketing department to need a written consent process.

Separate informational messages from marketing

The TCPA treats informational and marketing messages differently. An informational text that confirms a meeting time or provides a location update is generally permitted with prior express consent when sent to a wireless number. A marketing text that promotes a service, a candidate, or an event requires prior express written consent with clear disclosures. The distinction depends on the content, not on the label the sender chooses.

An assistant who sends a one-off message from a personal phone is in a different position from a platform that sends automated reminders to hundreds of contacts. The first is still subject to the law, but the second carries more risk because the automation and the volume are visible. Write the rule by message type: confirmation, reminder, reschedule, and promotion. Then decide which types need written consent and which can rely on the existing relationship.

Consent should name the phone number, the sender, and the purpose. A checked box on an intake form that says "we may contact you" is weaker than a statement that the office may send appointment reminders to the number provided. Keep the date, the source, and the exact language the person agreed to. A screenshot of the form is better than a memory of the conversation.

For an executive assistant agency, consent may arrive through a client intake form, a candidate application, or a scheduling link. Each source should store the consent record with the contact. If a contact changes a phone number, the old consent does not automatically cover the new number. Treat a new number as a new consent event and log it separately. The 47 U.S.C. §227 text is the statutory starting point, while the FCC's rules add the operational detail.

Autodialed and prerecorded calls have stricter rules

The TCPA's automatic-dialing provisions apply to equipment that can store or produce telephone numbers and dial them without human intervention. The Supreme Court narrowed the definition in 2021, but the practical lesson for an executive office has not changed. If a platform dials or texts a list automatically, treat it as covered and confirm consent before the first message. A manual tap on a contact card is less risky than a campaign that runs from a spreadsheet.

Prerecorded or artificial-voice calls carry additional requirements, including consent and identification. Most executive scheduling does not need a recorded voice, so the simplest control is to avoid prerecorded reminders entirely. Use a human call, a text, or an email instead. When a vendor platform offers an automated voice reminder, ask whether the feature is enabled by default and turn it off unless the office has a documented consent process.

Honor quiet hours and identification duties

Telephone solicitations to residential subscribers are limited to the hours between 8 a.m. and 9 p.m. local time at the called party's location. The rule is a consumer protection, not a suggestion, and an assistant who calls a client on the West Coast from an East Coast office can violate it without intending to. Text messages should follow the same courtesy even where the calling-hour rule applies to voice calls, because a late-night buzz is still an interruption. A local-time field in the scheduling system prevents the most common mistake. When the recipient's location is unknown, use the most restrictive time zone in the contact list.

Marketing calls and texts must identify the caller and provide a callback number or address. The identification should be accurate and should not be buried in a long footer. If the office uses a scheduling platform, confirm that the sender name matches the office and that replies route to a monitored inbox. The 47 CFR §64.1200 rules set out the detailed restrictions, including the do-not-call provisions.

Revocation must be easy and fast

A recipient can revoke consent by any reasonable means, and the sender must honor the request. An opt-out message such as "stop" should be processed automatically, while a voicemail asking not to be texted again should be logged and applied by a person. The FCC has strengthened the revocation rules, and a slow response can turn a single complaint into a pattern. Treat every opt-out as effective for all non-emergency messages, not just the campaign that triggered it.

Keep a suppression list that is separate from the main contact list and check it before every send. If the office uses multiple tools, the suppression list must reach all of them. A client who opts out of reminders may still need a call about a same-day change, so define a narrow exception for urgent operational messages and document why it applies. Do not use that exception to keep sending routine updates.

Vendor platforms do not transfer the risk

A scheduling platform may promise TCPA compliance, but the office remains responsible for the consent it uploads and the messages it sends. Ask the vendor how it captures consent, how it handles opt-outs, and how quickly suppression takes effect. Request the audit log for a sample campaign. A vendor that cannot show the consent record is asking the client to carry the risk.

Review the contract for indemnity, data use, and message content approval. Confirm who owns the phone numbers and whether the vendor can use them for its own marketing. If the platform sends messages from a shared short code, the sender identity may not match the executive office. That mismatch can confuse recipients and weaken the consent record. The FCC's TCPA rules page is a useful reference when reviewing vendor claims.

A practical policy for an executive office

Write a one-page policy that covers the channels, the consent standard, the quiet hours, the opt-out process, and the escalation path. Name the person who approves new message templates and the person who reviews the suppression list each month. Keep the policy short enough for an assistant to use during a busy day. A long policy that no one reads is not a control.

Train new assistants on the difference between a confirmation and a promotion. Give them approved templates that include the sender identity and the opt-out instruction. Require a second review before any message is sent to a purchased list or a list assembled from a directory. Most violations begin with a well-meaning assistant trying to be helpful with a list that was never consented.

Records, audits, and escalation

Keep consent records, message logs, opt-out requests, and vendor reports for at least the period the office uses for other business records. A four-year retention period is common because TCPA claims can surface long after the campaign. Store the records by contact and by campaign so a single request can be answered without searching several systems. The records retention baseline offers a structure that can be adapted.

Run a quarterly sample of 20 messages and check the consent source, the content, the time sent, and the opt-out status. If a message fails, fix the template and the list before the next send. Escalate a legal threat or a regulator inquiry to counsel immediately, and preserve the relevant records. A calm, documented response is much stronger than a reconstructed one.

Conclusion

The TCPA does not ban scheduling texts, and most executive offices can use them safely. The requirement is a documented consent process, a respect for quiet hours, an easy opt-out, and a vendor that can prove what it sent. Those controls are ordinary operations work, not a legal project. An assistant who understands them can move quickly without creating a compliance problem that outlasts the meeting.

For help building a scheduling and communications workflow that fits an executive office, talk to our team. The goal is a system where a confirmation text is fast, welcome, and defensible. That combination is achievable with a short policy and a habit of recording consent at the point of contact. The policy should be reviewed when a new platform or a new state enters the picture.

★★★★★

“My EA handles everything from board prep to multi-city travel, and I finally have time to focus on the work that matters.”

Chief Executive Officer, Series B SaaS company