Numa's communication layer removes the primary capacity constraint on service advisors — inbound status calls and administrative follow-up — so advisors can focus on write-ups and approvals. With Numa's Status Updates and Operator tools handling routine Fixed Ops communication, dealerships have seen average RO counts climb from 17 to 23 over 90 days using the same advisors. The path to higher advisor capacity isn't pushing harder — it's redesigning the support structure with Numa.

How Many ROs Should a Service Advisor Handle Per Day?

The honest answer is: it depends — but here are the numbers.

Industry benchmarks put the average service advisor in the range of 15–20 repair orders per day. Top-quartile advisors at well-run fixed ops operations reach 22–28 ROs per day without sacrificing write-up quality or customer communication. The theoretical ceiling in an optimized environment — dedicated phone support, automated status updates, fully staffed service lanes — runs as high as 30–35, but that number requires a support structure most operations haven't built.

The variables that actually determine where a given advisor lands: store volume and workflow design, the advisor's years of experience, whether a BDC or phone support handles inbound calls, and how much administrative work the advisor is responsible for versus offloaded to support staff.

The most important finding from Fixed Ops benchmarking data is this: the gap between average advisors and top-quartile advisors is not primarily explained by technical skill or how fast they write up. It's explained by what the top-quartile advisor is not doing — status calls, administrative follow-up, and inbound phone interruptions. Take those tasks off an average advisor's plate and their RO count typically climbs within 30–60 days.

The Benchmark Range Across the Industry

Fixed ops benchmarks vary by franchise, market, and operation type, but the core data points are consistent enough to anchor a useful comparison:

Entry-level / new advisor (0–2 years): 10–14 ROs per day is typical. New advisors are slower on write-ups, less confident on repair recommendations, and more dependent on supervision. Putting a new advisor into a high-volume environment before they've built their process often hurts both quality and speed.

Mid-level advisor (2–5 years): 15–20 ROs per day. This is the average range and where most operations staff. Advisors at this level have solid process knowledge but may still be interrupted frequently by status calls and administrative tasks that eat into write-up time.

Senior / top-quartile advisor (5+ years, well-supported): 22–28 ROs per day. These advisors have efficient write-up routines, strong customer relationships that reduce re-explanation time, and — critically — they are not spending 45 minutes per day returning status calls.

High-volume outliers: Some advisors in high-support environments — dedicated phone BDC, automated status updates, well-staffed service lanes — report 30+ ROs per day consistently. These are not normal conditions. Replicating them requires the full support stack to be in place.

The franchise matters too. A Honda dealership with predictable, scheduled maintenance volume will see different advisor capacity than a Chrysler Dodge Jeep Ram dealership dealing with a higher proportion of unscheduled and complex repairs. Apples-to-apples comparisons require filtering by franchise and RO mix.

What Variables Actually Affect Advisor RO Capacity

The RO count is the output. The inputs are what Fixed Ops Directors actually control. Six variables move the number in practice:

1. Inbound phone volume absorbed by the advisor. An advisor personally handling 20–30 status calls per day is losing 60–90 minutes of productive write-up time. That's 3–5 ROs per day in capacity, entirely consumed by calls that could be handled another way.

2. Write-up lane workflow. If the advisor is also doing vehicle check-in, loaner processing, and shuttle coordination as part of their role, their effective write-up time shrinks. Stores that separate the physical check-in process from the write-up step see faster advisor throughput.

3. Technician efficiency and communication. An advisor whose technicians are communicating clearly on MPI status, completion times, and parts delays spends less time chasing shop updates. Poor shop communication forces advisors into a manual tracking role that eats capacity.

4. BDC or phone support. Advisors at stores with a functioning BDC or dedicated phone support handling inbound status calls consistently report higher RO counts than advisors at stores where all calls land on the drive. This is one of the most consistent findings in fixed ops capacity benchmarking.

5. DMS and workflow tooling. Advisors who can pull customer history, quote recommendations, and schedule follow-up repairs quickly within their DMS or service tool are faster than advisors navigating a fragmented or slow system. Tool friction is a real capacity constraint and often goes unmeasured.

6. Experience mix on the floor. A floor with two senior advisors and four entry-level advisors will average lower RO counts than a floor with four senior advisors and two entry-level. Experience distribution affects aggregate capacity even when individual benchmarks are being met.

How Top-Quartile Advisors Get to Higher RO Counts

The advisors handling 22–28 ROs per day aren't necessarily faster at writing up a single RO. They've built a workflow that protects their productive time from interruption.

Three consistent patterns across high-output fixed ops advisors:

They batch their communication. Rather than taking every status call as it arrives, top advisors at well-run stores have a system for sending proactive updates at defined intervals. The customer gets a text at inspection completion, another when the vehicle is ready. The advisor doesn't get interrupted mid-write-up because the customer already knows what's happening. See service status update best practices for the specific cadence.

They hand off predictable tasks. Appointment confirmation calls, parts-delay notifications, and routine inquiry calls are not advisor tasks at top-quartile operations. Either the BDC handles them or they're systematized and routed away from the advisor's direct line. This isn't about the advisor being unavailable — it's about protecting advisor time for the tasks that require their specific expertise.

They close the loop at write-up. Top advisors get customer expectations fully set at the point of write-up: estimated completion time, likely cost range, channel preference for updates, and what to do if the estimate changes. Clean intake reduces the number of follow-up calls because the customer's questions were answered before they thought to ask them.

