A business can do great work all week and still get very few reviews if nobody owns the ask.

If reviews are scarce, check whether requests happen consistently and promptly before assuming customers are unwilling to help.

The request may simply happen too late or not at all.

The fix is a small post-job system: decide when a job is complete, assign who sends the request, give them one easy link, and track whether the request went out.

For a local service business, that is far more useful than asking the team to “remember to get reviews.”

Google allows businesses to ask customers for reviews with a direct link or QR code.

Google also says reviews must reflect genuine experiences and prohibits incentives in exchange for reviews.

Google’s review-request guidance gives examples such as thank-you emails, receipts, chat interactions, and QR codes.

Start with one clear trigger

The best time to ask is connected to a real completed experience, not to an arbitrary calendar reminder.

Choose a moment that means the customer has received the service.

For example:

  • A plumber asks after the repair is finished, the invoice is paid, and the homeowner confirms the water is working.
  • A landscaper asks after the final walkthrough.
  • A salon asks after the appointment is complete and checkout is finished.
  • A restaurant asks through a receipt or thank-you message after the visit.

Your trigger should be simple enough that the team can use it every time.

“When the job is completed and paid” is clearer than “when the customer seems happy.”

That distinction matters.

If the process depends on someone guessing how satisfied a customer is, it becomes inconsistent and can create a skewed picture of customer feedback.

A neutral completion rule is easier for staff to follow and fairer to customers.

Make the review request take one step

A customer should not need to search for your business, find the right profile, and figure out where to leave feedback.

Create a direct review link from your Google Business Profile.

Google also provides a QR code option for review requests.

Put the link where your team already works:

  • in the job-complete email template
  • in the invoice or receipt process
  • in the CRM’s completed-job stage
  • in the technician’s closeout screen
  • in a printed leave-behind card, if that fits the business

Google specifically suggests placing the link or QR code on receipts, thank-you emails, chat interactions, or in-store displays.

Use the channel that matches how your customers normally hear from you.

A home-service customer may respond best to a short text.

A retail customer may see it on a receipt.

There is no need to force every business into the same channel.

Give one person ownership

A review process fails when everyone owns it and nobody checks it.

Decide who is responsible for each part:

Step Owner Done when
Mark the job complete Technician, office manager, or owner The job reaches the defined completion stage
Send the request CRM automation or named staff member The customer receives the link
Check for missed requests Office manager or owner The completed-job list is reviewed weekly
Reply to new reviews Owner or designated manager A thoughtful response is posted when appropriate

This does not need a complicated CRM.

A small team can start with a spreadsheet or a completed-job list.

The important part is being able to answer one basic question at the end of the week: “Which completed customers were asked?”

If you already use a CRM, connect the request to a specific status such as “job complete” or “invoice paid.”

A simple CRM process can keep completed jobs, follow-up tasks, and customer history from disappearing into text threads and memory.

Use plain, neutral request language

Do not ask for a five-star review.

Do not tell customers what to write.

Do not turn the message into an advertisement.

Ask for an honest review and make the link easy to use.

Example text message

Thanks for choosing [Business Name] for your [service]. If you have a minute, would you share an honest review of your experience? It helps future customers understand what to expect: [review link]

Example email

Subject: Thank you for choosing [Business Name]

Hi [First Name],

Thank you for trusting us with your [service]. If you have a moment, we would appreciate an honest review of your experience. Your feedback helps us improve and helps other customers make a more informed decision.

[Leave a review]

Thank you, [Name]

The wording should sound like your business.

A family-owned HVAC company should not write like a software company.

Keep it short, specific, and human.

Invite context without asking for praise

Useful feedback can explain what work was done, how it turned out, and what working with the business was like.

If you use a context-focused request, make those details optional.

Don't ask for a positive answer, a particular rating, or words for the customer to copy.

Optional context-focused wording

If you'd like, you can share what work we did, how it turned out, and what it was like working with us. Please use your own words and share your honest experience.

Check the review platform's rules before using a detailed prompt.

Google's current policy says merchants shouldn't request specific content in reviews.

Making a request neutral or optional doesn't remove that restriction.

For Google reviews, use the open-ended example above; don't treat this context-focused wording as a Google-compliant template.

Follow up once, then let it go

People are busy.

A customer may intend to leave a review and forget.

One polite reminder is reasonable if you have not received a review after your normal waiting period.

For example:

Just a quick follow-up from [Business Name]. If you have not had a chance to share feedback on your recent [service], here is the link: [review link]. We appreciate your time.

Do not keep sending reminders.

The goal is to make feedback easy, not to turn a completed job into an annoyance.

Avoid shortcuts that create risk

Google’s policy is clear that reviews must reflect a genuine experience.

Google prohibits offering payment, discounts, free goods, or services in exchange for posting, changing, or removing reviews.

Read the current Google Maps user-generated content policy before building any promotion around reviews.

Avoid these practices:

  • Offering a discount, gift card, contest entry, or other reward for a review
  • Asking only customers you believe will leave positive feedback
  • Asking for a specific star rating
  • Providing a script for customers to copy
  • Pressuring customers to remove or change a negative review
  • Having employees, friends, or vendors post reviews without a real customer experience

An honest mix of feedback can be useful.

Google notes that balanced reviews can help potential customers decide, and it recommends responding to reviews with a helpful, professional tone.

A negative review is not automatically a marketing failure.

It may show you where a handoff, communication step, or service expectation needs work.

Treat review replies as part of the system

The request is only half the process.

Someone should check new reviews and reply when a response would be useful.

For a positive review, a short, specific thank-you is enough.

Avoid using the same generic response every time.

For a negative review:

  1. Read it carefully before responding.
  2. Check the customer record and speak with the relevant team member.
  3. Reply calmly and without sharing private customer details.
  4. Acknowledge the concern if appropriate.
  5. Move a complicated resolution to phone or email.

Google recommends keeping replies professional, relevant, and concise, while protecting reviewer privacy.

The purpose is not to win an argument in public.

It is to show future customers that the business takes feedback seriously.

Track the process, not just the review count

Do not obsess over a number without knowing whether your team is actually sending requests.

Start with a simple weekly check:

  • Completed jobs this week
  • Customers sent a review request
  • Customers sent one follow-up
  • New reviews received
  • Common feedback themes
  • Requests that were missed and why

The first useful improvement may be operational.

Maybe technicians close jobs in the field but the office never sees the update.

Maybe invoices are sent days later.

Maybe the review link is buried in a template nobody uses.

Fix the broken handoff before spending money on reputation tools or campaigns.

Set up the system this week

You can build a working first version in a few steps:

  1. Create your direct Google review link or QR code.
  2. Choose one completion trigger, such as paid invoice or completed walkthrough.
  3. Write one text and one email template.
  4. Assign the person or automation that sends each request.
  5. Add a “review request sent” field to your CRM, job list, or spreadsheet.
  6. Review completed jobs once a week for missed requests.
  7. Check new reviews and identify recurring service feedback.

The goal is not to automate every customer interaction.

The goal is to make sure a customer who has completed a real job gets a clear, respectful chance to share their experience.

Reviews can strengthen the proof customers see when they compare local businesses, but they are only one part of a trustworthy buying path.

Use them alongside real examples, photos, clear services, and useful website copy.

For more on that broader trust system, read How to Build Trust With Proof of Work.

Choose the next step that fits your business

If you can assign the trigger, message, owner, and weekly check yourself, a practical Playbook can help you put the system in place without overcomplicating it.

If your review request needs to connect to a CRM, invoicing system, or customer messaging workflow, scoped Setup Services can help build that handoff.