Review Automation
Your Service Drive Is Writing Your Dealership's Google Rating
Dealerships coach reviews on delivery day and ignore the service lane, where most customer visits actually happen. Here is how to find out whose experience your public rating reflects, and a five-step fix.
by Jerrod Anthraper
Tag Your Last Twenty Reviews S or F
Pull up your dealership's Google reviews and go down the last twenty. Mark each one S if it came from the showroom and F if it came from fixed ops. You can almost always tell in one sentence — sales reviews name a salesperson, service reviews name a wait.
Most stores find the same split. The fives say "Marcus made it easy." The ones and twos say three hours for a recall, nobody called, the loaner was gone. Two departments are writing your rating. Only one of them was ever asked to.
The Leak: Your Rating Is a Self-Selected Sample of Angry Service Customers
Run the volume math. A store selling ninety cars a month is writing eight hundred to a thousand repair orders in that same month. Service is where the relationship actually lives — a buyer sees your sales team twice in six years and your service drive twelve times.
But the review ask is built into delivery day, where there is a script, a spiff, and a manager watching. In the service lane there is no ask at all. So the only service customers who write anything are the ones angry enough to do it unprompted. That is the sample your rating is made of, and roughly 88% of consumers say they trust online reviews as much as a personal recommendation. They are trusting a sample you never collected.
Why It Happens: The Ask Lands in the Worst Ninety Seconds of the Visit
Two things cause this, and neither one is laziness.
The first is ownership. Reviews sit under the sales manager because delivery day is where the process was built. Nobody assigned them to the service director, so nobody in fixed ops has a number to hit.
The second is timing. When a service ask does happen, it happens at the cashier window — the exact moment the customer is handing over $840 for something that broke. That is the low point of the entire visit. Advisors know it, feel the awkwardness, and stop asking. Then the manufacturer CSI survey shows up in the same conversation, the advisor pitches that instead, and the Google ask disappears entirely.
The Fix: Five Steps to Make Fixed Ops Your Review Engine
1. Split your sample before you change anything
Take ninety days of reviews and tag every one sales or service. Count each side and average the stars on each side separately. Then put your RO count next to your unit count for the same period.
Almost every store finds the same picture: service generates ten times the customer visits and a fraction of the reviews, at a much lower average. That one table ends the debate about where the problem is, and it gives your service director a starting number instead of a complaint.
Do not skip ahead to the fix. Owners who change the process without measuring the split end up arguing with their service director about whether the problem is real, and that argument kills the initiative faster than any software gap ever will.
2. Move the ask off the cashier window
For express work — oil, tires, a quick recall — send the ask a few hours after pickup, once the customer is home and the visit went the way it was supposed to. For repair work, wait until the next day. The customer needs to drive it and confirm the noise is actually gone before she can honestly say you fixed it.
Nobody asks well while taking a payment. Take the ask out of the advisor's mouth and put it on a timer.
The interval matters more than the wording. A customer who has driven the car and found the problem gone will write you a specific, credible review. A customer asked at the register writes nothing, or writes about the wait.
3. Ask by advisor name and track ask rate by advisor
Send the request with the advisor's first name in it: "Did Ronnie get your Tahoe sorted out?" Customers rate people, not buildings, and an advisor's name in the text lifts response.
Then track requests sent and reviews earned per advisor and post it in the shop where the hours board hangs. Not to punish anyone — to make it visible. A review process without a name attached becomes nobody's job by the second week.
4. Put one question in front of the link
Before the Google link, ask a single question: how did we do, one to five? Fours and fives get the review link. Ones through threes get routed to the service director's phone, and somebody calls that customer inside the hour.
This is the step that makes advisors willing to ask at all. They stop asking when they are afraid of the answer, and the fear is rational — they know about the three-hour wait. Give them a system that catches the bad ones before Google does and the ask rate climbs on its own.
5. Separate the CSI survey from the Google ask
Your manufacturer survey and your public reviews are two different instruments serving two different masters, and advisors conflate them constantly. The survey protects your allocation and your bonus money. Google reviews decide whether the next person searching your dealer name at 8 p.m. drives to your store or the one twelve miles up the road.
Give the advisor one sentence and one link for the Google ask. Let the CSI survey run on its own timeline. Asking one person to pitch both in the same breath means you get neither.
The Proof
Volume is the whole game in fixed ops. A store writing nine hundred ROs a month does not need a better ask — it needs an ask that fires on all nine hundred instead of on the handful an advisor remembers.
AMG Transport Co., a Tykon client in transportation and logistics, went from 5-6 reviews per month to 5-6 reviews per day within two months of putting an automated, trigger-based ask in front of every completed job.
Same customers. Same service quality. The only thing that changed was that the ask stopped depending on whether a busy person remembered to make it.
What This Looks Like When It Runs Itself
None of the above requires new software in theory. In practice it requires somebody to watch the RO close queue all day, send a timed text on every one, catch the low scores within the hour, and keep doing it in December when the shop is buried.
That is the job James, Tykon's AI sales agent, is built to hold. It fires the ask off RO close, waits the right interval depending on the work performed, routes anything under four stars to your service director's phone before it reaches Google, and follows the good ones with a referral ask while the customer is still happy.
If you want a starting point, do step one this week. Ninety days of reviews, tagged S or F, with your RO count beside your unit count. Send us the table and we will tell you what we would fix first — no deck required.