Techs can’t solve the problem that can’t be found
The fellas who taught me to write service were arguably some of the best I’ve seen do the job. They had all sorts of tricks up their sleeves, like the boomerang business cards you’ve read about before. Today, I’d like to share another tip my friend Sam gave me. It made my life easier as a writer, so much so that later in my career as a tech, I trained my writers to take this simple step: print out service histories. This might sound a bit antiquated in paperless 2026, but bear with me.
Service updates that keep repairs moving. Photo: Gustavo Fring from Pexels.
Sam had me do this primarily because some technicians developed a bad habit of recommending service based solely on vehicle mileage or sometimes based on a factory service recommendation. This was, however, a pretty big problem if a service had been performed recently and a tech unwittingly sent a writer to recommend it again.
For instance, maybe a customer’s vehicle maintenance schedule called for oil changes every 3,000 miles and a trans flush every 40,000 miles. At 39,000 miles, the customer comes in for a regularly scheduled oil change and rotation. Knowing he has a road trip planned with the family, our customer intelligently elects to perform the trans service early so as not to run afoul of the service schedule. When the customer next returned at 42,000 miles, an ambitious tech might say, “Hey, this car is overdue for a trans flush. Mr. Service Writer, you’d better recommend one!”
Expert communication from inspection to completion. Photo: Freepik.
The writer who failed to catch this is now made to look like a bit of a swindler. Dutiful technicians can inadvertently turn their writers into crooked thieves. Printing vehicle history out—and highlighting aberrations like this one—often saves this from happening. Shifting this responsibility from being solely the tech’s into a shared task involves many eyes looking over any given vehicle.
The second instance Sam correctly identified as beneficial was when a vehicle had repairs performed in the past that could be related to a present problem. Who knows what’s causing the high-speed miss and P0300 code in that vehicle in for service today? Probably no one. But if the vehicle previously revealed a stored P0171 code when in for service at some point, maybe that info might inspire the tech to begin testing the fuel filter or pump. And further inspection of the service records might show your shop may have already replaced that, too.
Trusted service support at every step of the repair. Photo: Gustavo Fring from Pexels..
A writer who caught those possibly-interrelated occurrences when printing and examining service history might catch previous repairs that could be related to the current problem. Jotting a note for a tech is saving the shop and tech time, assisting passively in the diag process, and most importantly, keeping customer sentiment high. “Mr. Smith, we looked into it, and we think this fuel pump we installed a while back may be just starting to fail. We’re going to test a few things, but we feel the safe move is preemptively replacing it at no cost to you” is the best any customer can ask for.
That’s the example at its extreme, but you can certainly imagine the myriad other ways this can help. If you don’t do this little trick yourself, odds are quite high you’ve even been in this predicament. “Didn’t you guys just replace that?” is very often the question asked before a customer puts their guard way up.
Writers, get involved. Print those histories, or peruse them electronically and make notes for your tech, or wander out and have a quick chat. Your mechanics will thank you, and despite the vehicle’s status being the same, you’ll have customers who rely on you, not question your integrity.
The articles and other content contained on this site may contain links to third party websites. By clicking them, you consent to Dorman’s Website Use Agreement.
Participation in this forum is subject to Dorman’s Website Terms & Conditions. Please read our Comment Policy before commenting.