Your Google Rating Isn't Why You're Losing Leads

Spring 2023: my Google rating was 4.9, 41 reviews, and my booking rate from Google inbound calls was 34%.

Six months later, the rating had slipped to 4.8. I had 187 reviews. Booking rate from the same channel: 61%.

I didn't change my pricing, retrain anyone, or run a new ad. The only thing that changed was review volume — and if I hadn't been tracking it through CallRail and Airtable, I would have spent that entire stretch panicking about the decimal instead of understanding what was actually happening.

That's the conversation I want to have. Because most small electrical shops are optimizing for the wrong number entirely.

The Number You're Optimizing For Doesn't Mean What You Think

The 5.0 is a vanity metric. I'll say it plainly.

When a homeowner in East Austin pulls up Google to find an electrician, they're not doing a decimal comparison. They're running a fast, mostly unconscious trust check — does this business look real, does it look busy, did someone leave a review recently. The decimal is not the primary input.

I know this because I built the attribution chain to see it. Every inbound call to Reeves Electric gets a dedicated CallRail number: Google LSA, Google Business Profile, organic search, our trucks, Yelp, the occasional direct mail piece. Every booked job gets tagged to its source. I've been doing this since month six. So when my rating moved from 4.7 to 4.9 in late 2022, I was watching for a booking rate bump from Google. It didn't come. What I saw instead was the booking rate start climbing in Q2 2023, which is exactly when our review count crossed 100 and was still moving fast.

Your gut will tell you the rating matters most. Your gut on this is wrong.

Count and Recency Are Doing the Heavy Lifting

When we had 40 reviews at 4.9, our Google inbound booking rate was in the low-to-mid thirties. As we scaled from 40 to 180 reviews over roughly eight months, the booking rate climbed. Not in a straight line, but the trend was clear — and it didn't track with any rating movement. Our rating actually dipped during that window because we were asking more customers, including ones with mediocre experiences. We got 4s. We got occasional 3s. The volume swamped it.

Recency matters for a related reason. A shop with a 4.8 whose last review is eleven months old looks like they closed. My dispatcher surfaces this directly in our weekly call review sessions — four recorded calls, two booked, two lost, every Monday. More than once we've heard a customer say "you had way more reviews than the other guys" or "I saw you had a recent one."

Volume. Freshness. That's what they're actually looking at.

A competitor with 400 reviews at 4.8 is not losing to your 23 reviews at 5.0. They're winning by a margin you can't see because you're not tracking the right variable.

The customer doesn't trust the perfection. They trust the crowd.

Chasing 5.0 Is Actively Suppressing Your Volume

Shops obsessed with maintaining a perfect score make a specific set of decisions that kill velocity. They hold back on asking customers they're not confident about. They wait until they've confirmed satisfaction before sending the request. The caution feels like good business. It's actually just a cost that doesn't appear on the P&L.

The 5.0 instinct is a gut call, not a lead-data call. I've had conversations at trade events with shop owners who have beautiful ratings and no idea what their Google inbound booking rate is. No tracking number on the profile, no CallRail, no attribution chain. They're protecting a number they've never connected to a single booked dollar.

This is the same logic I apply to Google LSA. If you're running those ads without recording and reviewing the calls, you don't know what you're buying. The rating is the same problem — without attribution, the decimal you're protecting is a feeling, not a fact.

Your gut after 4,000 service calls has real information in it. Your gut after 23 Google reviews is hope. Know which one you're working with.

The Ninety Days That Changed How I Think About This

I launched Reeves Electric in February 2022. Pricing model, software stack, branded vans — I'd planned for all of it. What I hadn't planned for was the fact that I was now the person returning the irritated 9:30pm call from the customer whose breaker kept tripping.

Month two, my NPS was a 4. I'll keep saying that number out loud because it's the most useful thing I have to offer someone who's early.

I started answering every call myself for ninety days straight. And I started taking notes — not on what I thought was going wrong, but on what customers were actually saying, where they hesitated, where I lost them. Noting it down, then going back to fix the thing that caused it. By month nine, NPS was 81. That improvement wasn't a review campaign. It was fixing what was actually broken in the first 90 seconds of the intake call — and when you do that, reviews come at volume because the experience is genuinely different.

The weekly call review practice with my dispatcher is a direct extension of those ninety days. Four calls, every Monday. Two that booked, two that didn't. We tag what worked and what broke. That practice is also what told me, clearly, that customers were citing review count and not rating as part of why they called.

