Are Overwhelmed Service Advisors Costing the Shop Sales?

Three counts from one ordinary week

Pick a week without a holiday, a missing advisor or a storm, and count three things. None of it needs new software; a printout and a pencil will do for the first pass.

• Calls. Export the phone system’s call log for the week and total answered and unanswered calls by hour and by line, if the system records those fields. Separate calls that reached voicemail from calls that hung up before it, and mark which unanswered numbers got a call back the same day.
• Approvals. For every repair order where the customer had to approve an estimate, write down when the estimate went out, when the customer decided, and how many times the shop tried to reach the customer in between. Where the shop management system timestamps job status, it holds these times; where it does not, the advisor’s notes do.
• Cars. At the same time every morning, count the cars on the property and write one status next to each: waiting for diagnosis, waiting for the customer’s approval, waiting for parts, in a bay, or finished and waiting for pickup. Add the day each car arrived.

The car count has a useful property. Averaged over a few weeks, the number of cars on the property comes close to the cars delivered per day multiplied by the average days each car stays. In queuing theory this is Little’s Law, and John D. C. Little’s 2011 review of it in Operations Research names auto repair among its everyday examples. Turned around, average days in the shop is the average morning count divided by the cars delivered per day. Illustrative example: a hypothetical shop that delivers 10 cars a day and averages 30 cars at the morning count keeps each car about 3 days. If the average stay drops to 2 days at the same 10 cars a day, the morning count falls to about 20, and those 10 spaces were holding cars that were waiting, not being worked on.

Service advisor to technician ratio: measured, not borrowed

This guide found no government or academic source for a service advisor to technician ratio, and a ratio quoted without the count behind it cannot be checked against one shop’s work. A ratio is really a statement about two things: advisor minutes per repair order, and repair orders per technician per day. Both move with the shop’s work mix.

The measured version uses the same week. From the call log and the repair orders, the advisor’s day splits into minutes per repair order (write-up, estimate, approval calls, status calls, pickup and payment) and minutes on calls that never become a repair order (price questions, scheduling, parts vendors, wrong numbers). A tally sheet at the counter for two or three days fills in what the systems do not record. Then work it in four steps:

• Real counter minutes per advisor per day: the scheduled day, less lunch and the chores that land at the counter but belong to no customer, such as signing for parts deliveries.
• Less the minutes spent on calls that do not become a repair order.
• Divided by advisor minutes per repair order: the repair orders one advisor can carry in a day.
• Divided by repair orders per technician per day, from last month’s count: the technicians one advisor can support.

Illustrative example, not a client: an advisor has 420 real counter minutes a day, spends 60 of them on calls that never become a repair order, and the sample shows 24 minutes per repair order. That advisor can carry about 15 repair orders a day. If each tech averages 3 repair orders a day, the advisor supports about 5 techs. If the 24 minutes held, a maintenance-heavy mix at 5 per tech would mean about 3 techs, and long diagnostic and engine work at 1.5 per tech about 10. A six-tech shop at 3 repair orders per tech writes 18 a day, three more than one advisor can carry: about 72 minutes of counter work a day with nowhere to go, and it comes out of the phone and the approval calls. The shop’s own numbers replace every figure here.

Call center, another advisor or a different phone routine

Whether to hire a call center is the right question to ask after the counts, not before them, because the three options fix three different patterns.

• Misses cluster in the rush windows, and the capacity count shows room the rest of the day: change the phone routine first. Stagger the advisors’ start and end times so two people cover drop-off and pickup, name who answers when the advisor is with a customer (a second advisor, the shop foreman or the owner), and keep one callback list worked at set times every hour.
• Misses spread through the whole day, and the capacity count shows more repair orders than the counter can carry: add a person. That person need not be a second full advisor. Someone who answers, schedules and makes status calls, without selling repairs, takes the minutes that do not need an advisor’s judgment and leaves the advisor the estimates and the approvals.
• Misses fall at lunch, after closing or in short bursts nobody can predict: an outside answering service or call center, or software that answers the phone, including the AI voice tools sold to shops. Ask one question before price: can it book into the shop’s schedule, or does it take a message? A message is a callback someone still has to make, so it needs a named owner and a time.
• Calls get answered and still do not book: none of the three fixes that. The counter’s script and the lost-lead sheet below do.

