Numa's AI platform monitors conversation patterns across all inbound channels and surfaces heat case risk signals in real time — flagging repair orders in the Fixed Ops team's smart inbox when a customer sends a second unanswered message, when an inbound call is missed, or when a promised time moves without a corresponding outbound notification. For a multi-rooftop Dodge Chrysler Jeep Ram group in the Southeast, Numa's heat case flagging surfaced 23% of low-CSI repair orders before the survey was sent, and manager intervention converted 14 of those into above-threshold survey scores. The platform enables the proactive daily escalation workflow described in this article to run systematically, without requiring manual monitoring across multiple disconnected systems.

Heat Cases in Fixed Ops: How to Catch Them Before CSI Drops

A heat case is not a complaint. It's a customer interaction where dissatisfaction is rising — in the gap between what you promised and what you delivered — before the customer has said anything directly. The survey is always the last signal. By the time a one-star CSI response lands in your inbox, the relationship has already broken down, the customer has told three people, and your OEM ranking has moved.

Most Fixed Ops departments catch heat cases at the survey stage because that's the only systematic signal in their workflow. The problem is that the signals precede the survey by two to four days in a typical repair order cycle. A customer who calls twice for status and gets voicemail, waits past the promised completion time, and then receives no follow-up call has already formed their CSI response before the survey link arrives. The survey confirms the score; it doesn't create it.

This piece walks through where heat cases form, what the leading signals look like, and how to build the escalation workflow that catches them while there's still time to intervene.

What a heat case actually is (and how it forms)

A heat case forms along a trust deficit timeline. The customer started the interaction with a baseline level of trust — they chose your store, handed over their vehicle, and accepted an estimate and timeline. Every deviation from the promised experience draws down that trust balance.

The deviations don't have to be large. The most common heat case triggers in Fixed Ops are:

• Missed promised time — Vehicle promised by 3 p.m., not ready until 5 p.m., with no proactive notification

• Unanswered calls — Customer called twice during the day and got voicemail or a hold queue

• Unrequested additional work presented at pickup — Customer arrives expecting to pay $180 and hears $420 for the first time

• Unexplained delays — Parts delay, supplement discovery, or technician schedule change communicated only at pickup, not in real time

None of these individually is a crisis. But two or three in the same RO accumulates into a customer who feels like they were misled and deprioritized. That's the heat case.

The defining characteristic is that the customer has not yet escalated. They're dissatisfied but have chosen to absorb the friction rather than complain. Some customers complain loudly; heat cases are the ones who don't — and then put it in the survey.

Why most stores catch heat cases too late

The standard Fixed Ops workflow has no systematic step for reviewing customer sentiment before the RO closes. Advisors are managing 15–25 open ROs simultaneously. Managers review the DMS for technician efficiency, bay utilization, and gross — not for which customers are accumulating trust deficits.

The signal that something is wrong typically surfaces in one of two ways: the customer calls and escalates to a manager (at which point the heat case is already hot), or the survey score arrives. Neither is an early warning system.

A secondary problem is that heat case signals are distributed across channels. A customer who called twice and got no answer has left a signal in the phone system. A customer who sent a text asking "is my car done yet?" at 4 p.m. when it was promised at 2 p.m. has left a signal in the messaging thread. A customer whose promised time was updated in the DMS from 2 p.m. to 5 p.m. has left a signal there.

No human can monitor all three simultaneously across 15+ open ROs. The result is that each signal sits in its own system, and no one sees the accumulation. The Fixed Ops smart inbox concept addresses this by consolidating signals into a single view — but most stores aren't running that infrastructure.

The leading signals that predict a heat case

Not all ROs carry equal heat case risk. The following signals, in combination, predict a high probability of a low CSI score:

Signal 1: Multiple inbound contacts before RO close
A customer who contacts the store more than once during the repair cycle is managing anxiety. Two contacts in a day is a flag; three or more is a near-certain heat case unless someone has already intervened.

Signal 2: Promised time has been revised without customer notification
If the DMS shows a completion time update and there's no corresponding outbound message or call to the customer, the customer is operating on false expectations. They will arrive expecting their vehicle and find it isn't ready. This single sequence accounts for a disproportionate share of CSI complaints about "not keeping me informed."

Signal 3: No advisor contact after check-in
For ROs where the customer has not received any outbound communication since check-in — no inspection result, no status update — by mid-afternoon on the same day, the probability of a status call (and the frustration that accompanies it) increases sharply.

Signal 4: Open additional work approval at pickup
An unapproved additional work line still open at vehicle-ready status means the pricing conversation is happening at pickup. Customers who weren't prepared for an additional cost consistently rate the "explanation of charges" dimension lower.

Signal 5: Prior low CSI on previous visits
Customers who rated the store below threshold on a previous visit have a shorter trust balance. An RO that goes smoothly for a first-time customer may be enough to tip a returning low-scorer into a heat case.

How to build heat case escalation into the daily workflow

