Every store in this article had the same starting condition. Declined service tickets in the DMS. No systematic process to follow up. Revenue walking out of the service lane every month without being recovered.
The volume varied. The problem was identical. Customers came in. Advisors wrote up repair recommendations. Customers deferred some of those repairs. The declined items were logged. And then nothing happened.
One store had months of declined service records with no outreach on file. Not because the team did not care. Because there was no trigger. No system that made the follow-up happen automatically. The work of contacting those customers sat in a gap between what advisors were responsible for and what the BDC was resourced to handle at speed.
At $450 average repair order value, even a store with 100 declined tickets per month is sitting on $9,000 in potentially recoverable Fixed Ops revenue. At 200 tickets per month, that number doubles. None of it converts without a contact.
Each of these stores made one structural change. They connected their DMS-based declined service events to an automated outbound workflow. When an advisor marked a service item as declined and closed the RO, the system triggered a personalized outbound message to the customer within 48 hours.
The message was not generic. It referenced the specific repair that had been declined, the customer's vehicle, and the date of the visit. It offered a direct path to schedule. Replies routed to a service team member for handling.
No manual export. No end-of-month call list. No generic service marketing email. The trigger fired at the declined ticket event, automatically, at the moment the opportunity was still warm.
The 48-hour window is not arbitrary. It reflects when customers are most likely to respond. Within two days of the visit, the repair recommendation is still fresh. The customer remembers the advisor and the conversation. The cost estimate is still in their inbox or written on the service receipt. That is the moment when outreach feels like a natural follow-up rather than a cold contact.
Before the case study detail, it is worth being direct about the limits of this approach. These stores saw strong results. The results were not universal across every customer interaction.
Automated outbound performs well for customers who deferred a repair for practical reasons: scheduling constraints, cost timing, or simply being rushed that day. For those customers, a timely and specific reminder is often all that is needed.
Automated outbound is less effective for customers who had a negative experience during the visit, who are in a financial situation that makes any repair timing genuinely difficult, or who declined for a reason they want to discuss with someone. Those situations require a human conversation, and the better-designed systems escalate those customers to a BDC rep or service advisor rather than continuing with automated messages.
The practical implication is that a well-designed system is not fully automated. It is automated at the top of the funnel and human at the point of complexity. Stores that set up escalation paths correctly see higher overall conversion rates than stores that treat every declined ticket as purely automated.
These questions come directly from Fixed Ops Directors who went through the evaluation process before these results were achieved.
Does the system trigger automatically from the DMS, or does someone have to initiate it?
The timing advantage disappears if a human has to export a list or manually start the campaign. The trigger must fire from the DMS event without human intervention.
What is the lag between the declined ticket and the first message?
Same-day or next-day is the target. Ask vendors to confirm the actual message delivery window, not the theoretical capability. A 48-hour commitment should be verifiable.
How does the system handle customer responses?
Every tool that sends outbound messages also generates replies. Ask specifically how those replies are routed, who sees them, and how quickly. A customer who replies with "how much would that cost?" and hears nothing back is worse than a customer who was never contacted.
Can the system track from declined ticket to completed RO?
Attribution is the only way to measure whether the program is working. If the tool cannot connect the outbound message to the downstream RO close, the Fixed Ops Director cannot quantify the recovery rate. This is a non-negotiable requirement for a program that is supposed to generate measurable revenue.
What happens at 90 days if the customer has not responded?
Some customers will not convert in the first follow-up. Ask what the recommended cadence looks like and when the system stops reaching out. Continued messaging to a non-responding customer generates opt-outs. A defined endpoint is part of a responsible outbound program.
These two stores operated in the same region. They were part of a coordinated rollout of automated outbound connected to declined service triggers. Both stores had existing declined service volume and no systematic follow-up process in place.
In month one, the combined result was 211 incremental ROs. Both stores were recovering the same types of declined service items: fluid services, brake components, tire work, and scheduled maintenance that had been deferred.
The math on those 211 ROs is direct. At $450 average repair order value, that is $94,950 in Fixed Ops revenue from a single month of automated follow-up. Neither store hired additional staff to achieve that result. The change was the system, not the headcount.
The velocity in month one was notable. The declined service records had been accumulating without outreach. Once the trigger was live, the backlog of warm leads converted at a rate that reflected how long those customers had been waiting for a follow-up that never came. Month two and subsequent months stabilized at a lower but sustained incremental rate as the backlog cleared and the program shifted to ongoing declined ticket recovery.
A separate Chevrolet dealership tracked the impact of automated outbound over a full 12-month measurement period. At the end of that year, Fixed Ops revenue was 25% higher than the prior year.
More significant than the revenue growth was the efficiency metric. That store reached the highest dollars-per-RO in its region. The program did not just add volume. It improved the quality of the ROs being completed because the customers coming in for declined service follow-up were completing the repairs they had originally deferred. Those are not oil change tickets. They are brake jobs, fluid services, and inspection items that carry higher average revenue.
A 25% year-over-year improvement on Fixed Ops revenue represents a structural change in the department's output. It is not a one-month spike. It reflects a sustained increase in recovery rate across a full year of declined service volume.
A multi-rooftop dealer group tracked its full-year 2025 results. The total incremental revenue from automated outbound campaigns, measured across Fixed Ops and parts, was $1.5 million.
At scale, the math works differently. The per-store numbers are similar to the single-point examples above. Across multiple rooftops, those recoveries accumulate. The group-level result reflects what happens when the system runs consistently across a high volume of declined tickets and appointment follow-ups month after month.
The parts revenue component is worth noting. Declined service recovery does not only add labor revenue. When a brake job or suspension repair is completed, parts revenue follows. Stores that track the full downstream impact of declined service recovery consistently find that the parts contribution adds 15 to 30% on top of the base labor recovery calculation.
The common thread across all three results is structural: a trigger that connects the declined service event in the DMS to a personalized outbound message within 48 hours, tracked to RO close.
No-show prevention adds another layer. At a 20% no-show rate and $450 per open RO, preventing 10 no-shows per month recovers $4,500. That runs alongside declined service recovery as a parallel program using the same automated outbound infrastructure.
The aggregate impact across a store with 200 declined tickets per month and 20 monthly no-shows is material. Recovering 20% of declined tickets adds $18,000 per month. Preventing 10 no-shows adds $4,500. Combined: $22,500 per month in Fixed Ops revenue that was previously leaving without being captured.
Numa is the tool behind each of the results documented in this article. Automated outbound connected to the DMS, triggered at the declined service event, personalized by vehicle and repair type, tracked to RO close across every store in the group.
See how three stores turned declined service into booked ROs and calculate what that recovery rate would be worth at your store.
Q: How does Numa's Voice AI Operator improve declined service follow-up for automotive dealerships?
A: Numa's Voice AI Operator automates outbound calls to customers who have declined recommended services, ensuring timely and consistent follow-up. This reduces the risk of lost revenue by re-engaging customers, resulting in measurable increases in repair orders (ROs) and fixed operations revenue without adding workload to dealership staff.
Q: What impact can Numa's customer operations automation have on dealership fixed ops revenue?
A: Dealerships using Numa’s customer operations automation platform have seen significant improvements, including a 25% year-over-year increase in fixed ops revenue. By systematically recovering declined service through automated outreach, dealerships capture incremental revenue that would otherwise be lost, enhancing overall profitability.
Q: Why is communications automation important for managing declined service in automotive service lanes?
A: Communications automation, powered by Numa’s Voice AI, ensures that declined service follow-ups are timely, personalized, and consistent. This removes the manual burden from service advisors, closes the communication gap with customers, and improves customer satisfaction by proactively addressing their service needs.
Q: Can Numa’s Voice AI for fixed ops recovery be easily integrated into existing dealership systems?
A: Yes, Numa’s Voice AI Operator is designed to seamlessly integrate with dealership management systems (DMS), enabling automated triggers for declined service follow-up. This integration streamlines customer operations, allowing dealerships to efficiently manage communications and recover lost revenue without disrupting daily workflows.
No more hold music. No more unanswered voicemails. Your customers are top priority.
