Numa automates the four-touchpoint status update cadence — drop-off confirmation, MPI notification, delay alert, and ready-for-pickup — by pulling directly from the DMS so updates fire the moment the repair milestone hits, without requiring advisor action. The Status Updates product removes the repetitive status calls that chew up advisor time while keeping advisors in every approval and relationship conversation that matters. For Fixed Ops Directors managing volume-heavy operations, this is the layer that keeps the proactive cadence from slipping when the drive gets slammed.

Service Status Update Best Practices: What Top Stores Do Differently

Most fixed ops teams send status updates the same way: when the customer calls and asks. The advisor stops what they're doing, checks the repair order, and gives a verbal summary — then does it again 90 minutes later when the same customer calls back. This reactive pattern costs advisors time, frustrates customers, and drives CSI scores down.

Top-performing fixed ops operations do the opposite. They send updates on a fixed cadence — regardless of whether the customer has called — and they use a defined channel hierarchy to match how each customer actually wants to receive information. The result is fewer inbound calls, higher customer satisfaction, and advisors who spend more time on the drive than on the phone.

The framework isn't complicated. It comes down to four scheduled touchpoints, a clear channel preference system, and scripted messages that communicate progress even when nothing dramatic has happened. Here's how it works.

Why Reactive Status Updates Create More Work, Not Less

The intuition behind reactive updates is reasonable: don't bother the customer until you have something to tell them. The problem is that customers don't know when you'll have something to tell them. So they call.

Each inbound call from a waiting customer takes an advisor 3–5 minutes to handle: locate the RO, find the technician's current status, formulate an answer, communicate it, and field any follow-up questions. At a busy fixed ops operation running 30–40 ROs per advisor per day, that adds up to an hour or more of advisor time consumed by customers who simply want to know what's happening with their car.

The calls also arrive at the worst moments — when the advisor is walking a vehicle, writing up a new customer, or in the middle of an approval conversation. Each interruption breaks focus and slows the write-up lane down.

Here's the counterintuitive reality: sending a proactive update at 10 AM eliminates the 10:30 AM inbound call. The customer already knows what you would have told them. They don't need to call. Studies on Fixed Ops communication consistently show that customers who receive proactive updates call back at roughly half the rate of customers who don't.

The Proactive Cadence Top Stores Use

Top fixed ops operations structure updates around four defined touchpoints:

1. Drop-off confirmation (within 15 minutes of RO creation)
The customer just handed over their car. A quick confirmation — "We've got your vehicle checked in and your advisor is [Name]. We'll update you when the inspection is complete" — sets expectations and reduces anxiety immediately.

2. Inspection complete / multipoint results (within 30 minutes of tech completing MPI)
This is the highest-value touchpoint. The customer learns what was found and what the advisor recommends. Proactive delivery here means fewer "did you find anything else?" calls later. It also creates a natural window for the advisor to walk the customer through approval rather than chasing them down.

3. Work-in-progress update (if wait time exceeds the original estimate by 30 minutes)
Delays happen. Customers who hear about delays proactively react significantly better than customers who call and discover the delay themselves. The message doesn't need to be elaborate — "we've hit a wait on a part and your vehicle will be ready by 3:30 instead of 2:00" covers it.

4. Ready for pickup
Simple and direct. Time-stamp it. Include the total. Tell the customer where to go when they arrive.

Four touchpoints. Four messages. Most customers get two to three of these per visit, depending on whether a delay occurs. Advisors who adopt this cadence consistently report fewer inbound status calls within the first two weeks.

Channel Selection: When to Text, Call, or Email

The channel hierarchy at top fixed ops operations follows one principle: meet the customer where they prefer, default to text.

Text: Best for transactional updates — drop-off confirmation, MPI results, ready notification. Short, scannable, and doesn't require the customer to be free to receive the information. Customers can reply with approval on multipoint recommendations without calling back.

Phone call: Reserved for complex conversations — significant unexpected repairs, safety-critical findings, or anything requiring a detailed explanation and consent. When the repair cost is going to surprise the customer, the advisor should call, not text. The human voice carries nuance that a text message can't.

Email: Useful for summary documentation — a post-visit copy of what was completed, what was deferred, and what's coming due next. This isn't a real-time channel, but it creates a paper trail the customer values and often shares with a family member who makes vehicle decisions with them.

At intake, the service advisor should confirm channel preference explicitly: "We'll send you a text when your inspection is done and again when the car is ready — is [phone number] the best number for that?" Most customers say yes. The ones who want calls will tell you.

For more on structuring the advisor-to-customer communication workflow, see our service advisor communication framework.

What to Say at Each Touchpoint

The content of a status update matters, but not as much as most advisors think. Customers aren't looking for a novel — they're looking for three things: confirmation that something is happening, a timeline, and a next step.

