CallNous

Giving exact prices over the phone for non-commoditized work can definitely backfire and reduce the interaction to a price comparison. That said, customers are still going to ask. The real opportunity isn’t in saying yes or no to pricing, it’s in how the conversation is handled. The goal should be to guide the caller, build trust, and move toward an appointment without defaulting to price as the decision factor. That requires consistency, which is where many shops struggle, especially during busy periods or after hours. In practice, the shops that win here aren’t avoiding the question. They’re handling it in a structured way that protects their value while still capturing the opportunity. At the end of the day, this is less about pricing and more about having a reliable front-end process that turns calls into booked work.

This is a solid breakdown of what actually drives profitability in a shop. What stands out is that most of these points assume something important is already happening consistently: that ample opportunities are being captured in the first place. For example, focusing on gross profit over total sales, improving production, and building better estimates all depend on having a steady flow of approved work. But that flow starts much earlier than most shops think. It starts the moment a customer decides to call. The reality is that many shops already have strong demand, full calendars, and good car counts, yet still struggle with cash flow and profitability. As you pointed out, the issue often isn’t a lack of business, it’s how efficiently that business is captured and converted. Where this becomes interesting is at the front end of the process. Missed calls, rushed conversations, or inconsistent handling of inquiries directly impact: how many estimates are created how many jobs are booked and ultimately how much of that potential gross profit is realized If a shop is working hard to improve labor margins, optimize workflow, and increase billed hours, but is still missing inbound opportunities or not handling them consistently, there’s a ceiling on how much those improvements can actually translate into bottom-line results. In that sense, improving profitability isn’t just about pricing, production, or financial awareness. It’s also about ensuring that every potential job actually makes it into the system to begin with. The shops that seem to gain an edge are the ones that treat inbound demand as something to be managed just as deliberately as technician efficiency or inventory. When every call is answered, handled consistently, and turned into a properly booked opportunity, all of the strategies outlined here become significantly more effective. It doesn’t replace the fundamentals you described, it amplifies them. It ensures that the effort put into improving margins, workflow, and estimates actually shows up where it matters most: the bottom line.

This is a strong reminder that attracting the right customers and building trust is what separates good shops from great ones. But there’s an operational gap that often gets overlooked in this conversation. A lot of shops invest time and money into targeting ideal customers, refining their messaging, and improving their reputation. Yet when those same high-value customers actually call the shop, the experience breaks down. Phones go unanswered during peak hours, staff are stretched thin, or after-hours calls simply go to voicemail. At that point, it doesn’t matter how good the marketing strategy is. The opportunity is already lost. If the goal is to attract and retain ideal customers, then every touchpoint has to support that experience. The first interaction is often the phone call. It needs to be immediate, consistent, and handled in a way that reflects the professionalism the shop is trying to project. What’s interesting is that many shops think of this as a staffing problem, when it’s really a systems problem. The shops that are starting to stand out are the ones ensuring that every call is answered, every inquiry is handled properly, and no potential customer slips through, especially during busy or off-hours periods. That doesn’t replace relationships. It protects them. It ensures that all the effort put into attracting the right customers actually converts into real conversations, bookings, and long-term loyalty. In a lot of ways, this is the missing link between marketing strategy and real-world results.

Wonderful, it would be great to meet you Matthew and learn about your business as well.

Thank you for that, what's strange is it's working on my end. It goes to a simple google calendar booking page. Perhaps I switch to Calendly..

Zenas, you're in survival mode right now, I get it. I've been there. A few things that come to mind: You don't have a pricing problem, you have a positioning problem. If customers are shopping you on price, you're attracting the wrong customers. Price shoppers don't build a business, they just keep you busy and broke. $120/hr labor with minimal parts markup means you're competing with the guy down the street who's also desperate. Raise your labor rate to $140-150 and mark parts up 40%. You'll lose the tire kickers. Good...they weren't profitable anyway. Your real constraint is time, not money. You're one guy with three bays. Every minute you spend answering phones, ordering parts, or writing invoices is a minute you're not billing $120/hr. That's the leak. The phone is probably killing you and you don't realize it. When you're under a car at 9am and the phone rings, what happens? Miss it? You just lost a $400 job. Answer it? You just stopped billing. Track your missed calls for one week during your busiest hours. Multiply that number by $400. That's what you're leaving on the table every month. Most solo shops lose $2-3K/month+ just from calls they can't answer during peak times. At $7K overhead, you can't afford to keep bleeding calls. What I'd do if I were you: Track how many calls you're missing. That number will tell you if you need better systems or just better pricing. The goal isn't to work harder. It's to capture the revenue that's already trying to reach you.

