You're parked outside a job with the engine still running, thumbs over your phone, typing out your hours for the fourth time today. Same question, same answer, a different customer. By Friday you've written some version of "we cover Worcester and the towns around it, usually booked about a week out" so many times you could type it blindfolded.
Nobody warns you that running a shop means answering the same ten questions about the work almost as often as you do the work itself. What are your hours. Where do you go. Do you take cards. Can you swing by and take a look. Each reply costs a minute or two, and a minute or two, forty-odd times a week, adds up to an afternoon you never get back.
Good news: you don't need a chatbot or a big phone system to fix this. You need a short library of your own answers, written once, kept where your thumb can reach them, ready to send and tweak in seconds. AI happens to be good at building that library out of the replies you've already typed a hundred times. Here's how.
Figure out your ten questions first
Before you automate a thing, spend five minutes naming the questions. You already know them cold, so this part is quick.
Scroll back through a week of texts and emails and watch what keeps coming up. For most shops it's some mix of these:
- Hours, and whether you're open weekends
- Service area, which towns you actually cover
- Whether you take cards, checks, or just cash
- "Can you come take a look," and what that visit costs
- Rough lead time, how booked out you are right now
- Whether estimates are free
Most shops land on eight to twelve. Jot yours in a note on your phone. That list is the spine of everything else.
Let AI turn your old replies into clean drafts
Here's the part that saves you the actual writing. You've already answered these questions well, dozens of times, in your own words. You just have to hand those words to the AI.
Grab a few of the real texts and emails where you answered each question and copy a handful of them, warts and all. Don't clean them up first, the rough ones teach it how you really talk.
Paste them into an AI assistant (ChatGPT, Claude, whichever you've got) with a plain ask. Something like: "Here are a bunch of replies I've sent customers. Turn them into a set of short, reusable answers I can save and edit. Keep my wording and tone, and group them by topic."
What comes back is a tidy set of short answers that sound like you, because they came from you. No stiff manual language, no robot cheer. One pass is usually enough to get a solid first draft of your whole library.
Keep it in your voice, not form-letter land
The reason most saved replies feel cold is that somebody else wrote them. Yours won't have that problem if you built them from your own texts, but it's still worth a quick read to catch anything that drifted stiff.
Read each draft once, out loud if you can, and fix what doesn't sound like you. A few small habits keep them human:
- Keep your real greeting ("Hey, thanks for reaching out")
- Leave a blank to drop in a name or a date
- One or two sentences is plenty, you don't owe anyone a paragraph
Treat a saved reply as a starting point, not a send button. You're pasting it in, then adding the one detail that makes it fit the person asking.
Save them where your thumb can reach
A plain list in your notes app works fine, you just copy and paste from it. There's something faster, though, and it's already built into your phone.
Both iPhones and Androids have a text-replacement feature, where you type a short code and the full reply expands on its own. You set up a little shortcut once, and after that the answer appears the second you type a couple of letters.
- iPhone: Settings, then General, then Keyboard, then Text Replacement. Type the reply in the top box and a short code like "hhours" in the bottom.
- Android: look under Settings, System, Languages and input, for a personal dictionary or text-shortcut option. Same idea, same payoff.
- Keep the codes easy to remember: "hhours" for hours, "harea" for service area, "hcards" for payment.
One honest limit: long replies with line breaks don't always behave inside text replacement, so keep your shortest answers there and leave the longer ones in a pinned note you copy from.
Prices and promises still get a human glance
This is the one rule we won't let slide. AI writes the starting point, but anything with a dollar figure or a time commitment gets your own eyes before it goes out. A saved reply is fast, and fast is exactly how a wrong price or a promised Tuesday slips through.
Prices drift. Your week fills up. The quote that was right in March reads wrong by June, and a saved "we can be there tomorrow" becomes a headache when tomorrow's already full.
- Don't bake a specific price into a saved reply, use a range or "depends on what we find"
- Never promise a date you haven't checked against your actual calendar
- Reread anything that commits you to money or time before you hit send
If the text-replacement setup makes your eyes cross, that's the kind of small thing we help Massachusetts shops sort out in an afternoon.
Worth doing this week
None of this takes a weekend. Five steps, start to finish:
- List your ten most-asked questions in a note. Five minutes, you already know them.
- Copy ten real replies you've already sent and paste them into an AI assistant, asking for clean reusable versions in your voice.
- Read the drafts once, out loud, and cut anything that sounds stiff.
- Load the five you use most into your phone's text replacement with easy codes.
- Leave prices and dates out, or flag them, so you always glance before you send.
Do that, and the next time someone asks what time you open, the answer's out the door before you've climbed back in the truck.