Make the reminder text ask for a reply
5 min read
By Lumina Software
- Operations
- Service business
- Scheduling
- Customer communication
- Automation
A reminder text that only says "See you tomorrow at 2" is a one-way street. It tells you nothing, so you still find out about the no-show at 2:15 when the chair is empty.
Make the reminder ask for a reply. Then the reply, or the silence, becomes something your team can act on the day before.
Why the plain reminder fails
Say your booking tool sends a reminder. It goes out a day before. It has the time, the address, maybe a map link. It looks fine.
Here is the problem. When nobody answers it, you can't tell three kinds of people apart.
One person read it and is coming.
One person read it and knows they can't make it, but felt awkward calling.
One person never saw it, because the number on file is an old one.
All three look the same in your system until the slot passes. By then it is too late to fill it.
I think the reminder is the cheapest place in the whole day to catch a lost slot. Most shops treat it as a courtesy instead of a check.
Write the text so the answer is one tap
The fix is small. Change the text so it asks a question that is easy to answer.
Something like this:
"Hi Dana, this is (your business name). You're booked tomorrow, Tuesday, at 2:00 PM. Reply 1 to confirm or 2 if you need a new time."
A few things matter in that line.
Use the business name people know. If the text comes from a short code with no name, people ignore it or think it is spam.
Say the day and the time. "Tomorrow" alone gets missed when someone reads it after midnight.
Give two choices with numbers. Typing "yes" is easy too, but numbers are easier to match in software and harder to misread.
Make "I need a new time" a normal option. My view is that people who can't come will tell you more often if you hand them the words. If the only option is confirm, the ones who can't make it just stay quiet.
Don't add a third or fourth choice. Every extra choice is one more thing the person has to read on a lock screen.
Decide what happens to each answer
This is the part most setups skip. The text goes out, the replies come back, and they land in an inbox nobody watches. That is worse than no question at all, because now the customer told you and you still didn't act.
Before you turn this on, write down what happens for each case.
If they reply 1, mark the visit confirmed. Nothing else. Don't send a long thank you message back. A short "Thanks, see you then" is fine.
If they reply 2, it needs a person or a booking flow, fast. Text back a link to pick a new time. Or put it on someone's list to call before noon. Then open the old slot right away so it can be given to someone else.
People will also reply with questions. "Is there parking?" "Can I bring my kid?" "Running 10 min late." These need a human to read them the same day. Route them to the front desk inbox, not to the void.
Then there is no reply at all. Pick a cutoff, like 10 AM the day of. Anyone who hasn't answered gets a phone call from a person or a second text. This is where you find the wrong numbers and the people who forgot.
If you only build one piece of this, build the "no reply" list. It is the one that turns silence into a short call list.
Fill the slot you just got back
A reply of 2 the day before is good news, even if it doesn't feel like it. You now have an open slot with almost a full day to fill it.
Keep a short list of people who asked for an earlier time. Your front desk may already keep this list in someone's head or on a sticky note. Put it somewhere the whole front desk can see.
When a slot opens, text the first few people on that list. First to reply gets it. Don't send it to everyone at once, or you will have five people show up for one chair.
This is also a good job for software. The rule is simple and it is the same every time. A slot opens, the list gets a text, the first yes gets booked, the rest get a "this one's taken, we'll keep you on the list."
What I'm not sure about
There are parts of this I don't have a firm answer on.
How far ahead to send it is one. A day before works for most visits. For long jobs or ones with prep, like a home service visit where someone has to clear a garage, two days might be better. I'd test it on your own calendar instead of copying someone else's rule.
Whether to send a second reminder the morning of is another. Some customers like it. Some find it pushy. If you send one, make it short and skip the question if they already confirmed.
And texting rules matter. You need the customer's okay to text them, and you need a clear way for them to opt out. I'm not a lawyer, so check what applies to your business before you turn on any automated texts.
Try it on next week's schedule
If your booking system lets you edit the reminder text, you don't need a new tool to test this.
Change tomorrow's reminder to ask for a 1 or a 2. Pick one person who reads every reply before 10 AM. Have them call everyone who stayed quiet.
Then count, at the end of the week, how many 2s you got and how many of those slots you filled. That count is yours, from your own phones, and it will tell you more than any average from a stranger's blog.
If the replies pile up faster than one person can handle, that is when it is worth building the routing in software. That is the kind of small system we build at Lumina Software, but the text change itself costs nothing and you can make it this afternoon.
Edit the reminder template today, and put a name next to "reads replies by 10 AM" on tomorrow's schedule.
Written by Lumina Software. Have a question? Book a call