Appointment Confirmations and Reminders

A no-show appointment costs you the drive time, the lost slot, and the credibility hit when the next customer's appointment runs late because you tried to fit the no-show's reschedule in. Reminders cut no-show rates roughly in half — sometimes more — and that's before you count the customers who reschedule themselves rather than no-show, which is even better for everyone.

Suprata sends confirmation and reminder messages automatically, on a regular schedule, via email or SMS or both. This article covers when each message goes out, what they should say, how the reschedule flow works, and the settings that determine whether the system is your friend or an annoyance.

When you'd think about this

You're setting up a brand-new account and the default message templates don't match your voice.
Your no-show rate is too high and you want to know if reminders would help (yes, they would).
A customer complains about getting too many messages from you (this happens — the threshold is real).
A reminder went out at 7 AM and the customer was furious — you need to fix the quiet-hours window.
You're choosing between SMS-only, email-only, or both.
The reschedule link in your confirmations isn't working as expected.

The mental model — three message types, three timings

There are three distinct messages in the life of a confirmed appointment:

The confirmation — sent when the appointment is scheduled. "We've got you down for Tuesday at 10." Usually goes out immediately when the appointment is created or moved to Scheduled.
The reminder — sent before the appointment, typically 24 or 48 hours ahead. "Quick reminder: tomorrow at 10 we're coming out." This is the message that does the most no-show prevention.
The "tech is on the way" — sent shortly before arrival, sometimes triggered by GPS/check-in. "Your tech Carlos is en route, ETA 9:55." This one is mostly about customer experience — it doesn't move the no-show needle much.

A good setup has all three. A minimal setup has at least the first two. SMS-only or email-only is fine; both is better but with diminishing returns and higher per-customer cost (especially for SMS).

When messages actually go out

Suprata checks for appointments whose reminder time has come up every few minutes, but it only sends messages during waking hours — typically 9 AM to 7 PM in your timezone. Sending an SMS reminder at 3 AM would generate angry customers; the system holds the message and sends it in the morning instead.

Two settings to know:

The reminder lead time. How far in advance does "the day before" mean? Typically 24 hours, but some businesses prefer 48 (gives the customer more time to reschedule) and some prefer 12 (closer to "tomorrow" rather than "yesterday I forgot already"). Try 24 first.
The send window. What hours are messages allowed to go out? 9 AM-7 PM is the safe default. Adjust if your customer base is different (B2B might prefer 9-5; on-call services might extend to 8 PM).

Confirmation messages (sent on creation) usually don't wait for the send window — they go immediately because the customer just booked and is expecting a confirmation. But many accounts add a "if it's after 9 PM, hold until tomorrow morning" rule for these too.

The dispatch board — appointments lined up across techs, with status colors indicating which have been confirmed

What each message should say

You can customize the message wording. The defaults are reasonable but generic — rewrite them to match your voice. Some principles:

The confirmation:

Subject line / opening: who you are, what's confirmed.
Date, time window, and address.
The tech's name (if you assign in advance and want the customer to know).
A way to reschedule or cancel — link, phone number, or both.
Your contact info for questions.

Bad: "Your appointment is confirmed for 10/15/2026 at 10:00:00."
Good: "Hi Sara — we've got you down for Tuesday Oct 15 between 10 and 11 AM. Carlos will be your tech. Reply RESCHEDULE if you need to move it, or call us at (555) 123-4567."

The reminder:

Should feel like a reminder, not a fresh confirmation.
Restate the date/time briefly.
Offer an easy reschedule path — don't make it a phone call only if you can avoid it.
Don't send a wall of text. Three sentences is plenty.

Bad: A 10-paragraph re-introduction.
Good: "Hi Sara — quick reminder we're coming tomorrow Tue Oct 15, 10-11 AM. Reply CONFIRM or RESCHEDULE."

The "tech is on the way":

Tech's name and approximate ETA.
Optional photo of the tech (some shops do this; it builds trust).
A way to ask a quick question if needed.

Bad: "Tech in transit."
Good: "Carlos is heading your way, ETA 9:55. Text back if you need to reach him."

SMS vs. email — practical tradeoffs