There's a third throttle most shops don't track: call answer rate during peak hours. You can nail marketing and recruiting, but if 40% of your inbound calls hit voicemail between 8-10am because your service advisor is helping someone at the counter, you're funding your competitor's growth, not your own. The pattern: customer calls three shops. First one that picks up and sounds competent gets the job. If you're call #2 and they hit voicemail, you don't exist. A quick test could be pulling your missed call log for the last 30 days. Filter for 8-10am and 4-6pm specifically. Multiply those missed calls by your average ticket and a 30% conversion rate (conservative as the first shop to answer usually wins). Most shops I've talked to are shocked when that number lands north of $3-5K/month+ in leaked revenue. In my humble opinion, the real chicken-or-egg question isn't marketing vs. recruiting, it's this: Are you losing revenue because you don't have enough capacity, or because the capacity you have isn't converting inbound demand? If your bays are at 70% utilization but your phone answer rate during rushes is 60%, hiring another tech doesn't solve the problem. You're leaving money on the table before the work even gets scheduled. Fix the conversion leak first. Then you'll know if you actually need more capacity or if you just needed to capture the calls you were already getting.

I did something similar. I built an AI phone system for my in-laws' tire shop. Same Claude approach, same "90% there in a day" experience. The scheduling/bay management piece you built is the backend workflow. What I found missing was the frontend: most appointment requests start with a phone call, not a customer logging into a portal. If someone calls at 9am asking "can you fit me in today?", the service advisor has to check availability while on the call and manually input it somewhere. That's the piece I automated. AI answers the phone, checks real-time availability, books the slot, done. On the open source thing: I get why nobody grabbed it. Shop owners don't want to host software on their own server or mess with code. They want it to just work. That's why paid SaaS tools win even when free alternatives exist. It's not about features, it's about someone else handling the infrastructure and "done-for-you" rather than DIY. If you ever want to make this usable for actual shops, you'd need to either host it yourself or partner with someone who can. Otherwise it's a cool portfolio piece but not something a shop owner will touch.

I've been thinking about the missed call problem a lot lately (for reasons I'll get to), and one thing that helped me frame it differently: most shops don't have a call volume problem, they have a call timing problem. There's already mention of Tekmetric + Auto Ops, which is smart. But the issue those tools expose is usually this: your answer rate looks fine on average, but if you filter by time of day, you'll see 8-10am and 4-6pm are bloodbaths. That's when real customers with real money are calling and they're the ones hitting voicemail. Consider this quick diagnostic you can run today: Pull your missed call log for the last 30 days from Auto Ops. Filter for 8-10am and 4-6pm specifically. Count those calls. Multiply by: Your average ticket (let's say $400 for tires/alignments) Estimated conversion rate (30% is conservative, first shop to answer usually gets the job) That's your monthly revenue leak. Most shops I've talked to are surprised when that number lands north of $3-5K/month+. The real question then becomes: Is this a staffing problem or a systems problem? If your service advisors are buried helping in-shop customers during those windows, hiring another body might help but that's $40-50K/year in payroll for what amounts to 2-4 hours of overflow coverage per day. The math doesn't usually work unless you're already turning bays and need the headcount for other reasons. Alternative approach I've seen work: treat peak call hours like you'd treat peak bay utilization. You wouldn't leave a lift empty during your busiest time. Why leave the phone line empty? Some shops route overflow to an after-hours service, but most of those can't check inventory or book into your Tekmetric system, so they're just taking messages with extra steps. The callback conversion rate on those is brutal. Curious what others have tried here, especially if you've solved this without adding full-time headcount. It's one of those problems that feels like it should have a clean answer but most "solutions" I've seen just move the problem around.

Peyton, this is solid math. The efficiency×HPRO lens cuts through a lot of the noise. If I may, one variable that I didn't see but quietly bleeds margin: how many of those ROs never made it onto the schedule because the phone rang during a rush. I've seen shops running 85%+ efficiency on their B techs, bay utilization looks clean, but they're still leaving $3-5K/month on the table just from calls that went to voicemail during 8-10am and 4-6pm peaks. The pattern: customer calls three shops. First one that picks up and sounds competent gets the job. If you're the second call and they hit voicemail, you don't exist. Worth tracking: inbound call answer rate during peak hours and conversion rate on callbacks vs live pickups. Most shops assume 80-90% answer rate. Reality is closer to 60-70% when bays are full. If you're debating the B tech hire and your phones are getting missed during rushes, fixing the phone problem first might fund the tech hire within 90 days—without adding headcount pressure until you've proven the revenue ceiling actually needs it. The hire still makes sense if you're truly capacity-constrained. But I've watched shops add a tech, then realize six months later they could've captured the same revenue gain just by answering more calls with the team they had. As a quick test, pull your missed call log for last 30 days. Multiply by your average ARPO and conversion rate assumption (say 30% of inbound calls convert). If that number is >$2K/month, you've got a phone problem, not a capacity problem.