How Often Should a Business Send Appointment Reminders?

This article covers reminder frequency, channel selection, legal consent basics under the TCPA (47 U.S.C. 227) and CAN-SPAM Act (15 U.S.C. Chapter 103), message length, and opt-out handling for US service businesses. It does not cover:

• State-level rules. Several US states have additional requirements for automated communications. Florida (Fla. Stat. 501.059), Oklahoma (Okla. Stat. tit. 15, 756.1), and Washington (RCW 80.36.400) have statutes that interact with or go beyond the federal TCPA. This article addresses only the federal framework. Consult a qualified attorney for state-specific obligations.
• HIPAA-covered communications. If your business is a covered entity under the Health Insurance Portability and Accountability Act, appointment reminders may be subject to additional requirements under 45 C.F.R. Part 164, Subpart E. This article does not address health information rules and uses no medical or health examples.
• Specific booking or messaging software integrations. Dave by voolama does not ship with built-in connectors to named booking systems or SMS platforms. The workflow approach described here uses an API Call node to connect to any service with a REST API endpoint. Configuring that connection is specific to your chosen services and is outside the scope of this article.
• The evidentiary basis for the timing recommendations. The 48-to-72-hour and same-morning schedule reflects common practice in service business operations and is not derived from a single published study. The timing recommendations in this article are a practical starting point. If your business type or customer base suggests a different cadence, test and adjust.

Commercial interest disclosure: This article is published by voolama LLC, the company that builds and operates Dave by voolama. The workflow approach described in the final section runs on Dave.

For most service businesses, two reminders are the right number. One reminder sent 48 to 72 hours before the appointment gives the customer enough time to reschedule if something has come up. A second reminder sent the morning of the appointment serves as a same-day confirmation. Together, these two touches cover the gap between booking and arrival without overwhelming the customer.

A third reminder, sent one hour before the appointment, is reasonable in two situations: the appointment is long or high-value (a half-day consulting session, a multi-step service that requires preparation), or the customer has a history of late arrivals that creates problems for other bookings. Outside those situations, a third reminder is more likely to produce an opt-out than a confirmation.

For bookings made less than 24 hours before the appointment, the standard two-reminder sequence does not apply. A single reminder sent shortly after booking, confirming the time and location, is sufficient. Sending a 72-hour reminder for a booking that is only six hours away is confusing and looks like a system error.

A practical reminder schedule for a standard service booking:

• 72 hours before: First reminder. Confirm date, time, location, and include a reschedule or cancel link.
• Morning of: Second reminder. Short confirmation with address or call-in link and a single opt-out instruction.
• 1 hour before (optional): Third reminder, only for long or high-value appointments.
• Same-day booking: One reminder only, sent immediately after booking confirmation.

The three most common reminder channels for US service businesses are email, SMS (text message), and automated phone calls. Each has different legal requirements under federal law.

Text message (SMS): TCPA, 47 U.S.C. 227(b)(1)(A)

The Telephone Consumer Protection Act, 47 U.S.C. 227(b)(1)(A), prohibits sending automated text messages to a mobile number without prior express written consent. The FCC has implemented this requirement in 47 C.F.R. Part 64, Subpart L. Consent must be obtained before the first message is sent, must be in writing (which includes electronic records), and must clearly describe what the customer is consenting to receive. Collect consent at the time of booking, keep a dated record of it, and include opt-out instructions (such as "Reply STOP") in every message. If you are unsure whether your booking process captures valid consent under 47 C.F.R. 64.1200, consult a qualified attorney before sending automated texts.

Email: CAN-SPAM Act, 15 U.S.C. Chapter 103

Email reminders are governed by the CAN-SPAM Act, 15 U.S.C. Chapter 103, implemented by the FTC. Every commercial email must include a working unsubscribe mechanism and your physical mailing address. Appointment reminders are generally considered transactional rather than commercial messages under 16 C.F.R. 316.3, but if the reminder includes any promotional content, the full CAN-SPAM requirements apply. The FTC's compliance guide for the CAN-SPAM Act (linked in sources) explains the transactional-versus-commercial distinction in detail. Keep reminder emails free of promotional language to stay clearly on the transactional side.

