The Eight Touch Map: a message for every moment of auto repair customer follow up

This is the map from our video on auto shop customer follow up automation. The video set it up in four steps, and this page follows the same order:

1. Pickup ready. The words never change and the customer wants it, so switch it on first.
2. The reminder. Check your shop system first, because most already send it.
3. The review request. A day or two after pickup, the same request to every customer. A flagged ticket gets a person's call first.
4. Drafts last. Estimates and declined work are drafted for a person, and they go last, because a draft nobody reads is a delay.

Below is the full map of eight touches, a message for each one, and the rules that keep it honest.

Why map the whole repair order

"Nobody told me" is a complaint every advisor has heard, and it can turn a fair price into a bad review. Most follow-up tools are sold as one text after the visit. A repair order actually has eight moments where the customer is waiting to hear from you, and they aren't equally safe to automate.

Texting is often the channel customers prefer for these updates. A 1,000-driver survey by the vendor TEXT2DRIVE, reported by Auto Remarketing, found 42% preferred text, 29% email and 18% phone, and 57% preferred text for appointment reminders. It's a 2022 survey of dealership customers, so use it as a direction and ask your own customers.

The eight touches

#	Moment	Who sends it	Message to start from (edit to your voice)
1	Appointment reminder	sends itself	"Hi {first name}, it's Redline Auto. Reminder: your {car} is booked {day} at {time}."
2	Vehicle checked in	sends itself	"We've got your {car}. {Advisor} will text you after the inspection."
3	Inspection or estimate ready	drafted, person sends	"Your estimate for the {car} is ready: {items and prices}. Want me to go ahead?"
4	Waiting on approval	drafted, person sends	"Just checking in on the {item} estimate. Happy to call if that's easier."
5	Ready for pickup	sends itself	"Your {car} is ready for pickup. We're open until {closing time}."
6	Thank you and review request	sends itself, same for everyone	"Thanks for coming in. If you have a minute, would you leave us a review? {link}"
7	Declined or deferred work	drafted, person sends	"Last visit we noted {item}. Want a fresh quote when you're ready?"
8	Next service due	sends itself	"Your {car} is due for {service} around {date or mileage}. Reply to book."

The pattern is simple. Fixed-content messages can send themselves. Anything with a price, a recommendation or an apology goes through a person.

Step 1. Pickup ready

Start here. The content never changes, the customer is waiting for it, and nothing about it can go wrong in a way that costs you. Hook it to the repair order status your shop system already uses for "ready," and add one hold: if a comeback flag is on the ticket, the text waits for the advisor.

Step 2. The reminder

Before you build anything, check whether your shop system already sends appointment reminders. Most do. If it does, leave it there, so customers don't get two reminders from two tools. If it doesn't, add touch 1 with your shop's quiet hours, and nothing before 8 a.m. or after 8 p.m. local time (or whatever window you choose).

Step 3. The review request

Send it a day or two after pickup, and send it the same way to every customer. Google's policy for merchants says you may not discourage negative reviews or selectively solicit positive reviews from customers, so don't build a rule that only asks happy customers.

What you can do is make sure an unhappy customer hears from a person first. If the ticket carries a flag, such as a comeback, a long wait for a part or a complaint, the advisor calls before the request goes out. The request itself stays the same.

Step 4. Drafts last

Touches 3, 4 and 7 have prices, recommendations or judgment in them, so the AI drafts and a person sends. They come last for a practical reason: a draft only helps if someone reads it quickly. Before you switch them on, name the person who reviews each type and the time they'll do it. If estimates already take two days because the advisor has twelve cars, a faster draft won't help. Fix the queue first.

Rules that keep it honest

• One owner per message type. When something breaks, you know whose it is.
• Quiet hours. Pick a window and stick to it.
• Stop means stop. A STOP reply ends automated messages on every channel, not only texting.
• Registration. If you text from an application, Twilio's A2P 10DLC documentation says the sending number has to be registered. Check that your provider has done it.
• Replies reach a person. Any customer reply lands in front of someone, with the car's history visible.

What to count after 30 days

Skip vendor percentages and count what you can check yourself: messages sent by type, replies, appointments booked from a reply, STOP requests and complaints. If STOP requests climb, your cadence is too heavy. Shops are still early here. The 2026 Ratchet+Wrench industry survey found 15% of shops using AI for marketing automation, and the top reasons others held back were not knowing what to trust (23%) and cost (20%). Starting with the fixed messages addresses both.

Where RevvOS fits

RevvOS reads from your shop, customer and marketing systems, shows where each item came from, and prepares the next message for a named person to edit, approve, reject or replace. It sends only where that workflow has been set up, and it doesn't replace your shop system. See auto shop customer follow up automation, estimate follow up and declined work follow up.