- Get link
- X
- Other Apps
 |
Every shop has a version of this story. A tech drives forty minutes across town, parks in front of a quiet house, knocks twice, and waits. Nobody is home. The customer forgot, or wrote the day down wrong, or assumed the appointment was next week. The tech idles in the driveway, the office scrambles to fill the gap, and a slot that could have gone to a paying job turns into windshield time.
The frustrating part is that most no-shows are not rude customers. They are busy people who booked three weeks ago and heard nothing from you since. A short, well-timed reminder sequence fixes most of that, and it does not need new software or a marketing plan. Below is the sequence we recommend for small crews: four touches, the right channel for each one, what every message has to say, and what happens when a customer replies.
The short version
- Four touches: a booking confirmation, a reminder 24 hours before, one on the morning of the job, and one when the tech is on the way.
- Text for speed, email for the paper trail, and a phone call only when a confirmation never comes back.
- Every reminder carries the same core facts: the arrival window, the address, who needs to be home, and anything the customer must get ready before you arrive.
- Replies have to land in front of a person, not inside an app nobody opens. Sort out the routing before you automate anything.
The sequence at a glance
Four messages, each timed to the moment a customer can still act on it. Send the same four for every job, so customers learn what to expect.
| Step | When | Channel | Its job |
|---|---|---|---|
| 1. Booking confirmation | Right after the job is booked | Text, plus email | Locks in the details while the conversation is fresh, so a wrong address gets fixed today instead of at the door. |
| 2. 24-hour reminder | The day before, late afternoon | Text | Asks for a confirm or a reschedule while there is still time to refill the slot. |
| 3. Morning-of reminder | 7–8 a.m. on the day | Text | Short and practical: the window, the address, and any gate or parking note. |
| 4. On-the-way text | When the tech leaves the previous job | Text | Names the tech and gives a realistic arrival time, so someone is actually home and ready. |
Why text carries most of the load: a text gets seen within minutes, and replying takes two seconds. Email still earns its place at booking, because that confirmation is the record the customer searches for later. A phone call is your escalation step, not your default — save it for the customer who never confirmed.
What every message has to contain
A reminder that just says “you have an appointment tomorrow” wastes the send. Every message in the sequence should carry the facts a customer needs to be home, ready, and reachable:
- The date and the arrival window. A window, not a fake exact time. “Between 9 and 11” sets an honest expectation; “at 9:30” creates an angry customer at 9:40.
- The service address, stated back for confirmation. Half of all wrong-house problems are a typo from the booking call. Let the customer catch it in a text, not your tech at the wrong door.
- Who needs to be home. If an adult has to be present, or someone has to be there to approve work, say so plainly.
- Access notes. Gate codes, where to park, a dog that needs to be inside, a side entrance. Ask for them in the 24-hour reminder, while there is time to add them to the job notes.
- A payment-ready note. One short line — card on file, or payment due when the work is done — so the end of the job is not an awkward surprise.
- A reply path. “Reply C to confirm, or reply here to move it.” If the message does not invite a reply, customers will not send one.
Two of the four, written out. Our full set of text message scripts for contractors covers the rest of the customer journey, from missed calls to review requests.
The 24-hour reminder:
“Hi [Name], this is [Shop Name] confirming your [job] tomorrow, [date], between [9 and 11 a.m.] at [address]. Please have an adult home, and if there is a gate code or a parking note, just reply with it here. Reply C to confirm, or reply here if you need to move it.”
The on-the-way text:
“Hi [Name], [Tech name] from [Shop Name] is on the way and should be with you in about [30] minutes. If anything has changed at your end, reply here and we will see it right away.”
When the customer replies: route it to a human
Two-way is the whole point. A reminder the customer cannot answer is just a billboard, and the replies you get are exactly the ones that save jobs: “running about 20 minutes late,” “the gate code is 4417,” “can we move this to Thursday?” Each of those needs a named owner, fast.
Our routing rules for a small crew are simple. During work hours, every reply lands in one shared inbox that whoever is running the day actually watches — not on the personal phone of a tech who is under a house. The reply should sit next to the job it belongs to, on the same board the day is run from; our dispatch board system for a growing crew shows that setup. The assigned tech gets a copy of replies to the on-the-way text, because “running late” changes his next move, not the office’s. After hours, an automatic reply sets the expectation — when you will answer, and what to do in a real emergency — instead of leaving the customer talking to silence.
Set a response standard and keep it boring: during work hours, a reminder reply gets an answer within about fifteen minutes. We would honestly rather see a shop send three reminders that a person monitors than five that vanish into an app nobody opens.
The no-show rescue step
Even a good sequence will not catch everyone, so decide the rescue steps now, while nobody is standing in a driveway. Ours: the tech knocks, calls, and texts from the door — three attempts, all logged on the job — then waits a set ten minutes unless dispatch says otherwise. While the tech is still nearby, the office sends one rescue text: “We were just at your door and missed you. We can come back today at [time] or tomorrow at [time] — reply 1 or 2 and we will hold it.” Two concrete options get answers; “please call us to reschedule” mostly gets silence.
Log every no-show on the customer record. One no-show is life happening. A customer who no-shows twice gets a phone call to book the next visit instead of a text sequence, and a deposit conversation is fair at that point. That protects the slots your other customers are waiting for.
Set it up with the tools you already have
Setup order matters more than software. Work through these five steps before you spend anything:
1. Turn on what your calendar or CRM already sends. Most scheduling tools and field-service apps already include confirmations and reminders — they are just switched off or still using the default wording. Our comparison of scheduling apps for HVAC technicians notes which ones handle reminders well. Start there.
2. Replace the default templates. Use the checklist above: window, address, who needs to be home, access notes, payment note, reply path. Fifteen minutes of editing, once.
3. Run the on-the-way text by hand for a week. Have each tech send it from a saved template before you automate it. A week of doing it manually shows you where the timing breaks, and that is a dispatch habit to fix, not a software gap.
4. Name the reply owner, every day. Put it on the morning board. Unowned inboxes are where “running late” messages go to die.
5. Count no-shows once a month. Ten minutes: how many, which day of the week, and how far ahead the job was booked. Jobs booked three or more weeks out are the usual repeat offenders — for those, add one extra touch a week before: a short “still good for next Tuesday?” text.
Answer 3 questions → is your sequence ready?
Do not judge the sequence by how it reads — judge it by these three questions. Question 1: Does every booked job trigger a same-day confirmation with the address stated back? If no, fix step one first — reminders built on unconfirmed bookings just remind people about the wrong appointment. Question 2: If a customer replies “running late” at 7 a.m., whose screen does it land on? If the honest answer is “whoever notices,” your routing is not done, and that is the fix that saves the most jobs. Question 3: When a tech is standing at an empty house, does everyone know the exact next step? Knock, call, text, ten-minute wait, rescue text with two options, log it. If your crew can recite that, your sequence is ready — and the empty-house trips should start getting rare.
FAQs
How many reminders should I send before an appointment?
Four touches is the sweet spot for most home-service jobs: a confirmation at booking, one 24 hours before, one on the morning of the job, and one when the tech is on the way. More than that starts to feel like nagging, and customers tune it out.
Should appointment reminders be texts, calls, or emails?
Texts do the heavy lifting because customers see them fast and can reply in seconds. Use email for the booking confirmation, where a written record helps. Save phone calls for the customer who never confirmed, where a two-minute call is cheaper than a wasted trip.
What should I do when a customer does not confirm?
Send the morning-of reminder anyway, then make one short phone call before the tech drives out. Mark the job at risk on the board. If nobody answers either, have the tech call from the driveway before knocking, and follow the rescue steps in this guide.
Do I need new software to automate appointment reminders?
No. Most calendars, CRMs, and scheduling apps already send confirmations and reminders; they are often just switched off. Turn those on, fix the wording, and run the sequence for a month before you consider paying for anything new.
No prices appear in this article.
Affiliate disclosure: some links on this site are affiliate links. If you buy through them we may earn a commission at no extra cost to you.
Comments
Post a Comment