You can ask customers for Google reviews. The useful question is how to make that invitation part of normal service without buying praise, filtering out criticism or putting people under pressure.
For a UK business, a review process needs three things: a real customer experience, a straightforward invitation and someone responsible for what happens afterwards. Start there before adding another reputation tool or CRM sequence.
What Google allows, and where requests go wrong
Google’s review guidance allows businesses to remind customers to leave reviews. It prohibits incentives for posting reviews, changing them or removing negative feedback. A discount for an “honest review” still offers a benefit in exchange for a review; asking for honesty does not fix that.
Google’s current content policy also prohibits selectively soliciting positive reviews. A process that sends happy customers to Google but sends unhappy customers only to a private form is commonly called review gating. The problem is the selective public invitation.
The same policy says businesses should not pressure people to review while on the premises or request specific review content. Its examples include asking staff to solicit a certain number of reviews and asking for wording that identifies a staff member. Remove those instructions from team scripts.
Customers should choose their own rating and words. Keep private feedback available to everyone alongside the same opportunity to leave a public review. Do not use a satisfaction score to decide who receives that opportunity.
Build the request around a completed customer experience
Choose a clear point in the customer journey
Write down when your business considers an experience complete enough for feedback. That could be after a repaired item is collected, an order arrives or a service appointment finishes. This is an operational recommendation, rather than a universal waiting period set by Google.
Choose timing that lets people assess the work. An invitation sent when an order is placed may arrive before the customer has experienced delivery or used the product. For a longer project, agree which completed stage the request relates to.
Give the process an owner. In a small business that may be the person closing jobs; in a larger one it may sit with customer service. The owner should know which system records completion and who can correct a wrongly triggered request.
Use the link for the right Business Profile
Google provides a review link and QR code through Business Profile. Its current instructions are to open your profile, select Read reviews, then Get more reviews. Copy the link or download the QR code. Google currently specifies a computer browser for generating the QR code.
Test the destination before sharing it. If you have several locations, check the business name and location rather than assuming an old link still points to the right profile. Open it on a phone as well as a computer.
A printed QR code also needs a practical test at its actual size and position. Reflections, small printing and awkward placement can make an otherwise correct code difficult to scan.
Customers need to sign into a Google Account to leave a review; Google says a Gmail address is not required. Staff should be ready to explain that without taking over the customer’s account.
Keep the invitation short and optional
An example of neutral wording is: “Thank you for choosing us. If you would like to share your experience, you can leave a Google review using this link. We also welcome feedback directly if there is anything you would like us to know.”
Adapt the greeting to your business and the actual service. Keep the request easy to understand, and check that the message makes sense when read without the surrounding conversation. A customer should recognise who is contacting them and why.
Check the channel before automating delivery
Google’s permission to request reviews does not settle whether a particular email or text complies with UK communications law. The ICO’s PECR guidance distinguishes genuine research and routine service messages from marketing, and explains that promotional content can bring a message within marketing rules.
Do not assume a public review invitation is exempt simply because you call it feedback or send it after a purchase. Assess the actual purpose, wording, recipient and channel before enabling a sequence. If it is direct marketing, establish the applicable permission and opt-out arrangements. Keep sales offers out of the review invitation.
Give your CRM a small, testable job
Our recommendation is to begin with one invitation and a visible record of whether it was sent. Avoid stacking reminders from the booking system, ecommerce platform and CRM before you understand how they interact.
For each invitation, the team should be able to identify the completed experience, destination profile, sending route and send time. Collect only what you need to operate and check the process.
Ask whoever manages your email and CRM workflows to demonstrate these cases before switching it on:
- A completed job produces the intended invitation.
- An unfinished or cancelled job does not trigger the completed-service message.
- A corrected completion date does not unexpectedly restart the sequence.
- A returning customer does not receive overlapping requests from several systems.
- A request to stop further messages is respected by every connected sending route.
Use test records and controlled destinations for those checks. Do not create public reviews as test data. Keep a simple way to pause the workflow if messages start going to the wrong people.
Plan how you will handle criticism
A review invitation creates a responsibility to listen. Assign someone to check new feedback and route genuine service problems to the person who can resolve them.
Google recommends professional, concise replies and protecting reviewers’ privacy. A public response can acknowledge the issue and offer a direct contact route without exposing an order history, address or other private details. Move the investigation into a private conversation where needed.
If you believe a review breaks the rules, use Google’s reporting process. Disagreement or a low rating alone is not grounds for removal. Google provides a Reviews Management Tool to check decisions and a one-time appeal route where eligible. Record the relevant policy concern and supporting evidence rather than repeatedly flagging the same review.
Keep service recovery separate from attempts to improve the public score. Resolve the customer’s actual problem and record what your business needs to change.
Understand the consequences of manipulating reviews
Google says a business that violates its fake engagement policy may face Business Profile restrictions as well as review removal. Examples include temporarily preventing new reviews, temporarily unpublishing existing reviews and displaying a warning that fake reviews were removed.
These are possible measures, rather than an automatic outcome for every case. Google also documents an appeal process for restrictions. If you receive a notice, retain it, investigate the collection process and use the stated route to respond.
Displaying reviews on your website brings another responsibility
The UK rules are already in force. The CMA’s current overview explains that changes introduced in April 2025 include a banned practice relating to fake reviews and concealed incentivised reviews. Disclosing an incentive does not override Google’s separate prohibition on offering incentives for its reviews.
If your website displays consumer reviews, review counts or ratings, read the CMA’s short guide for review publishers. It covers material originally collected by someone else, too. Installing a third-party widget does not transfer all responsibility to its supplier.
The guide calls for reasonable and proportionate prevention and removal measures, a published policy, risk assessment and processes for detecting, investigating and acting on banned material.
Start by identifying every review display you control. Include widgets and manually copied quotes, then establish who maintains them, how concerns reach that person and how corrections happen. Check that a displayed count or rating still matches the source it claims to represent. Use the full guidance to assess what your particular setup requires.
A practical review-process audit
Walk through one real customer journey from completion to invitation, response and any website display. Inspect the actual messages, links and automation settings rather than relying on the name of a tool or a supplier’s promise.
Ask the team where they see friction: customers reaching the wrong listing, invitations arriving too early, duplicate messages or feedback nobody owns. Fix the process before trying to increase its output.
Review those checks when you change booking software, add a location or replace a review widget. Keep the collection process focused on genuine experiences and the operational report focused on whether it works as intended. A review count by itself tells you little about whether customers received useful service or whether their concerns were resolved.
If you need help connecting your review requests, Business Profile and website, talk to BuzzBoost. We can help you examine the customer journey and identify a practical next step across your SEO, website and CRM setup.
Featured image: AI-generated editorial artwork, not a photograph of a real BuzzBoost office, client or result.