If your intake is broken, your reviews will reflect it eventually no matter how hard you work on reputation management. Fix the operation. The volume follows.

What Healthy Review Velocity Looks Like

At five trucks doing residential service, I'm running somewhere between 15 and 25 jobs a week depending on the ticket mix — that's what I see in my shop. If you're asking every customer, you should be covering most of them. The question is whether the request is going out automatically or whether a human is supposed to remember.

The shops that are manually texting review requests cover maybe 40% of jobs on a good week. Automate it through NiceJob or Podium — both integrate with Jobber and Service Fusion, both trigger off job completion — and coverage goes to nearly every job. That automation is most of the game.

Timing matters. In my shop, requests going out within two hours of job completion convert at a noticeably higher rate than ones going out the next morning. The tech just left, the experience is fresh, the customer is still in it. Set the trigger accordingly if your platform supports it.

For review management software: NiceJob or Podium. Pick one. Both work. Anything more complicated is overhead you don't need at this stage.

What to Do Monday Morning

Pull your Google Business Profile review count and your 90-day new review total. Log into your profile, count what you've received in the last 90 days. Write that number down. Treat it as a KPI going forward — same as booking rate, same as ticket average.

Set up a CallRail tracking number on your Google Business Profile if you don't have one. Twenty minutes. Buy a local number, assign it to the GBP source, forward it to your main line. Every call from that channel is now recorded and attributed. Do this before you change anything else. You can't fix what you can't measure.

Listen to the last four calls where someone found you on Google and didn't book. Not to diagnose your rating. To hear what actually happened. Were they price-shopping and you couldn't get to a number? Looking for same-day and you didn't have it? Did the call go to voicemail? That's where the conversion gap is — not in the decimal between 4.8 and 5.0.

If you're not on NiceJob or Podium, set one up this week. Connect it to your job management platform. Set the trigger for two hours after job completion. Turn it on. Check your velocity number again in 30 days.

Four things. The rating stabilizes once the velocity is real.

---

FAQ

Does my Google rating actually affect my LSA ranking, or is that a separate system?

LSA and your standard Google Business Profile run on partially separate logic. LSA rank is weighted heavily toward review count, response rate, and booking rate within the LSA system itself. Your star average matters, but less than you'd expect. A shop with 300 LSA-verified reviews will typically outrank a shop with 30 reviews at a higher average. Track the two separately and don't assume that protecting your GBP rating is doing anything for your LSA position.

How many reviews do I need before count stops being my main problem?

In my shop, the count problem was most acute below 100. In that range, every review moved visibly and customers were clearly doing the math on whether we were established. As we pushed past 100 toward 300, velocity and recency became the dominant factors — when did the last review come in, not how many total. Past 300 the questions shift again: photos, response time, booking experience. But velocity never stops mattering. A shop at 400 reviews that goes quiet for six months starts looking stale. Keep the engine running.

My best customers never leave reviews no matter what I do — what actually converts?

Two things made a difference for us. First, timing — ask within two hours of job completion, not two days later. Second, reduce friction. Don't send them to your Google page and expect them to find the form. Send a direct link to the review form. One tap, starts typing. Text converts better than email for residential customers in my experience. Automate it through NiceJob or Podium and both the timing and the link problem get solved at once.

A competitor has 600 reviews and I've seen their work — it's not better than mine. How do I close that gap?

You probably can't match 600 in a year at a residential service pace, and that's the wrong target anyway. What you can close is the recency gap. If they're adding 10 reviews a month and you start adding 20, you start looking more active than they do — and customers scan recent reviews more than the total count. Automate the request, run the velocity up, post fresh photos regularly. You're not trying to match their number. You're trying to look more current.

Should I respond to every review?

Yes. Every review, including the positives. Your response to a negative review is read by the next ten potential customers looking at your profile. Keep responses short and specific — write a real sentence about the actual situation, not a copy-pasted "we're sorry to hear this" that shows up word-for-word on every 2-star. Templated responses signal that nobody's home.

One bad review dropped me from 4.9 to 4.7 and I only have 30 reviews — should I try to get it removed or just push volume?

Push volume. Removal is a long, uncertain process. Google's bar is whether the review violates their policies, not whether it's unfair. If it's genuinely fake or violates terms, flag it. If it's a real customer who had a bad experience, your energy is better spent on the next 20 review requests. At 30 reviews, getting to 60 is the fastest way to stabilize the rating and it builds the velocity habit. That's where to put the time.