SMS. Higher open rates (over 95% within minutes vs. ~25% for email). Better for time-sensitive content. Costs per message (small, but real). More likely to feel intrusive if overused. Limited to short content (160 chars per segment; longer messages are split or sent as MMS). Doesn't support rich formatting or attachments.

Email. Lower per-message cost (effectively zero). Supports formatting, links, photos. Slower opens; less time-sensitive. Less intrusive but also less attention-grabbing. Spam filters can swallow legitimate confirmations.

The right mix:

Confirmation — both. Email for the record, SMS for immediate ack.
Reminder — SMS strongly preferred. Email as a fallback if no mobile number.
Tech-on-the-way — SMS only. Email is too slow to matter for a 15-minute heads-up.

To send SMS, you need a Twilio account configured (see Setting up SMS via Twilio). Email runs through your configured SMTP (see Setting up email/SMTP).

The reschedule flow

The whole point of reminders is to convert "won't show" into "rescheduled" instead. That means the reschedule path has to be easy.

The conventional flow:

Customer receives the reminder.
They reply with a keyword (e.g., "RESCHEDULE") or click a link.
The system either:
- Surfaces an alert in dispatch ("Sara wants to reschedule") for the team to act on, or
- Opens a customer-facing self-service reschedule page where the customer picks a new slot directly, or
- Auto-replies with a phone number to call.
The new slot is booked; the old slot is freed; a fresh confirmation goes out for the new time.

The self-service version (option 2) is the most powerful because it works at 11 PM when no one's in the office. Configure it if your account supports it.

If a customer doesn't reply or click anything by the appointment time, that's a no-show. Most accounts have an auto-status flow that marks unattended appointments accordingly so they show up in the no-show report.

Configuration choices that matter

Walk through these on initial setup:

Default channels per customer. Email-only, SMS-only, or both. Most accounts default to "both if we have both contact methods, else whichever we have." Customers who opted out of one or the other should have that respected per-customer.
Quiet hours. When messages won't go out. 9 AM-7 PM is conventional; adjust per business.
Reminder lead time. 24 hours is the default; you can have multiple reminders if appropriate (48-hour and 24-hour, for example).
Templates. Customize the wording for each of the three message types. Use mail-merge variables for date, time, customer name, tech name, address, links — the templates support a standard set.
Reschedule link / keyword. Make sure the reschedule path actually works before you turn confirmations on for everyone.
Per-customer opt-out. Customers who genuinely don't want messages can be marked accordingly. Respect this — repeated unwanted messages are an FCC issue in the US.

Common mistakes

Sending reminders at all hours. A 6 AM reminder is the easiest way to lose a customer. Always set a quiet-hours window.
Using a generic, robotic template. "Your appointment is confirmed for [DATE] at [TIME]" feels like a system, not a business. Spend ten minutes humanizing the templates.
Confirmation without a reschedule path. A confirmation that says "see you Tuesday" with no way to change it forces every reschedule into a phone call. That's a chunk of customers who'll just no-show instead.
Three-reminders-overlap-in-an-hour. Some accounts accidentally set up multiple overlapping reminder rules, and a customer gets hammered. Audit your reminder rules; one or two well-spaced reminders is plenty.
Not testing the SMS flow on your own phone first. Send yourself a confirmation. Send yourself a reminder. Reply with the reschedule keyword. Make sure the loop closes. Find broken links before the first customer does.
Not handling opt-out. A customer texts "STOP" and the system keeps sending. That's a regulatory and trust problem. Make sure your account's opt-out handling is turned on (Twilio handles most of this automatically; verify it).
Using personal phone numbers as the reply-to. Customers reply to confirmations, and those replies need to land somewhere monitored. If the SMS comes from a Twilio number, replies arrive through Suprata's inbox. If it comes from someone's personal cell, replies go nowhere useful.
Assuming the customer will always confirm. Some won't. The reminder's job is to get the customer thinking about the appointment; the confirmation reply is gravy. Don't cancel an appointment just because it wasn't explicitly confirmed.

A note on tone and frequency

Customers tolerate two messages from you per appointment without complaint: a confirmation when booked, a reminder the day before. Three is borderline (add the en-route ping, which most people actually like). Four is annoying. Five is a complaint.

Resist the urge to "just to be sure" with extra reminders. The data is clear that two well-placed messages do more than four overlapping ones. Quality of timing beats quantity of messaging.