How to Build a Consistent Review Collection Process

What a consistent review collection process looks like

A review collection process is the documented sequence your team follows after a genuine customer interaction. It starts when a job, visit, purchase or appointment has been completed and ends when feedback has been acknowledged and any useful learning has reached the right person.

It is not a one-off campaign, a bowl of QR-code cards left by the till, or a monthly message sent to an old contact list. A reliable system gives every team member the same practical answers:

• Who should receive an invitation?
• When is the best point to ask?
• Which channel should we use?
• What exactly should we say?
• Who owns the follow-up and the reporting?

For a Google-focused process, make the action easy. Google allows businesses to share a direct review link or QR code in places such as receipts, thank-you emails, chat interactions and in-store displays. Google’s instructions for creating a review link or QR code are the best starting point for the route customers will use.

Set the rules before you train anyone

Your process needs a short written policy before it needs scripts. This protects customers, staff and the business when someone is under pressure to improve a star rating quickly.

There is also a UK consumer-protection reason to take this seriously. Since 6 April 2025, practices involving fake reviews and concealed incentivised reviews have been among the banned practices under the Digital Markets, Competition and Consumers Act 2024. The Competition and Markets Authority (CMA) has published detailed guidance for businesses that obtain or publish review information. Read the CMA’s fake reviews guidance before setting any incentive, moderation or review-display policy.

Include these rules in your team policy

• We invite customers after a genuine, completed interaction using the same eligibility rule for everyone.
• We do not offer money, discounts, gifts, prize-draw entries, upgrades or any other benefit for a review.
• We never ask for a particular rating or suggest what a customer should write.
• We do not ask staff, family, friends or suppliers to review experiences they have not genuinely had as customers.
• We do not take a customer’s phone, sign into their account or write a review for them.
• We make it easy for customers to decline and do not ask again in person after a clear no.
• We escalate complaints and sensitive feedback through the normal service-recovery process.

If you use email or text messages for review requests, check how that activity fits your privacy notice, contact permissions and wider communications policy. Whether a message is direct marketing depends on its content and context; where electronic review follow-up forms part of your marketing activity, the ICO’s PECR guidance on electronic marketing explains consent, the soft opt-in and the need for a simple opt-out. Regulated businesses and organisations handling sensitive information should obtain sector-specific advice before introducing automated requests.

Design the process around real customer moments

The best time to ask is usually shortly after the customer has received the value they came for. “Shortly after” will mean different things for a café, a builder and a physiotherapy clinic. Map the point at which the outcome is clear, rather than copying another business’s timing.

Write one sentence that defines the trigger for your business. For example: “Every customer whose installation has been signed off and whose final invoice has been issued receives one review invitation within two working days.” That sentence gives the team a clear standard and gives a manager something to audit.

Choose one primary destination

For many local businesses, Google is the natural primary destination because potential customers can see reviews on the Business Profile in Search and Maps. Google says reviews can help a business stand out and recommends requesting them with a link or QR code. Google’s review-request best-practice guidance is a useful reference for your staff policy.

Keep the first request simple: one clear destination and one direct link. If you operate in a sector where another established platform matters, decide in advance how it fits your process. Do not use a satisfaction question to send only satisfied customers to Google and dissatisfied customers somewhere private. If you use more than one platform, rotate invitations by a neutral rule or ask the customer to choose where they would prefer to leave honest feedback.

Give every person a defined role

Review collection fails when it is everybody’s job and therefore nobody’s job. A small team can keep this simple, but the responsibilities should still be explicit.

Do not set individual staff targets for five-star reviews. That encourages pressure and selective asking. If you use targets, make them process targets: for example, the percentage of eligible completed jobs that were sent the standard invitation, or the percentage of staff who completed training.

Train staff to ask naturally and confidently

Most employees do not avoid asking because they are unwilling. They avoid it because they worry about interrupting, sounding needy, receiving a negative response or not knowing the rules. Good training deals with those worries directly.

Run a focused 30-minute team session

1. 1

   Explain the purpose and the boundaries

   Start with why honest reviews are useful: they help prospective customers understand what the business is like and show the team where service can improve. Then cover the non-negotiables: no incentives, no rating requests, no screening for happy customers and no handling a customer’s device.

2. 2

   Show the exact customer journey

   Scan the real QR code together and open the actual review link on a phone. Staff should know where the card, receipt message or email template is found, and who to tell if the link stops working.

3. 3

   Practise one sentence, not a sales pitch

   Pair staff up for two or three short role plays: a pleased customer, a rushed customer and a customer who raises a concern. The goal is a calm invitation and a respectful exit, not a perfect performance.

4. 4

   Teach the escalation route

   Staff must know what to do if a customer is unhappy: listen, thank them for raising it, pass the issue to the named person and avoid arguing about a possible review. This is customer service, not reputation control.

Use language people can say in their own voice