Automated phone calls: TCPA, 47 U.S.C. 227(b)(1)(A) and (B)

Automated or pre-recorded phone calls to mobile numbers require prior written consent under the TCPA, 47 U.S.C. 227(b)(1)(A). Calls to landlines for appointment reminders may be permitted without prior consent under 47 U.S.C. 227(b)(1)(B) if they do not use an artificial or pre-recorded voice, but the rules are specific and have exceptions. Review the FCC's guidance (linked in sources) and consult an attorney if you have questions about your specific situation.

Personal phone calls

A staff member making a personal, non-automated phone call to confirm an appointment is not covered by the TCPA's automated-call rules under 47 U.S.C. 227. This is a practical option for high-value bookings or for customers who have opted out of automated reminders but where a confirmation is still important.

The most common mistake in appointment reminders is length. A reminder has one job: confirm the appointment details and give the customer one action to take. Every word beyond that reduces the chance the customer reads the important part.

For SMS reminders, aim for under 160 characters. A standard SMS segment is 160 characters under GSM-7 encoding, the default encoding used by most US carriers for English-language messages. Messages longer than 160 characters are split into multiple segments under the SMS concatenation standard (3GPP TS 23.040), which can arrive out of order on some carriers. A 160-character SMS reminder can contain the customer's name, the appointment date and time, the business name, and an opt-out instruction.

A hypothetical SMS reminder for a repair shop: "Hi Alex, your appliance pickup at Riverside Repair is Wed Nov 11 at 2pm. Reply STOP to unsubscribe." That is 97 characters, well within the single-segment limit.

For email reminders, five sentences or fewer. Use the subject line to carry the appointment date and time so the customer can see the key information without opening the message. The body confirms the details, gives a reschedule or cancel link, and includes the unsubscribe mechanism required by the CAN-SPAM Act, 15 U.S.C. Chapter 103.

What to leave out of every reminder:

• Promotional offers or upsells. These turn a transactional message into a commercial one under 16 C.F.R. 316.3 and trigger the full CAN-SPAM Act requirements.
• Lengthy policy text. Link to your cancellation policy rather than quoting it in full.
• Multiple calls to action. One action per message: confirm, reschedule, or cancel. Not all three.
• Apologies or hedging language. "We just wanted to remind you" wastes characters and sounds uncertain.

Opt-outs are not a failure. They are a signal that a customer prefers a different communication style, and honoring them promptly is both a legal requirement and good practice.

For text messages, the FCC requires that opt-out requests be honored promptly under 47 U.S.C. 227 and 47 C.F.R. 64.1200. For email, the CAN-SPAM Act, 15 U.S.C. Chapter 103, requires that unsubscribe requests be processed within 10 business days of receipt. Keep a dated record of every opt-out so the preference is respected if the customer books again. A customer who opted out of automated texts can still receive a personal phone call from a staff member.

Edge cases that benefit from a human decision before a reminder goes out:

• A customer who has cancelled or not shown up for the last two appointments. An automated reminder may not be the right first step; a personal call from a staff member may be more appropriate.
• A booking made less than two hours before the appointment. The standard reminder sequence does not apply, and sending a 72-hour reminder for a same-day booking looks like a system error.
• A customer whose contact details have changed since the last booking. Sending a reminder to an old number or email address wastes a message and may reach the wrong person.

A workflow in Dave by voolama (hellodave.ai) can handle these edge cases by routing them to a staff member's Task Inbox before the reminder goes out. The Task Inbox is accessible under Tasks in the sidebar. Pending tasks appear with an amber status badge. A staff member with the Admin or Use role can review the case, add a comment explaining their decision, and click Approve to send the standard reminder or Reject to skip it and handle the customer directly. Every decision is recorded in the audit log, which supports SOC 2 CC6.1 and GDPR Article 30 when those compliance modes are active in the tenant.

Dave by voolama is managed SaaS: voolama LLC operates and hosts the platform, so your team installs nothing and provisions no servers. Dave supports seven AI provider types and you bring your own API keys. Workflows are built in the visual Workflow Editor and can include ten node types: Start, End, User Interaction, Human Review, Agent Interaction, Agent Review, Routing, API Call, Information, and Safety.