A multi-rooftop Ford dealer group in the Midwest tracked advisor RO counts before and after implementing proactive status updates and dedicated phone BDC support. Average RO counts across their fixed ops advisors increased from 17 to 23 over a 90-day period. No staffing changes — the same advisors, freed from status call volume.

Why Most Advisors Hit a Capacity Ceiling Around 18–20 ROs Per Day

The ceiling isn't usually a skills problem. It's an interruption problem.

At 18–20 ROs per day, an advisor without support structure is managing: 12–15 active customers with cars on-site who may call, 5–8 incoming ROs being written up, and 3–5 customers picking up. At a busy period, that's a lot of simultaneous threads.

The status call is the primary ceiling driver. A customer with a car in the shop has a natural anxiety cycle — they want to know something is happening, and when they don't hear anything, they call. Each call is 3–5 minutes. At 15–20 status calls per day, that's a minimum of 45–100 minutes consumed. That time has to come from somewhere, and it comes from write-up capacity.

The approval conversation is the secondary ceiling driver. Getting a customer to approve a repair recommendation requires reaching them on the first try or losing time to voicemail cycles. Advisors who are regularly playing phone tag on approvals are losing an hour or more per day to non-productive call attempts.

The third constraint is cognitive load. Managing 20+ active ROs simultaneously — tracking status, anticipating delays, remembering which customers want calls versus texts — is mentally demanding. Advisors without a systematic way to manage that load hit capacity not because they run out of time, but because they run out of bandwidth to track the details accurately.

For insight on how Fixed Ops teams benchmark advisor capacity against their peer groups, see how dealer groups evaluate fixed ops staffing structure.

How to Expand Capacity Without Breaking Quality

The levers that move advisor RO counts without sacrificing write-up quality or customer communication:

Take status calls off the advisor. This is the highest-impact lever and the most achievable without a large systems change. A BDC handling inbound status calls, or automated proactive updates sent before the customer calls, can recover 45–90 minutes of advisor time per day. At 15–20 RO per advisor rates, that recovered time often translates to 3–5 additional ROs per day.

Systematize proactive communication. The advisors with the lowest inbound status call volume send the most outbound updates. Counterintuitive but consistent — when customers know what's happening, they don't call to find out.

Clean up write-up lane friction. Walk the write-up process and identify steps the advisor is doing that don't require an advisor. Physical check-in, loaner paperwork, and initial appointment confirmation are candidates for offloading.

Invest in DMS speed. Advisors who can quote, approve, and close ROs quickly within their system have lower per-RO time. If your DMS is slow or requires multiple system switches to complete a standard write-up, the tool is constraining capacity.

How Numa Solves This

The capacity ceiling for service advisors is not a skills problem — it's a task distribution problem. The advisors who handle the most ROs without quality loss do so because routine communication and administrative tasks are not competing for their attention.

Numa's approach is to handle the routine Fixed Ops communication layer — status updates, inbound status calls, appointment confirmations, after-hours scheduling — so the Fixed Ops team is available for the work that requires their judgment. When an advisor isn't spending 75 minutes per day on inbound status calls and voicemail tag on approvals, that time converts directly into additional RO capacity.

For Fixed Ops Directors benchmarking advisor capacity and looking at the operational structure that supports higher RO counts, the question is not how to push advisors harder. It's how to design the support structure so they're not doing work that doesn't require them.

Frequently Asked Questions

What's the industry-average RO count per advisor per day?

The industry average runs 15–20 ROs per advisor per day across franchise dealerships. This range reflects a mix of advisor experience levels, store workflow designs, and varying levels of support staffing. Operations at the lower end of this range typically have advisors absorbing more administrative and communication tasks directly. The average is a floor, not a target — fixed ops directors at well-run operations consistently push their teams above it.

What's top-quartile?

Top-quartile service advisors at well-supported fixed ops operations handle 22–28 ROs per day. Reaching this range consistently requires a combination of advisor experience, proactive status communication that reduces inbound call volume, and BDC or phone support handling routine inbound inquiries. The top-quartile number is achievable at scale — it's not reserved for outlier individuals.

How does store size affect this?

Larger stores with higher daily volume typically have more support infrastructure — dedicated BDC, more service lane staff, better tooling — which enables advisors to focus on write-ups and approvals. Smaller operations often have advisors doing more tasks directly, which constrains their RO count even when their individual skills are strong. The relationship between store size and advisor RO count is mediated by support structure, not store size itself.

Do BDC-supported advisors handle more ROs?

Yes, consistently. Advisors at stores where a BDC handles inbound status calls and appointment scheduling report higher RO counts than advisors at stores without that support. The mechanism is simple: phone time not spent on status calls converts directly to write-up time. The advisors who see the largest gains from BDC support are typically mid-level advisors who were previously absorbing the most phone volume — their RO counts respond most quickly once inbound calls are redirected.

What's the ceiling without sacrificing quality?

The practical ceiling for a fully supported service advisor — automated proactive updates, BDC handling inbound calls, clean write-up lane process — runs around 28–32 ROs per day before quality metrics (CSI communication scores, approval rates, RO accuracy) start to degrade. Above that range, advisors are moving too fast to give each customer adequate attention at write-up. Most operations should target 22–26 for top performers as a sustainable high-water mark, not 30+.