Keep the invitation out of emotionally inappropriate moments. A veterinary practice should not ask for a review during a distressing consultation; a funeral-related service needs even more judgement. In sensitive services, a centrally managed, carefully timed follow-up may be more suitable than a verbal request.

Create a simple review-request SOP

An SOP is a standard operating procedure: a short document describing the task so it happens the same way regardless of who is on shift. Keep it to one page where possible. The version below is a practical starting point for a local business.

1. 1

   Mark the customer interaction as complete

   Use your existing booking, till, job-management or invoicing system to mark the agreed trigger: for example, “appointment complete”, “vehicle collected” or “handover signed off”. Check that there is no open service issue requiring attention.

2. 2

   Make the optional personal invitation

   Where staff see the customer, use the agreed one-sentence prompt. A personal invitation makes the later message less surprising, but it is not essential where the service is entirely remote or the context is sensitive.

3. 3

   Send one clear request through the approved channel

   Send the direct link by the permitted and appropriate channel, using the relevant template. Make the request recognisable, identify the business clearly and avoid adding unrelated promotions to the same message.

4. 4

   Use a restrained reminder rule

   A sensible starting rule is no more than one polite reminder, sent only to customers who have not opted out and only where your communications permissions allow it. Set a fixed interval, such as seven days, then stop. Repeated chasing damages trust and makes staff uncomfortable.

5. 5

   Monitor reviews and route learning

   Check new reviews on a set cadence. Thank the customer without sharing confidential details, flag a service concern to the right manager and note recurring themes such as waiting times, communication or workmanship.

6. 6

   Review the process weekly

   Look at whether eligible customers actually received the invitation, whether the link still works and whether any staff member needs support. Fix a broken handover or unclear trigger before changing the wording of the request.

Review-request templates your team can use

Personalise the business name and service where it is appropriate, but do not overcomplicate the message. Customers should immediately understand who is writing, why they are receiving it and what will happen when they use the link.

Choose channels that match the service

Use the channel customers already associate with their purchase or booking. A well-timed email can work well for a high-consideration home improvement job; a QR code may be more natural for a coffee shop; an appointment business might use its existing post-visit message.

Consistency matters more than trying every channel at once. Start with one personal moment and one digital follow-up. Once that is reliably happening, add another route only if it solves a real gap.

Measure process health, not just your average rating

A star average is an outcome, not a management system. It cannot tell you whether staff forgot to ask, the QR code was unreadable or customers never received the follow-up message. Track the few numbers that show where the process breaks down.

For example, if 48 customers were eligible last week and 40 received the standard invitation, your invitation coverage was 83%. That is a useful operational conversation: why did eight customers miss the process? Do not turn it into a judgement about which employee got the most positive reviews.

A simple weekly scorecard

Do not pretend every review can be attributed perfectly to a particular message. Customers may review days later after finding you again on Google. Use your records to spot broad operational trends, not to make unsupported claims about a single channel.

Fix the common reasons team processes stall

If the system relies on staff remembering several separate tasks, reduce the number of decisions. Put the QR code on the standard receipt. Create a single approved email template. Add one field in the job-completion workflow. Small design changes are usually more reliable than repeatedly telling people to try harder.

A 30-day action plan to launch the process

Days 1–7

Set the foundation

Choose your primary review destination, create the direct review link and QR code, define the eligibility trigger, appoint a process owner and write the one-page policy. Test every link on more than one phone before anything reaches customers.

Days 8–14

Build the assets and train the team

Create one email or text template, one printed prompt and one escalation note for complaints. Run the 30-minute staff session, role-play the wording and make sure everyone knows where the materials are stored.

Days 15–21

Pilot and observe

Run the process with every eligible customer for one week. Do not change the rules after one quiet day. Instead, note missed triggers, customer questions, technical faults and moments where the request felt awkward.

Days 22–30

Improve the workflow, then make it routine

Review invitation coverage, new reviews and feedback themes with the team. Fix the biggest practical blockage, publish the final SOP and schedule a weekly ten-minute check-in. Refresh scripts and QR materials whenever your service, branding or review destination changes.

Decide when manual collection has reached its limit

A manual process is often the right place to start because it exposes the real customer journey and helps staff learn the wording. But it becomes fragile when several people must remember follow-ups, customer records live in different systems or no one can see which completed jobs missed the request.

If you want a central place to manage prompts, links and recurring follow-up without losing the personal touch, the DIY Review Flywheel Software is designed for businesses that want to run their own review process. If the main obstacle is lack of time or internal ownership rather than software, a Fully Managed Review Flywheel can help put the process in place and keep it moving.

Frequently asked questions

Sources and further reading

The guidance in this article was checked against the following current sources. Platforms, laws and interfaces can change, so confirm important details before acting.

• Create a Google link or QR code to request reviews — Google Business Profile Help
• Tips to get more reviews — Google Business Profile Help
• Prohibited and restricted content: fake engagement — Google Business Profile Help
• Fake reviews guidance (CMA208) — Competition and Markets Authority
• Guidance on direct marketing using electronic mail — Information Commissioner’s Office