The appointment reminder app that gets a reply.
An appointment reminder app has a narrower job than it looks. It is not there to tell clients something they already wrote down. It is there to get a decision out of them before the slot is lost: confirm, move it, or cancel early enough that someone else can take it. Every design choice follows from that, from the fields the reminder record needs to the hour the messages go out. Reminders are usually one part of a bigger booking flow, and if you are scoping the whole thing, our guide to a booking and scheduling app builder covers the calendar, services and staff side. This page stays on the reminder itself.
Below: the record a reminder needs, a cadence that survives contact with real clients, the difference between text, push and email, the US rules for reminder texts, what sending actually costs, and where the scheduling should live if you build your own.
See what the reminder record needsThe short version
Two touches, one reply, and a record that remembers consent.
Send a confirmation the moment the appointment is booked, a reminder a day or two before that asks for a reply, and a short same-day nudge. Let the client confirm, reschedule or cancel with one reply or one tap, and log which of those happened. Store consent per channel, the client's time zone and the outcome of every appointment, because those three things are what let you tell a no-show problem from a delivery problem. Text reaches clients who never installed anything; push is free but only reaches people with your app; email is the fallback. In the US, automated texts to mobile numbers need prior consent and an opt-out that works, and the FCC has written down exactly what that means.
The reminder record
What an appointment reminder app actually has to do.
Strip away the branding and every appointment reminder app, whether it is a client appointment reminder app for a salon or a patient reminder system for a clinic, runs the same loop. An appointment is created, one or more reminders are scheduled against it, each reminder goes out on a channel the client agreed to, the client responds or does not, and the appointment ends in a known state. The record that supports that loop needs more than a name and a time:
- The appointment: start time stored with the client's time zone, duration, service, provider and location
- The client: name, mobile number, email, and the language they want to be reminded in
- Consent per channel: whether they agreed to texts, push or email, when, and how you captured it
- The reminder plan: how many touches, how long before the start each one fires, and on which channel
- Delivery status per reminder: queued, sent, delivered, failed, and the reason if it failed
- The reply: confirmed, reschedule requested, cancelled, or no response, with a timestamp
- Opt-outs: a STOP or any other reasonable request to stop, honoured across every future appointment, not just this one
- The outcome: showed, late, cancelled in time, cancelled late, or no-show
The last two are the ones most small setups skip, and they are the ones that matter later. Opt-outs have to live on the client, not on the appointment, or the next booking texts someone who asked you to stop. Outcomes are the only way to know whether your reminders work: if no-shows stay flat while the confirmed rate climbs, the reminder is not the problem, the booking is.
The states an appointment moves through
Status should be a fixed set of states, not a notes field, so that "unconfirmed for tomorrow" is a list you can pull at 4 pm instead of a memory. This is the smallest set that still answers every question the front desk asks:
| State | What it means | What moves it on |
|---|---|---|
| Booked | Created by staff or by the client. The confirmation goes out now. | Reminder due, once the first offset in the plan arrives. |
| Reminder sent | A reminder went out and is waiting on a reply. | Confirmed, Reschedule requested, Cancelled, or No response at the deadline. |
| Confirmed | The client replied yes or tapped confirm. | Showed, or No-show if they still do not turn up. |
| Reschedule requested | The client asked to move it. The slot is not free yet. | Back to Booked with a new time, which re-plans every pending reminder. |
| Cancelled | The client cancelled, in time or late. Log which. | The slot is released, and a waitlist can be offered the time. |
| No response | The deadline passed with no reply. | A staff call, or treat it as unconfirmed and apply your overbooking policy. |
| Showed / No-show | Recorded at or after the start time by staff. | Nothing. This is the end state, and it feeds the no-show rate. |
Cadence
When to send appointment reminders.
There is no universal schedule, but there is a universal constraint: the reminder that asks for a decision has to land before your cancellation cutoff, or a cancellation frees nothing. Work backwards from that, and three touches fall out for most services.
At booking
Immediately
A confirmation with the date, time, place and how to change it. This is the message clients screenshot, and it is your record that the appointment existed if a late fee is ever disputed.
Before the cutoff
24 to 48 hours ahead
The reminder that asks for a reply. Send it earlier if your cancellation window is longer, because a cancellation that lands after the cutoff frees nothing. This one carries confirm, reschedule and cancel.
Same day
1 to 3 hours ahead
A short nudge with the address or the join link. No reply needed. Skip it for early morning appointments rather than sending it at 6 am.
Quiet hours and time zones
The FCC's telemarketing rules forbid solicitation calls before 8 am or after 9 pm in the called party's local time. An appointment reminder to your own client is not a solicitation, the rules exclude messages to people who gave permission or have an existing business relationship, but the window is still the right default for reminders, and it has to be computed in the client's time zone, not yours. A therapist in New York reminding a client who moved to Denver, or a tutor with students across Europe, gets this wrong by hours without noticing unless the record stores a time zone per client.
Match the cadence to the trade
The right offsets follow from how long the slot is and what a lost slot costs. A studio booking a four-hour session on a deposit wants the decision reminder several days out and a firm reschedule path, which is why a tattoo booking app treats the reminder as part of the deposit terms. A barbershop running 30-minute slots leans harder on the same-day nudge and a fast waitlist, the pattern a salon booking app is built around. A dental practice sits in between and folds the pre-visit instructions into the same-day message.
Text, push or email
Which reminder actually gets seen?
Most people searching for an appointment reminder text app have already decided on SMS, and for client-facing reminders that is usually right: it reaches a phone the client already carries without them installing anything. Push is the opposite trade. It costs nothing per message, but it only reaches clients who have your app installed and allowed notifications, which makes it the right channel for reminding your own staff, or for a business whose clients already live in its app. Email is cheap and holds detail, and it is the channel most likely to be read after the appointment.
| Channel | Reaches clients with nothing installed | Two-way reply | Cost per message | Consent | Where it fails |
|---|---|---|---|---|---|
| SMS | Yes | Yes, by replying C, R or STOP | $0.0083 per segment plus $0.0035 to $0.005 in carrier fees on Twilio, July 2026 pricing | Prior express consent for automated texts to mobile numbers | Unregistered senders, and long messages that split into extra paid segments |
| Push notification | No | Yes, with action buttons or a tap into the app | No carrier fee; the push provider's plan is the only cost | The OS permission prompt, which the client can decline | App deleted, notifications off, or a local reminder scheduled on a phone the client is not holding |
| Yes | Yes, through a link | Lowest of the three, no carrier fee | Transactional to your own clients; still honour unsubscribes | Read after the appointment, or filed under promotions | |
| Phone call by staff | Yes | Yes, live | Staff time | Live calls to your own clients are fine; a prerecorded voice needs consent | Voicemail, and it stops scaling past a few dozen a day |
The practical answer for most client-facing businesses is text for the reminder that asks for a reply, email for the booking confirmation with the detail in it, and push only once you are shipping an app your clients open anyway. Whatever the mix, the consent field in the record decides which of them a given client can receive, not a global setting.
The rules
The rules for appointment reminder texts.
Two US rule sets shape almost every decision above. The FCC's Telephone Consumer Protection Act rules, at 47 CFR 64.1200, govern automated calls and texts to mobile numbers, and the rule text treats texts as calls: paragraph (a)(9) says so outright, and (a)(10) spells out how consent for "calls or text messages" is revoked. HIPAA governs what a healthcare provider may say in a reminder. Neither is exotic, and both are easier to design in than to retrofit.
Consent and STOP
Under 47 CFR 64.1200(a)(1), an automated call or text to a mobile number needs the called party's prior express consent unless it is an emergency. Under (a)(10), the client can revoke that consent by any reasonable method: replying stop, quit, end, revoke, opt out, cancel or unsubscribe counts automatically, a reply in other words counts if a reasonable person would read it as a request to stop, and you cannot force clients to use one specific channel to opt out. Revocations must be honoured within a reasonable time, and never more than ten business days. Read 47 CFR 64.1200 on eCFR.
For an appointment reminder app that means three things. Capture consent at booking and store when and how. Treat any stop-like reply as an opt-out for the client, not just the appointment. And make the opt-out take effect immediately in your own system, even though the rule gives you slack.
The healthcare exemption is a good spec even if you never rely on it
Paragraph (a)(9)(iv) exempts certain messages from healthcare providers, including appointment and exam confirmations and reminders, from the consent requirement, but only when the message is free to the patient, does not count against their plan, and meets every one of these conditions. Read them as a checklist for any reminder text, medical or not:
- Sent only to the wireless number the patient gave you
- States the provider's name and contact information
- Limited to the permitted purposes: appointment and exam confirmations and reminders, wellness checkups, pre-registration and pre-operative instructions, lab results, post-discharge follow-up, prescription notifications, home healthcare instructions
- No marketing, and no billing, accounting or debt collection content
- 160 characters or less
- One message per day, and no more than three per week, per patient
- Tells the patient they can reply STOP, and the opt-out is honoured immediately
Because the free-to-the-patient condition is hard to guarantee, most practices get consent anyway and use the list as their message spec. It is a good one. The 160-character limit keeps you to a single SMS segment, the one-a-day cap kills the temptation to send five reminders, and the name-and-contact rule is what makes a client trust the message enough to reply.
HIPAA: say less in the message
The HIPAA Privacy Rule permits appointment reminders. HHS says so plainly in its FAQ on messages left for patients, with two caveats that translate directly into product rules: limit the information disclosed, and accommodate a patient's reasonable request to be contacted a different way or at a different place. In practice the reminder names the practice, the date and time, and how to respond, not the procedure or the diagnosis, and the client record has a preferred-contact field that the reminder plan actually reads.
What a compliant reminder text looks like
132 characters · one segment
Provider named, purpose only, a reply instruction, an opt-out, and room to spare under 160. Notice what is missing: the procedure, the price, and anything that reads as marketing. The reply keywords should be single letters that survive autocorrect, and the app should accept lowercase.
Sender registration
One more practical rule. In the US, sending application-driven texts from an ordinary 10-digit number means registering your business and your messaging use case with the carriers, known as A2P 10DLC. Twilio's pricing page notes that 10DLC senders pay registration onboarding fees on top of the per-message price. Plan for the registration before launch rather than after the first client says a text never arrived.
What it costs
Is there a free appointment reminder app?
For reminding yourself, yes: your phone's calendar does it, and a shared calendar invite reminds the client too if they accept it. For reminding clients by text at any volume, no, because every text costs money to send. Free tiers of booking tools usually include email reminders and cap or exclude SMS, or charge per text. That is less stinginess than pass-through. On Twilio's published US SMS pricing, current as of July 2026, an outbound SMS segment costs $0.0083 plus a carrier fee of $0.0035 to $0.005 depending on the network, a 10-digit number rents for $1.15 a month, and 10DLC registration fees come on top. Cheap per message, never zero.
Try it
What would the texts alone cost you?
Message costs only, at Twilio's published US long code rates as of July 2026, with the number rental included. Software, sender registration fees and anything a reminder tool charges are on top.
Text reminders per appointment
Outbound segments
400
Inbound replies
200
Per month
$8.03 to $10.13
That is $0.040 to $0.051 per appointment in messages, one segment each, across the carrier fees Twilio lists.
Free calendar reminders against a real reminder app
The message cost is rarely the expensive part. What you pay a reminder tool for is the scheduling, the reply handling and the compliance plumbing, and that is what separates the free options from the paid ones:
| Approach | Reminds the client | Text included | A reply changes the booking | Your cadence and fields | Cost |
|---|---|---|---|---|---|
| Calendar invite | Only if they accept the invite | No | No | Fixed | Free |
| Free tier of a booking tool | Yes, usually by email | Capped, or paid per text | Sometimes | The vendor's | Free until the cap |
| Paid reminder service | Yes | Yes | Yes | The vendor's, with settings | Per user or per message |
| Custom-built reminder app | Yes | Yes, through a provider you connect | Yes | Whatever your process needs | Build tool plus message costs |
Even the build-it-yourself row is not free. Newly is $25 a month before you have sent a single text, and the messages are billed by whichever provider you connect. The question is not whether reminders can be free, it is whether the tool you are paying for runs your cadence, your reply rules and your consent record, or its own.
Where the timer runs
On the phone or on a server: where the reminder waits.
If you build your own, the first architectural choice is where the reminder sits until it is time to send. There are three honest options, and they are not interchangeable.
A local notification on a phone
The app on a device asks the operating system to show a notification at a time. It works offline and needs no server, but it only fires on the phone that scheduled it, it knows nothing about a change made at the front desk, and Apple's local notification documentation keeps only the soonest 64 pending notifications per app and discards the rest. Right for reminding a solo provider about their own day. Wrong for reminding clients.
A scheduled push through a provider
Your server hands the push provider the message and a delivery time when the appointment is booked, then cancels and re-creates it if the time changes. OneSignal's create-notification API takes a send_after timestamp and has a cancel endpoint for exactly this, so no timer has to run on your own server. It reaches only clients who have your app installed.
A text through an SMS provider
The same idea with the message handed to an SMS API, either at send time by a job on your server or by scheduling through the provider. This is the channel for clients who installed nothing, and it brings consent capture, STOP handling and sender registration with it.
The 64-notification cap is from Apple's UIKit documentation for local notifications. The system keeps the soonest-firing 64 and discards the rest.
Whichever you pick, the reminder plan belongs in your database and the provider holds only the next pending send, so a reschedule updates one record and everything downstream follows. If you have not built with push before, start with the mechanics of push notifications in mobile apps before deciding how much of the reminder logic should live on the device.
When to build your own
Building an appointment reminder app that fits your process.
Most businesses should use the reminders built into whatever they book with, and only build when the tool cannot express their process: a cancellation window the vendor does not support, a reply that should trigger a waitlist, reminders in two languages, a consent record an auditor will ask for, or a client-facing app where the reminder is one screen of many. That gap is what Newly is for: describe the reminder record, the cadence and what a reply does, and it builds a real native app around your rules instead of the vendor's.
Know the boundaries before you describe it, because its documentation is specific. Push notifications go through OneSignal, using your own OneSignal account and your own Apple push key. The built-in backend has no background job queue and does not send email or SMS itself, so scheduled sends belong with the push provider or with a messaging service you connect and pay for separately, and you should not promise clients text reminders until you have watched one arrive on a real phone in your own testing. iOS builds upload to App Store Connect, where you finish the listing and submit for review yourself, and the current version produces no Android release builds. The price is $25 a month, with no free plan.
Spec it before you build it
Six decisions, all cheap to change on paper and expensive to change once clients are receiving messages:
- 1
Write the record
Every field in the list above, with the client's time zone and per-channel consent as required fields, not optional ones.
- 2
Fix the cadence
Two or three touches with offsets in hours before the start, computed in the client's time zone and clamped to 8 am to 9 pm.
- 3
Write the templates
Under 160 characters, provider named, purpose only, a reply instruction and STOP. Write the confirm, reschedule and cancel replies too.
- 4
Decide what a reply does
C confirms, R opens a reschedule path, and anything stop-like opts the client out everywhere. Decide what happens at the deadline with no reply.
- 5
Log the outcome
Showed, late, cancelled in time, cancelled late, no-show. Recorded by staff after the start time and reported monthly against the confirmed rate.
- 6
Pick where the timer runs
Provider-side scheduling for client messages, local notifications only for the provider's own phone, and one place in your database that owns the plan.
Sources
Where the specifics came from.
Four things on this page come from a primary source rather than general practice:
FAQ
Appointment reminder apps, answered.
An appointment reminder app sends clients or patients a confirmation when they book and one or more reminders before the appointment, usually by text, push notification or email, and records how they respond. The useful ones let the client confirm, reschedule or cancel from the reminder itself, log the outcome of every appointment, and store consent and opt-outs per client so the messages stay inside the rules for automated texts.
Start with the reply, not the message.
A reminder that cannot be answered is a notification. Decide what confirm, reschedule and stop do, write the record that remembers them, then build the app around it in Newly.