You finished the job clean. Showed up on time, communicated through the process, did exactly what you said you'd do. The customer was happy — you could tell.
And then you didn't get the review.
Not because they didn't like the work. Because the ask was wrong.
The Three Problems with How Contractors Ask for Reviews
Problem 1: Wrong timing.
Most contractors ask at payment. That's the wrong moment. The customer's mind is on price, not on the experience of working with you. The emotional peak — when they feel the gratitude, when they're looking at the finished project and thinking "this is exactly what I wanted" — that comes later. Usually the next morning.
The optimal ask window is 24 to 72 hours after job completion. A text sent at 9 AM the day after is the highest-converting ask you can send. The job is done, the invoice is paid, the work speaks for itself, and the goodwill is still fresh.
Problem 2: Wrong channel.
Email works for a lot of things. Review requests aren't one of them. Average open rate for service business email is 20 to 30%. Most customers don't check the email you sent about their roofing job a week later.
Text messages have 98% open rates and most get read within 3 minutes. If you're asking for reviews via email, you're leaving most of them on the table. One short text, sent to every customer, timed right, converts at 20 to 30%.
Problem 3: No direct link.
If your review request says "leave us a Google review" with no link, you've just added four steps to a process that should have zero friction. The customer has to open Google, search for your business, find the right listing, scroll to reviews, and then find the "Write a review" button.
Most people don't finish that journey. They intended to leave a review. They just didn't.
See how your review count compares to the top competitor in your market →
How to Get Your Direct Review Link
Google makes this straightforward.
Search for your business name on Google. When your Business Profile appears on the right side of the results, look for the "Get more reviews" button. Click it — you'll see a shareable link to copy.
That link takes customers directly to the review form, skipping all the search steps. Shorten it with bit.ly or a custom short link if you want something easy to read in a text message.
Keep this link somewhere accessible — in your CRM, your invoicing software, your phone's notes. You're going to use it after every job.
Three SMS Templates That Work
Copy these directly. Adjust the name and fill in your review link.
Template 1 — Day after, casual: "Hey [Name] — glad we could get that taken care of for you. If you have a minute, a quick Google review would really help us out: [your link]. Appreciate it."
Template 2 — Social proof angle: "[Name] — thanks for having us out. If you're happy with the work, a Google review goes a long way for a small business. Takes about 60 seconds: [your link]. No pressure."
Template 3 — Big visual job: "Hey [Name] — hope everything's looking good after [the project]. If you'd be willing to share your experience on Google, here's the link: [your link]. Thank you for the business."
What makes these work: they're short, they don't sound like templates, and the ask feels personal. Add one line that references the specific job — "glad we got the water heater sorted before winter" — and it instantly stops reading like a mass text.
Review Velocity Beats Review Volume
Google's algorithm doesn't just count reviews — it tracks the rate at which you're getting them.
A business with 200 reviews, all posted in a 3-month burst two years ago, ranks below a business with 80 reviews posted consistently over 18 months. Consistent velocity signals active business. It tells Google you're still operating, still serving customers, still relevant.
This is why building a review ask into your post-job workflow matters more than any one-time push. Five reviews a month, every month, compounds. It also means your count climbs steadily even in slower seasons.
Map Pack ranking factors include review recency as a direct signal. A review from this month carries more weight than one from last year.
Responding to Every Review
Once reviews start coming in, respond to all of them — five stars or one.
Google's documentation explicitly lists review response rate as a ranking signal. Businesses that respond to every review consistently outperform businesses with the same count and lower response rates. Responding shows Google the business is actively managed.
For five-star reviews: keep responses short and specific. "Thanks [Name], glad the deck came out exactly how you pictured it" beats "Thank you for your kind words!"
For negative reviews: respond calmly, acknowledge the issue, and take the conversation offline. Don't argue. A measured response to a negative review often impresses potential customers more than a perfect rating.
The GBP reviews guide covers response strategy in more depth — including how keyword-rich responses add additional relevance signals to your listing.
The AI Search Connection
Reviews are a Google Maps signal — they don't directly feed AI systems like ChatGPT or Perplexity. But they contribute indirectly.
Review content gets scraped, indexed, and used as training data. A business with 150 detailed five-star reviews has 150 data points saying "this HVAC company in Denver does good work." AI systems cross-reference this with your schema markup, website content, and third-party mentions to build a confidence score for your business.
Building NAP consistency and review volume together creates a compounding authority signal that affects both traditional search and AI recommendations.
The System in Practice
The businesses that consistently own the Map Pack in their market aren't getting reviews because their work is better than yours. They have a system.
Ask every customer. 24 to 48 hours after completion. Via text. With a direct link. Respond to every review within 48 hours. Repeat every job.
That's the whole thing. Most of your competitors aren't doing this. The ones who are sit in positions 1, 2, and 3.
Run a free audit to see how your review count and velocity stack up →