Price each option against the shop’s own count, not a vendor’s average: unanswered calls from new customers a month, times the share that book when answered, times the average repair order. The free missed-call cost calculator runs that arithmetic from four numbers, and the guide to what a missed call costs, linked at the end, explains each input.

How to track lost leads: calls and walk-ins that never became an RO

A lost lead is any inquiry that did not become a repair order: a call that booked nothing, a walk-in who left with a price and no appointment, an online request nobody confirmed. The unanswered calls from the phone log are the first group, and they reach nobody’s sheet unless someone pulls the log. The rest need a line written when they happen, because by Friday nobody remembers them. One line per lost lead:

• Date, time and channel: phone, walk-in, website or text.
• New customer or existing, and the vehicle.
• What the customer wanted, in a few words.
• Why it did not become a repair order: price, no appointment soon enough, work the shop does not do, waiting on the customer, or no answer and no callback.
• Who handled it, and whether anyone followed up.

Who decides the reason matters as much as the sheet: whoever decides what counts as a lost lead controls the count, so the advisor writes the line and the owner reads the sheet and a sample of the week’s voicemails. Then three numbers tell the story: inquiries, appointments booked, repair orders opened. A stack of no-appointment-soon-enough reasons is a capacity finding, not a price finding, and it points back to the counts above.

Why cars sit for days, and who owns moving them

A car that sits for days without being touched is waiting on something, and the morning count says what. Each status has its own cause and its own owner, and a car stalls when its status has no owner or no time limit.

• Waiting for diagnosis: the car arrived without a slot, or into a day that was already full. Owner: whoever dispatches work to the bays, whether a shop foreman, a lead tech or the advisor. Limit: a start time set at check-in, and a call to the customer if it slips.
• Waiting for approval: the estimate went out and the customer has not answered. Owner: the advisor who presented it. Limit: a second contact by a set hour, and a decision recorded by the end of the day: yes, no, or a date. Recording the yes is its own step, and the authorization log in the guide to extra repairs covers it.
• Waiting for parts: ordered, not here. Owner: whoever orders parts. Limit: an arrival check at open every morning, and a call to the customer that same morning when the date moves.
• In a bay but stopped: the tech found something new mid-job. Owner: the advisor for the call to the customer, the dispatcher for what the tech works on meanwhile.
• Finished, not picked up: the work is done and the customer has not been told, or has not come. Owner: the advisor. Limit: a call within the hour the car is finished.

Who pays for the wait depends on the pay plan. The Bureau of Labor Statistics notes that “Some repair shops pay technicians on an hourly basis, while others pay them based on the amount of work completed.” Under the first, a tech standing beside a car waiting on approval is paid for hours that bill nothing; under the second, the wait earns the tech no flagged hours and the shop carries the idle bay. The guide to technician efficiency counts those hours. Either way, the habit that moves cars is the morning count with a status and an owner next to every car: any car past its limit gets a name and a next step before the first drop-off of the day.

What to check every Friday

Once the first week is counted, five lines on one page keep the counter visible. Each line has a name next to it.

• Unanswered calls in the morning and evening rush windows, and how many got a callback the same day.
• Hours from estimate to the customer’s decision: the median, and the five longest with the reason.
• The morning car count by status, and every car past its limit in one status.
• Lost leads by reason, with no-appointment-soon-enough counted on its own line.
• Repair orders written per advisor per day, against the capacity from the measured ratio.

The free Friday Ledger, a six-check weekly sheet, is built for the same habit across the whole business.

When the counter is not the problem, and where the Review fits

If the week’s counts show few misses, approvals decided the same day and a steady morning count, the counter is keeping up, and any money leaving the shop is leaving somewhere else: hours clocked and not billed, a labor rate set below cost, declined work with no follow-up date. If an advisor left last month and the misses started then, the answer is a hire, not a study. And in a small shop where the owner writes every repair order, the owner already knows where the day goes; the counts above take an afternoon.

For a shop where the counts are unclear or the systems disagree, The Revenue Review covers this under the Inquiry → Quote hand-off and the approval step after it. With read-only access to the phone system’s call log, the appointment book and the shop management system, it counts unanswered calls by hour, hours from estimate to decision and days in the shop by status, and puts a monthly dollar figure on each wherever the records support one. Nobody here runs a repair shop, and the Review trains no advisors. It takes two weeks, and the report is the shop’s to keep.

The next step is a free 20-minute call, where we say plainly whether the Review is worth it for this shop, including when it is not.