The escalation workflow has to be proactive and systematic — not dependent on an advisor recognizing a problem and escalating voluntarily. Advisors are under pressure to close ROs, not to surface their own failures. Heat case catching requires a manager review step that is built into the daily cadence.

Morning stand-up (10 minutes, before the floor opens):
Review every open RO from the prior day that is carrying into today. Flag any where the promised time was missed and no customer contact was logged. These are highest-heat-risk: customer was left with an open loop overnight.

Midday scan (10–15 minutes, around noon):
Review the day's RO board for any RO where the promised time has moved by more than one hour and no outbound notification is logged. Call or text the customer immediately with a revised time and explanation. This single step, consistently executed, prevents the largest single category of heat cases.

Afternoon pre-close check (30 minutes before advisor shift end):
Review any RO that's received more than one inbound contact from the customer. If the customer has called or texted twice without a resolution, a manager — not the advisor — should make the next contact. The customer has already experienced one failed touchpoint; escalating the contact level signals that the store is taking it seriously.

Post-survey heat case debrief:
When a low CSI score arrives, reverse-engineer the RO. Which signals were present? When did they appear? Who was assigned and what did they do? Use this to calibrate which signal combinations are most predictive at your store. The pattern varies by rooftop — a store that runs a tight BDC function will have different leading signals than one that handles all status calls through advisors.

For Fixed Ops Directors who want to benchmark what a complete escalation workflow looks like against industry averages, the operator reporting dashboard provides breakdowns of inbound contact patterns by RO — useful for identifying which signal types are most prevalent before building the escalation criteria.

Measuring heat case prevention

The primary metric is CSI score on the "kept informed" dimension — typically the leading indicator of overall CSI movement. Secondary metrics:

• Heat case catch rate — what percentage of low CSI ROs had at least one intervention logged before the survey was sent

• Inbound contacts per RO — as heat case prevention improves, this ratio should decline because fewer customers are reaching out to fill information gaps

• Promised-time accuracy — percentage of ROs completed within 30 minutes of the promised time

A Toyota dealership in the Mountain West tracked these metrics after implementing a midday manager scan. Within 90 days, their "kept informed" CSI score moved from the 62nd to the 81st percentile in their region. The change wasn't in Fixed Ops capacity or headcount — it was in the systematic identification of trust deficits before the customer hit the survey.

How Numa solves this

The heat case detection problem is fundamentally an information aggregation problem. The signals are present in every store's data — in the phone logs, the message threads, the DMS timestamps — but they're distributed across systems that no advisor or manager can monitor simultaneously.

Numa's AI platform monitors conversation patterns across all inbound channels and surfaces heat case risk signals in real time. When a customer sends a second message before receiving a reply, when an inbound call is missed, or when an RO's promised time moves without a corresponding outbound notification, Numa flags the RO in the Fixed Ops team's smart inbox for manager review — before the customer's next contact.

For a multi-rooftop Dodge Chrysler Jeep Ram group in the Southeast, Numa's heat case flagging surfaced 23% of low-CSI ROs before the survey was sent. In 14 of those cases, a manager contact was made and the customer's survey score was above threshold. That's the ROI of early detection: preventing the score from landing, not analyzing it after the fact.

If you're evaluating how to structure the daily workflow around heat case signals, the piece on proactive service status updates covers the upstream fix — eliminating the silence that generates heat cases in the first place.

FAQ

Q1: What's a heat case?

A heat case is a customer whose dissatisfaction is building before it surfaces in a complaint or survey. The term distinguishes customers who are absorbing friction silently — and will express it in the CSI survey — from customers who escalate immediately. Heat cases are more damaging because they're invisible until the survey, by which point the relationship and the score are already set.

Q2: How early can a heat case be detected?

The first signals typically appear within two to four hours of check-in. A customer who calls for status before noon on a same-day RO, receives no answer, and doesn't get a callback is carrying heat case risk from that point. Well-designed Fixed Ops workflows can catch this within the same business day — well before the vehicle is ready and the survey is triggered.

Q3: Who should own heat case escalation?

The Fixed Ops manager or service director — not the advisor who owns the RO. Advisors are too close to the transaction and under too much pressure to admit a problem. A manager making a proactive call to a heat-risk customer signals escalated attention. The customer feels heard before they've had to complain. Advisor-owned escalation can work for minor recoveries, but systematic heat case management requires manager involvement.

Q4: What's the ROI of heat case prevention?

A single CSI point improvement in OEM rankings can affect dealer incentive payouts significantly at franchise stores. Beyond the direct financial impact, a customer recovered before the survey has a materially higher retention probability for both Fixed Ops and future sales. Customers who experience a problem and a recovery often have higher loyalty than customers who never experienced a problem — this effect is well-documented in service recovery research.

Q5: Can heat cases be prevented or only managed?

Both. The upstream prevention — proactive status updates, accurate promised times, real-time communication of changes — eliminates the friction that creates heat cases. The downstream management layer — daily signal review and manager escalation — catches the heat cases that still form despite good upstream practices. Strong Fixed Ops departments run both. Prevention reduces the frequency; detection limits the damage.