Drop-off confirmation:
"Hi [Name], this is [Advisor] at [Store]. Your [vehicle] is checked in and we'll have the inspection done by around [time]. I'll text you the results when we're finished."

MPI complete:
"Hi [Name], your inspection is done. [Summarize findings in one to two sentences — e.g., "Everything looks good" or "We found a brake issue I'd like to walk you through."]. I'll give you a call in the next 15 minutes to go over the details." OR include a direct approval link for straightforward jobs.

Delay notification:
"Hi [Name], quick update on your [vehicle] — we're running about [X] hours behind schedule on [job]. New estimated ready time is [time]. Sorry for the delay — I'll reach out as soon as it's done."

Ready for pickup:
"Hi [Name], your [vehicle] is ready. Total today is [$amount]. We're open until [time] — come to [lane/desk] when you arrive and we'll get you taken care of."

No filler. No marketing language. Just the facts the customer needs.

How to Scale This Across a Multi-Store Group

The cadence above works for a single advisor. Scaling it across a multi-rooftop group requires standardization at the process level, not just the message level.

The three places groups break down:

Inconsistent touchpoint timing. One store sends updates at 15 minutes; another waits until the end of the day. Customers who visit multiple stores get inconsistent experiences that erode trust in the group's brand. The fix is a group-level SOP that defines when each touchpoint fires.

Advisor discretion on channel. Left to their own judgment, advisors default to the channel they prefer, not the one the customer requested. Groups need a system that captures channel preference at intake and routes the right message to the right channel automatically.

No visibility across locations. Fixed Ops Directors managing multiple rooftops can't verify that updates are going out unless they have a centralized view of each store's communication activity. A group-level dashboard showing update send rates and inbound call volume by location is the only way to manage this at scale.

A Honda dealership group in the Midwest standardized their four-touchpoint cadence across five stores and tracked inbound service-status calls over 90 days. They reported a 38% reduction in status-inquiry calls within six weeks of rollout — without adding headcount.

For multi-rooftop operations evaluating how to systematize Fixed Ops communication, see how top dealer groups structure their communication SOP.

How Numa Solves This

Manual update cadences work — until the advisor gets slammed. When a Fixed Ops team is running 30+ ROs and three customers are waiting for status calls, the cadence slips. That's when inbound volume spikes and CSI scores drop.

Numa automates the four-touchpoint cadence without removing the advisor from the customer relationship. Drop-off confirmations go out when the RO is created. MPI notifications fire when the tech marks the inspection complete. Delay alerts trigger if the promised time is not going to be met. Ready notifications go out the moment the RO is closed.

Advisors set their preferences and the communication layer runs behind them. They still handle every approval conversation, every complex repair discussion, and every customer who wants to talk. The repetitive status calls — the ones that chew up advisor time without adding value — get handled before the customer picks up the phone.

For Fixed Ops Directors managing volume-heavy operations, see how Numa's status update automation fits into an existing advisor workflow.

Frequently Asked Questions

How often should a customer get a status update?

Most customers need two to four updates during a standard service visit: a drop-off confirmation, an MPI result notification, a delay alert (if applicable), and a ready-for-pickup message. More than four updates in a single visit starts to feel like noise. Fewer than two creates the vacuum that drives inbound status calls. The cadence should be tied to actual milestones in the repair process, not a fixed hourly schedule.

Should status updates come from the advisor personally?

The approval conversation and any complex findings should come from the advisor directly — those calls carry relationship weight. Transactional touchpoints (confirmation, ready notification, delay alert) can come from an automated system with the advisor's name attached. Customers don't distinguish between a text from "Mike at [Store]" sent manually versus one sent automatically. What they notice is whether the update arrives — not who pressed send.

Do customers prefer text, call, or email for status updates?

Roughly 70–80% of customers prefer text for transactional updates, based on Fixed Ops communication data across high-volume dealerships. Calls are preferred for significant repair findings or cost surprises. Email works as a follow-up summary after the visit but not as a real-time channel. Confirming preference at intake and recording it in the customer record is the only way to get this right at scale.

What if there's no real update to share?

Send the update anyway. "Your vehicle is in the queue and we expect the inspection to start around [time]" is a real update. Customers aren't looking for news — they're looking for evidence that someone is paying attention to their car. A brief, factual message confirming that the work is progressing on schedule prevents the customer from assuming nothing is happening and reaching for the phone.

How do status updates impact CSI?

Communication is consistently the top driver of Fixed Ops CSI scores, ahead of wait time and price. Customers who receive proactive, timely updates rate their service experience higher even when the wait time is longer than expected. The key mechanism is perceived control — customers who know what's happening feel less anxious and more satisfied. Dealers who implement a four-touchpoint proactive cadence typically see CSI lift within 30–60 days, before any other operational changes.