Not sure what you need?
Book a discovery call. We look at your market, competitors, and site, then recommend where to start.
Book a discovery call
“Thanks for choosing [Business]. If you would like to share your experience, you can leave an honest Google review here: [link]. Your feedback is welcome.” That is enough for a first request. No discount, no suggested rating, and no speech about how badly your business needs five stars.
Google permits requests for genuine, unincentivized reviews. Its Maps content policy prohibits paying or rewarding reviewers, discouraging negative feedback, and selectively soliciting positive reviews. It also prohibits pressure to review on the premises, requests for particular review content, and staff review-solicitation quotas. Do not ask customers to mention an employee, service keyword, or star rating.
Give the person room to decline. A customer should be able to receive the completed work, receipt, warranty information, and normal support without writing anything about your business. Keep the invitation separate from a technician’s need to finish an appointment or collect payment.
Platform policy and federal rules are different. The FTC’s consumer review rule Q&A explains that the rule prohibits incentives conditioned on positive or negative sentiment, including implied conditions. It does not prohibit every incentive regardless of sentiment, although nondisclosure and other deceptive practices can violate the FTC Act. Google’s policy is stricter for Google reviews: do not offer an incentive, even for an honest review.
Use the review link or QR code associated with your actual Business Profile. Google’s review guidance recommends these options and notes that reviewers need to sign in to a Google Account. Test the link on a phone before adding it to a receipt or message. Confirm the business name and location so requests do not send customers to the wrong branch.
Use the opening message as your email or text body, with your business name and link substituted. For a printed receipt, shorten it to: “Want to share your experience? Leave an honest Google review using this QR code.” These are suggested invitation templates. The customer supplies their own review, in their own words.
Keep the request to one task. An email that simultaneously asks for a referral, survey, social follow, and review makes the next step harder to find. Use a recognizable sender and a readable link label. Make support contact details available to everyone, whether or not they leave a public review.
For a completed service visit, a reasonable starting point is the follow-up message after the work is finished and the customer has had a chance to experience it. For a longer project, use a defined completion milestone. These are practical starting points to test. The sources here do not establish a universal best hour or day to ask.
Define eligibility using the customer relationship, completed work, and permission to use the communication channel. Apply it consistently, regardless of satisfaction. Do not run a private survey that sends happy customers to Google and unhappy customers only to a support form. Handle service concerns through normal support while keeping the public review option equally available.
If you choose a reminder, make it optional and limited. One reminder after a reasonable interval is a conservative workflow choice, not a proven optimum. Stop when someone declines, opts out, or says they already reviewed. Do not keep nudging because their rating is lower than you hoped.
Trigger. Use a real completion status in your scheduling or customer system. Check that a rescheduled visit, duplicate record, or canceled job will not start a request.
Message. Send the approved neutral invitation through a channel you are permitted to use. Keep opt-outs and contact preferences connected to the automation.
Stop conditions. Suppress duplicate requests and honor declines. Give staff a way to stop a mistaken message without changing eligibility based on whether the customer is happy.
Human owner. Assign someone to check delivery failures, wrong links, and customer replies. A reminder system needs maintenance even when the message sends automatically.
Test with internal contact records before enabling the workflow for customers. Walk through a completed job, a canceled job, an opt-out, and a repeated status change. Record which event caused each message. The point is to confirm that your system follows your written process, not to manufacture a burst of ratings.
If you need help connecting your customer records and follow-up messages, our CRM setup and automation service is a starting point. Bring the neutral invitation, eligibility rules, and stop conditions to the scoping conversation.
A useful response acknowledges the issue or detail and offers a sensible next step. Keep private account, health, address, or payment information out of public replies. Google’s reply guidance recommends concise, professional responses and moving complex concerns to a private conversation. Flag reviews that appear to violate policy; a low rating alone is not a policy violation.
For example: “Thank you for telling us about the delay. Please contact our office at [business contact] so we can look into the appointment.” Adapt that only to facts you can verify. Avoid an automatic apology that admits an event you have not checked, or a defensive response that argues with the person.
Keep service recovery independent of the review. Resolve the underlying problem because it needs attention. Do not make a refund, repair, or normal support conditional on deleting criticism. A reply is a public record of how you handle feedback, so have a person review sensitive responses before they go live.
Track eligible completed jobs, invitations sent, delivery failures, opt-outs, and new public reviews over the same reporting period. Keep these as separate counts. A new review might come from an older customer or someone who never received your message, so the totals alone do not prove the invitation caused it.
Look for operational fixes: a broken link, repeated requests, messages sent before completion, or a support inbox nobody checks. Discuss recurring service feedback with the team. Use the record to improve the process rather than setting targets for staff to collect reviews. The customer decides whether to publish and what to say.
For local businesses requesting Google reviews. Google policies and U.S. FTC guidance are linked below. The timing, templates, and tracking workflow are editorial recommendations, not measured conversion benchmarks or a guarantee of more reviews. Other platforms have their own rules. Licensed and regulated professions, such as healthcare and legal, may have their own rules on asking for reviews, so check yours first.
Bring your current request message and customer workflow to a discovery call. We can help identify the setup and follow-up work you need.
Book a free callHow relevance, distance, and prominence shape local results, plus the improvements you can actually make.
Read guideCheck categories, hours, contact details, and review practices against Google’s own guidance.
Read guideCheck deliverables, account access, ownership rights, reporting, and exit terms before signing.
Read guideOne free call. We look at your market, your competitors, and tell you exactly what we would do, whether you hire us or not.
Book a Discovery Call
West Pasco Pinellas Business Association (WPBA)