A no-show costs twice: the empty slot you could have sold, and the drive you already paid for. Reminders reduce it, but not all reminders do the same job, and the common version — a single generic message the day before — leaves most of the value on the table. What follows is the three-message pattern that works for visit-based businesses, with wording you can adapt.
The confirmation and the day-before message
Send the first at booking, while the customer still has the conversation open. It confirms what was agreed and quietly sets expectations: "Booked: Tuesday 3 September, arrival between 09:00 and 11:00. Erik will call about 20 minutes before. Address: Storgata 14, 2nd floor. Anything to change? Reply here and we'll move it." Specific arrival windows beat exact times you cannot keep — an unmet 09:00 does more damage than an honest two-hour window.
Send the second the day before, and make it easy to cancel. That sounds backwards, and it is the whole trick: you are not trying to extract a promise, you are trying to learn about a problem while the slot is still sellable. "Tomorrow, 09:00–11:00, Storgata 14. If that no longer works, tell us today and we'll find another time — no charge for moving it." A customer who reschedules on Monday evening is a saved slot; one who says nothing and disappears on Tuesday is not.
The on-the-way message, and what to leave out
Send the third on the day, when the technician is actually on the way: "Erik is on his way, about 25 minutes out. He'll need access to the cellar and roughly an hour." This is the message that prevents the specific failure where somebody is home but not ready — the cellar is locked, the car blocks the drive, nobody moved the furniture. It also quietly reduces the calls asking where you are.
Notice what is not in these templates. There is no "please confirm by replying YES", because confirmations mostly measure who is good at replying to texts. There is no apology for the reminder, no marketing, and no link that requires an account. Every message carries the same four facts — when, where, who, what to prepare — plus one obvious way to change it, and nothing else competing for attention.
What to do when a customer goes quiet
Decide in advance what happens when someone goes quiet. A workable rule: no response to the day-before message is fine and needs nothing, but no answer to a direct question you asked gets one phone call by mid-afternoon. If that call is not returned before the end of the day and the slot is in demand, tell the customer plainly that you are releasing it and how to rebook. Silent unilateral cancellation is how you turn a no-show into a bad review.
Judge it on no-shows and reschedules together
Judge the change on two numbers, not one. No-shows should fall, but reschedules will rise, and that combination is success rather than a new problem — a moved visit is a customer you kept and a slot you got back with warning. If no-shows fall while reschedules stay flat, you have most likely tightened your wording rather than surfaced problems earlier, and there is still room in the day-before message.
Rewrite your reminders in one sitting
Open your current reminder and check it against four facts: when (as a window you can keep), where (with floor and entrance), who is coming, and what needs preparing. Most reminders are missing at least two, and the missing ones are usually the reason somebody was home but not ready.
Add one obvious way to change the appointment, and make it the easiest action in the message. If rescheduling requires calling during office hours, you have built a system that converts a fixable conflict into a no-show, because the customer discovers the problem in the evening.
Set the arrival window to something you keep on a bad day. A two-hour window you hit consistently earns more trust than a thirty-minute window you miss twice a week, and the narrow window costs you the phone calls asking where the technician is.
Frequently asked question
When should you send an appointment reminder?
Three times, each doing a different job: at booking, to confirm the details while the customer still has the conversation open; the day before, framed to make rescheduling easy so a conflict surfaces while the slot is still sellable; and on the day when the technician is actually on the way, with an arrival estimate and what needs to be accessible. A single generic reminder the day before captures only part of the benefit.