How Many Calls Does an Auto Repair Shop Actually Miss? Run This 15-Minute Count
A practical 15-minute call-log audit for measuring overflow, lunch, closing-rush, and after-hours calls without relying on industry averages.
Ask three people in the same shop how many calls go unanswered and you will usually get three different answers. The owner remembers the calls that ring while everyone is under a car. The advisor remembers the lunch rush. The phone bill may show dozens of calls, but it does not explain which ones were customers, which ones reached voicemail, and which ones called again. That uncertainty makes it easy to dismiss missed calls as an occasional nuisance or inflate them into a dramatic revenue number. Neither helps. The useful number is the one your own phone system can show you. Give the count 15 minutes, separate calls by when and why they were missed, and then decide whether the problem is staffing, routing, follow-up, or coverage. You do not need a consultant, a call-tracking project, or an industry benchmark. You need a representative call log and a simple definition of a missed opportunity.
Nobody knows until they count
A busy shop is a bad place to estimate phone performance from memory. The calls people remember are usually the disruptive ones: a tow request during write-up, a ringing phone while an advisor is checking in a customer, or a no-start message discovered the next morning. Quiet losses are harder to notice. A caller may hang up before voicemail, call a competitor, or try again from another number. Even answered calls can be functionally missed when the employee says, "Can you call back later?" without collecting a name, vehicle, concern, and callback number. Start by defining the event you want to measure. For this audit, count a missed opportunity when an external caller seeking service does not complete a usable intake during the original call. That includes unanswered calls, abandoned calls, voicemail-only calls with insufficient detail, and answered calls that end without enough information for an advisor to follow up. Do not count spam, vendor calls, employee calls, duplicate redials from the same customer, or calls that successfully transferred to the right person. The goal is not to produce the largest number. It is to find the calls that created work for the customer but did not create an actionable record for the shop.
The three missed-call buckets
Put each missed opportunity into one of three buckets. The first is daytime overflow. These are calls that arrive while the shop is open but the counter is already occupied, the advisor is on another line, or the team is working away from the phone. Overflow is usually a concurrency problem, not a motivation problem. The second bucket is the lunch and closing rush. Do not assume those periods are a problem; use the call log to see whether misses actually cluster when staffing is thinnest or close approaches. A phone that is covered at 10:30 AM may be effectively uncovered at 12:15 PM or five minutes before closing, but your own time bands should prove it. The third bucket is structural closed time. A week contains 168 hours. A shop open 50 hours is dark for the remaining 118 hours. That 118-of-168 figure is schedule math, not a claim that calls arrive evenly or that every closed-hour call is valuable. It simply shows why an employee who covers the posted business day cannot also cover the full week. Nights, early mornings, weekends, and holidays should be measured separately because the right response may be different. A routine maintenance request can wait in a morning queue. A stranded caller, tow request, no-start, brake concern, or overheating report may need a configured text or transfer rule.
The 15-minute CDR count
Open the call detail record, or CDR, in your carrier or business-phone portal. Use at least seven recent days; fourteen is better if the export is already available. Filter to inbound calls on the main shop number. In the first 15 minutes, mark calls answered by a person or completed through an existing answering workflow, then isolate no-answer, busy, abandoned, forwarded, and voicemail outcomes. Remove obvious spam, internal calls, vendors, and duplicate redials. If the first pass shows a meaningful gap, do the slower reconciliation: compare the remaining caller IDs with appointments, repair orders, callback notes, or voicemail records. You are looking for external callers who did not leave the shop with a usable next step. Finally, label each one as overflow, lunch or closing rush, or structural closed time. If a line is ambiguous, mark it unknown instead of forcing it into the missed column. Record four numbers: total inbound service calls, completed intakes, missed opportunities, and unknowns. Then note the time bands where misses cluster. A raw miss percentage without time context is less useful than knowing that six of seven misses occurred between noon and 1 PM. Repeat the same count in another week before changing staffing. One unusual storm, holiday, or local event can distort a short sample.
Turn the count into dollars without fooling yourself
Use a formula, not a promise: qualified missed calls per week multiplied by the share you can successfully reach and intake, multiplied by the share of those intakes that book, multiplied by your average repair order. Keep the inputs separate. A missed vendor call is worth zero. A customer who already called back and booked should not be counted twice. A booked appointment is not the same as completed revenue, and gross repair-order value is not profit. Here is an explicitly hypothetical, conservative illustration, not an AutoShop Voice customer result or an industry benchmark. Suppose a shop identifies 3 to 10 qualified missed calls in a week. It assumes only 50% to 70% would complete an intake when answered, only 20% to 30% of those would ultimately book, and the shop's own average repair order is $250 to $450. The formula produces a broad gross booked-work range of $75 per week at the low end to $945 per week at the high end. That range is intentionally wide because the inputs drive the result. It does not account for cancellations, no-shows, parts, labor, capacity, repeat visits, or customer lifetime value. Replace every hypothetical input with your own data. If the result only works after using an aggressive booking rate or inflated repair order, the business case is weak. If conservative inputs still cover the cost of a coverage solution, test it and measure completed work rather than estimated leads.
Why voicemail does not rescue the call
Voicemail records audio; it does not guarantee intake. Some callers will leave a complete message. Others will leave a first name and "call me back," omit the vehicle, or hang up without recording anything. The advisor then has to replay the message, write down the number, return the call, reach voicemail, and start the intake from zero. That is not a recovered call yet. It is a callback task competing with walk-ins, technicians, parts questions, and the next ringing phone. Voicemail also removes triage from the moment when the caller can answer follow-up questions. "My car will not start" could mean a vehicle in a driveway, a fleet unit blocking a route, or a driver stranded on the shoulder. The recording does not ask whether the engine cranks, where the vehicle is, whether it is safe, or when it must be moving. A voicemail can still be useful evidence and should remain an available fallback, but it is a thin handoff. When you audit the call log, do not automatically classify every voicemail as saved. Check whether it contained enough information to create an actionable callback and whether the team actually made contact.
What 24/7 answering changes, and what it does not
A 24/7 answering layer changes the first response. Instead of sending an overflow or closed-hours caller directly to a recording, it can ask for the caller, callback number, vehicle, concern, drivability, urgency, and preferred timing. It can place routine requests in a dashboard queue and apply shop-configured escalation rules to urgent language. AutoShop Voice is built for that intake and handoff role. It can also support appointment requests or direct booking where the shop has configured the appropriate workflow. It does not replace the shop management system, diagnose the vehicle, guarantee that every caller books, or eliminate advisor judgment. By default, it works upstream of Tekmetric, Shop-Ware, Mitchell 1, Shopmonkey, or a manual process. The advisor reviews the record, checks capacity, resolves missing details, confirms the appointment, and closes the work. That distinction matters when measuring results. Calls handled is an operating metric. Complete intakes is a better metric. Confirmed appointments and completed repair orders are the business metrics. The answering layer creates more usable opportunities and a cleaner queue; the advisor still owns follow-up, scheduling, quoting, and the customer relationship.
Run the count before buying software or adding payroll. Pull one representative call log, remove noise and duplicate redials, and sort the remaining misses into overflow, lunch or closing rush, and structural closed time. Then apply your own booking and repair-order numbers with conservative assumptions. You may discover a small routing problem that a phone-system change fixes. You may find a predictable lunch gap. You may find that most missed opportunities occur during the 118 hours a 50-hour shop is closed. The answer should determine the remedy. Whatever you find, keep the standard simple: a call is not rescued until the shop has a usable intake and a real next step.
What is a normal missed-call rate for an auto repair shop?
There is no repository-backed universal rate that is honest to apply to every shop. Call volume, staffing, phone routing, business hours, season, and the mix of fleet and consumer work all change the result. Establish your own baseline from at least one representative week, repeat the count, and track missed opportunities by time bucket instead of comparing yourself with an unsupported industry percentage.
Do after-hours callers actually book appointments?
Some do, but there is no honest universal conversion rate to promise. After-hours answering preserves the opportunity by capturing the vehicle, concern, urgency, preferred timing, and callback details while the caller is engaged. The advisor still has to review availability, confirm the appointment, and close the work. Track confirmed and completed jobs from your own after-hours queue.
Why not hire another front-desk person?
Hiring may be the right answer when the shop needs another person for in-store customers, estimates, parts coordination, and full-time advisor work. One additional shift does not cover all 168 hours in a week, and it may not solve short bursts when several calls arrive together. Compare the actual gap with the job you need done. Use staff for judgment-heavy work and use overflow or after-hours coverage where the problem is availability.
How can I count missed calls if we use a basic landline?
Ask the carrier for an itemized inbound call log or access to its customer portal. Some landline providers expose answered, busy, and no-answer records; others require support to provide them. If no CDR is available, keep a seven-day manual tally beside the phone and compare it with caller ID, voicemail timestamps, and repair-order records. The same carrier can usually explain conditional forwarding for busy, no-answer, or closed-hours coverage.