- Get link
- X
- Other Apps
By Dan Miller · Last updated November 8, 2026
You have watched it happen in your own shop. A customer's call goes unanswered, your callback lands in voicemail, and the job goes to whoever picked up. But send that customer a short text and the reply comes back — a text waits politely on the screen instead of demanding attention on the spot.
The hard part is rarely the sending. It is the blank screen: what do you write without sounding like a robot or a billboard? This post is the words — scripts written to paste into whatever you already use — text-back setup, CRM or texting app — with the bracketed blanks swapped for your details.
Timing lives in our other posts — the 7-day post-job follow-up system covers when each message goes out. This post is the companion: the exact wording for the moments those systems create, plus the everyday ones they don't.
Ground rules before you paste anything
Six rules first.
1. Keep it short. Thirty words or fewer. A text is a tap on the shoulder, not a letter; if it needs a second paragraph, it needs to be a call.
2. One ask per text. A message that asks for a reply, a review and a booking gets none of the three.
3. Fill in the brackets first. The [square brackets] are blanks for your details — a text that goes out with [Name] still in it costs more than sending nothing.
4. Name the shop in the first text. Customers ignore numbers they don't recognize. "This is [Shop Name]" is the difference between a reply and a delete.
5. Text at sane hours. Daytime and early evening. A non-emergency text at 10:30 p.m. reads as careless — and real emergencies call, not text.
6. STOP means stop. If a customer replies STOP, the thread ends immediately — no confirmation message, no one last offer. And only text people who contacted you first, or existing customers: every script below follows a conversation the customer started. That is the whole permission basis — don't cross it to chase cold leads.
Set 1: Missed-call text-back
When to send: the moment a call goes unanswered — automatically, if your system allows it. No text-back yet? Our guide to setting up missed-call text-back in an afternoon covers the mechanics — these are the words inside it.
The moment the call is missed:
"Hi, this is [Name] at [Shop Name] — sorry we missed your call. What do you need help with? Reply here, or we'll call back by [time]."
About an hour later, no reply:
"Just checking back, [Name] — we missed your call earlier. Still need a hand? Reply here and we'll get you sorted today."
Next morning, last try:
"Morning, [Name] — last check-in from [Shop Name] about yesterday's call. Still need help? Reply and we'll get you booked. No reply needed if you're all set."
Why it works: speed and a named person first; the second assumes they got busy, not uninterested; the third closes the loop so silence never becomes a chase.
Set 2: Estimate follow-up
When to send: after an estimate goes out and goes quiet. The sequence matches our 48-hour estimate follow-up system — these are the words for its touches.
The same day the estimate goes out:
"Hi [Name], thanks for having us out today. Your estimate for the [job] is on its way to your inbox — any questions, just reply here. — [Name], [Shop Name]"
Day 2, checking in:
"Hi [Name], checking in on the estimate we sent over. Happy to walk through any line of it, or trim the scope if the budget needs it. Any questions?"
Day 7, the final nudge:
"Hi [Name], last check-in on your estimate before I close the file. Want to go ahead? Reply YES and we'll book you in. Not now? Reply NO and I'll stop following up."
Why it works: each text has one job, and the last makes "no" acceptable — which, oddly, is what gets people to answer at all.
Set 3: Review request
When to send: within an hour of finishing the job, while the work is still the best part of the customer's day. For the bigger picture — platform, tools, what never to offer in exchange — see how to get more Google reviews automatically.
Right after the job:
"Hi [Name], thanks for having [Shop Name] out today. If we earned it, a short Google review really helps a small shop like ours: [review link]. Thanks again."
Next day, no reply — once only:
"Hi [Name], no pressure — just resending the review link in case yesterday's text got buried: [review link]. Either way, thanks for trusting us with the work."
Why it works: you ask once, at peak goodwill, and the nudge blames the inbox, not the customer. After that, stop — the goodwill is worth more than the review.
Set 4: After-hours auto-reply
When to send: automatically, whenever a call or text lands after hours.
"Thanks for reaching [Shop Name] — we're closed and back at [8 a.m.]. Emergency tonight — [no heat, flooding, a sparking panel]? Call [emergency number]. Anything else, reply here and we'll answer first thing."
Why it works: it sorts the night for you: emergencies get a live path, everything else gets a promise with a time on it. It's the written twin of your spoken after-hours greeting — both should promise the same callback time, or callers will believe the worse one.
Set 5: Appointment reminder and on-my-way
When to send: the reminder the day before; the second when the truck rolls.
The day before:
"Hi [Name], a reminder from [Shop Name]: we're booked for [job] tomorrow at [time]. Reply C to confirm, or reply here if you need to move it."
When the tech leaves:
"Hi [Name], this is [Tech name] with [Shop Name] — I'm on my way and should be with you in about [30] minutes. See you shortly."
Why it works: the reminder gives customers a painless way to reschedule before your tech drives across town to an empty house; the on-my-way text means they're watching for the truck, not startled by it.
Set 6: Old-customer reactivation
When to send: once a season, to past customers only, in the weeks before the weather turns — not the week systems start breaking down.
"Hi [Name], it's [Name] at [Shop Name] — we looked after your [furnace] last season. Cold weather's coming; want a check booked before it turns? Reply YES and we'll call to set a time."
Why it works: it goes only to people who already trust you, names the work you did for them, and YES is the easiest reply in the world. No discount, no urgency trick — the relationship is the offer.
Every script, on one timing chart
Pin it next to whoever runs the phones.
| Script | Send when | Job it does |
|---|---|---|
| Missed-call text-back | The moment a call is missed | Opens a text thread before they dial a competitor |
| Missed-call last try | The next morning, if no reply | Closes the loop without pestering |
| Estimate thank-you | The same day the estimate goes out | Confirms arrival and opens a reply channel |
| Estimate check-in | Day 2 | Handles doubts while the job is still winnable |
| Estimate final nudge | Day 7 | Gets a kind yes — or a clean no |
| Review request | Within an hour of finishing the job | Asks at the moment of peak goodwill |
| After-hours auto-reply | Whenever the office is closed | Sorts emergencies from morning work |
| Appointment reminder | The day before the visit | Surfaces reschedules before the truck rolls |
| Seasonal check-in | Once a season, past customers only | Fills quiet weeks with people who already trust you |
Which set do you set up first?
Don't launch all six this week. Pick the set that plugs your biggest leak, run it a month, then add the next:
Do good jobs slip away because nobody picked up? Start with Set 1 — the only set that recovers work already lost, and the one asking least of your customers, since they started the conversation.
Do estimates go out and then just sit there? Start with Set 2. What most shops are missing is not effort — it's a day-7 message they're willing to send.
Is the work good but the review count thin? Start with Set 3. One text sent on time beats any review tool you bolt on later.
Sets 4, 5 and 6 are polish — add them once the leak is plugged, one set at a time. Change six messages in a week and you'll never know which one worked.
FAQs
Is it legal to text customers like this?
In plain terms — and we are not lawyers, so this is a working rule, not legal advice: text people who contacted your shop first, or customers about their own jobs, and the moment anyone opts out they get nothing more. Cold-texting strangers is a different activity with different rules — talk to a lawyer before doing it.
How many follow-ups is too many before it becomes pestering?
Three touches per thread is the ceiling here: the first message, one follow-up, one closer. The number matters less than the ending — a sequence with a planned final message is follow-up; one without is pestering, whatever the count.
Should I text customers from my personal cell number?
No — use a business number or a texting tool, even as a one-truck shop. The thread belongs to the business: it survives a lost phone, doesn't walk away with a tech who leaves, and your personal number stays out of strangers' phones.
Texts or calls — which one gets answered?
They do different jobs. A call is for problems — anything complicated or emotional. A text is for things the customer needs to see twice: a time, a link, a yes-or-no question. Texts carry logistics; calls carry problems. Don't diagnose a furnace by text, or read an estimate aloud when a text can carry the number.
Do these scripts work for email too?
The structure, yes — one ask, the shop named early, a clear ending. The length, no: word for word in an email, these read as abrupt. Email gives you room for the context each script had to cut. Use the script as the skeleton, add the context, keep the rule: one email, one ask.
Want the dollar figure for your own shop?
Calculate my true cost →Disclosure: Some posts on TradeAI Tools contain affiliate links. This post does not. If you buy through an affiliate link elsewhere on this site, we may earn a commission at no extra cost to you.
Comments
Post a Comment