It is 9am on a Tuesday. The monthly survey report is open on your screen.
Two 2-star reviews. Both from three weeks ago.
You pull the repair orders. One customer called three times. Each call was logged. Nobody escalated. The advisor was busy. The service manager assumed it was handled. It was not.
The review is already live. The OEM survey window has closed. There is no recovery play.
You were not there when it mattered. You are here now, reading about it after the fact.
This is the default state for most Fixed Ops operations. Not because the team is bad. Not because the advisors do not care. Because the systems in place are built to tell you what happened, not what is happening. The monthly survey report is an autopsy. It confirms the damage. It does not prevent it.
The moment you are sitting in right now is the real CSI problem. Finding out after the fact. Not the score. The timing.
Traditional CSI surveys arrive 2 to 4 weeks after the customer visit. That gap is not a minor inconvenience. It is a structural flaw.
Here is what it costs.
OEM holdback for a typical franchise dealership runs between 1% and 3% of the manufacturer suggested retail price on every new vehicle sold. For a store moving 80 units a month at an average transaction of $42,000, that is roughly $50,400 in holdback per month. That number is conditional on meeting CSI thresholds.
Most OEMs tie holdback eligibility to CSI score thresholds. The exact cutoffs vary by brand, but a common structure penalizes stores that fall below a regional or national benchmark. A single bad survey period can push a store below threshold.
One survey cycle with two or three 2-star responses can move a store's score 10 to 15 points on a 1,000-point scale. Depending on where the store sits relative to the OEM threshold, that 10-point drop can trigger a holdback reduction worth tens of thousands of dollars per quarter.
The surveys that drive that damage were completed weeks ago. The customers who filled them out formed their opinions while they were still in your Fixed Ops department. They were frustrated before they left. You just did not know it.
The 2 to 4 week lag is not a survey design problem. It is a visibility problem. And every fix that tries to solve CSI by improving the survey misses the point entirely.
Three fixes show up repeatedly in Fixed Ops operations. All three fail for the same structural reason.
More training for advisors. Training improves skills. It does not surface problems in real time. An advisor can be fully trained and still miss the signal from a customer who called three times without resolution. Training builds capability. It does not build visibility. The system that hides frustrated customers from management is still intact after every training session.
Exit interviews and comment cards. These are voluntary. Customers who fill them out are disproportionately satisfied or disproportionately furious. The middle, the quietly frustrated customer who is already composing a one-star review on the drive home, almost never fills out a comment card. Opt-in feedback is skewed feedback. It is not a representative signal.
More frequent survey cadence. Some Fixed Ops Directors respond to the lag problem by adding mid-cycle survey touchpoints. This produces more data. It does not produce earlier data. A survey sent at 10 days post-visit instead of 21 days post-visit still arrives after the customer has made up their mind. The opinion formed at the service counter does not change when the survey link arrives. You are still reading a report. You are still finding out after the fact.
The structural reason all three fixes fail is the same: they collect feedback after the customer has left. The problem is not the instrument. The problem is that the instrument only measures what has already happened.
The leak type here is what Fixed Ops teams call a heat case. A heat case is a customer who is frustrated, has not yet filed a complaint or survey response, and still has a recoverable situation. But only if someone reaches them in time. Heat cases become bad surveys when nobody reaches them. The standard fixes do not detect heat cases. They detect bad surveys. By then, it is too late.
You do not have a CSI score problem.
You have a visibility problem.
The score is downstream. It reflects what happened to customers who were frustrated and never heard from anyone before they filled out the survey. Every bad survey that lands in your monthly report was a heat case at some earlier point. That heat case was recoverable. You did not know it existed.
The reframe is this: if you could see which customers were frustrated before they left the Fixed Ops department, you could address it before it became a survey. The survey would not improve the situation. The situation would improve, and the survey would reflect that.
This is a different problem than the one most Fixed Ops teams are trying to solve. The common approach is to manage the survey. Follow up faster. Train advisors to prime customers before the survey arrives. Ask for good reviews. These tactics treat the survey as the output to optimize. They do not address the communication gap that produces bad surveys.
The approach that changes outcomes is detecting the heat case while it is still a heat case. That requires visibility into what is happening in your Fixed Ops operation in real time. Not a report that arrives three weeks later.
A Chrysler Dodge Jeep Ram dealership moved its CSI score from 820 to 981 in one month. The change was not a new training program. It was not a revised survey cadence. It was a system that flagged frustrated customers in real time and escalated heat cases before the customer left.
A Honda dealership moved its CSI follow-up score from 80 to 94. The only operational change was implementing the system. Nothing else changed in the Fixed Ops workflow.
Both results point to the same mechanism: catching the problem while there is still time to fix it. The score improves because the communication failure is addressed before it becomes a survey failure.
The category of tool that makes this possible is real-time CSI detection. It monitors customer conversations as they happen, flags sentiment signals that indicate frustration, and routes an alert to the service manager before the customer reaches the cashier.
This is not a survey tool. It does not improve the questionnaire. It surfaces the heat case while it is still recoverable.
A dealership that moved their CSI score 161 points in 30 days did not do it with better surveys. They did it with earlier visibility.
That is the shift. From finding out after the fact to knowing while you can still act.
See how a dealership moved their CSI score 160 points in 30 days.
What is a good CSI score for a dealership?
CSI score scales vary by OEM, but most use a 0 to 1,000 point range or a percentage-based scale. On a 1,000-point scale, scores above 900 are generally considered strong. OEM holdback thresholds typically sit between 850 and 920 depending on the brand and regional benchmarks. The more useful question is not what the number is, but whether it is trending toward or away from the holdback threshold. That is what matters.
How long does it take to improve CSI scores?
Results depend on what is causing the low scores. If the root cause is a communication failure (customers not receiving status updates, calls going unanswered, frustration building without escalation), scores can move within a single survey cycle, typically 30 days. A Chrysler Dodge Jeep Ram dealership moved from 820 to 981 in one month after addressing the communication gap. Structural issues like advisor skill deficits or process failures take longer.
What factors affect CSI scores the most?
Communication is the primary driver of CSI outcomes in Fixed Ops. Customers who receive proactive status updates, have their questions answered promptly, and feel informed about the status of their vehicle rate the experience significantly higher than customers who had to chase information. The quality of the repair matters, but survey data consistently shows that customers forgive process issues when communication is strong. They do not forgive being ignored.
What is a heat case in Fixed Ops?
A heat case is a customer who is frustrated during or after a Fixed Ops visit, has not yet filed a complaint or negative survey response, and is still in a recoverable situation. Heat cases are the stage between "frustrated customer" and "bad survey." Most Fixed Ops operations do not have visibility into heat cases because their feedback systems are retrospective. By the time the survey arrives, the heat case has already converted to a bad score.
How can a dealership detect CSI issues before a survey comes back?
Real-time conversation monitoring is the operational mechanism. Systems that analyze customer communication during the Fixed Ops visit (including inbound calls, text threads, and service advisor interactions) can identify sentiment signals that indicate frustration. When those signals appear, an alert goes to the service manager or Fixed Ops Director while the customer is still on the lot. The escalation happens in real time. The recovery is possible. Numa provides this capability under the LiveCSI product line, flagging heat cases before they exit the service department.
No more hold music. No more unanswered voicemails. Your customers are top priority.
