The best time to ask for a review is not “whenever the marketing calendar says so.” It is after the customer has received the work, had a chance to inspect it, and knows whether the business kept its promises.

That sounds simple, but review requests often fail in predictable ways: the business asks too early, sends a vague message, makes the customer hunt for the right page, or keeps following up after the customer has chosen not to respond.

A better process is short, specific, and voluntary. This guide shows how to build one without scripting fake enthusiasm or pressuring customers.

1. Define the completion moment

Choose the observable event that makes a review request appropriate for each service. Examples include:

  • the customer has inspected the completed repair;
  • the final cleaning walkthrough is finished;
  • the installation has passed the agreed acceptance check;
  • the customer has received the promised deliverable;
  • a stated post-service waiting period has passed without an unresolved issue.

“Invoice sent” is not always the same as “value delivered.” Base the request on the customer’s experience of completion, not only on an internal administrative event.

If there is an open complaint, callback, damage claim, missed deliverable, or billing dispute, route the situation to support first. A review request should never compete with problem resolution.

2. Ask every eligible customer consistently

Do not ask only the customers you believe will leave five stars. A selective process can distort the feedback you receive and may conflict with a platform’s policies.

Write a neutral eligibility rule such as:

Send one review request after the completion check to every customer who can be contacted for that purpose and who has no unresolved service issue.

The rule should not depend on a private satisfaction score, the employee’s guess, the size of the purchase, or whether the customer praised the work in person.

Keep a simple record of eligible, requested, followed up, completed, declined, and suppressed. That prevents duplicates and lets the business improve the process without guessing.

3. Make the request direct and honest

A useful review request has four parts:

  1. identify the completed service;
  2. thank the customer without exaggeration;
  3. ask for an honest review;
  4. provide the direct review destination.

For example:

Thanks for choosing Northside Plumbing for the kitchen faucet replacement. If you have a moment, would you share an honest review of the service? Your feedback helps us understand what worked and what we should improve: [direct review link]

The wording does not tell the customer what rating to leave. It does not imply that only positive feedback is welcome. It also gives enough context for the customer to recognize the job without exposing sensitive information.

Use the customer’s real service and the business’s real name. Do not invent personalization or send a message that implies a person wrote it manually when it was generated automatically.

4. Remove avoidable friction

Test the request from a customer’s device before using it. The link should open the intended review flow, not a homepage, search result, login maze, or internal dashboard.

Check that:

  • the destination belongs to the correct business and location;
  • the link works on mobile;
  • the business name and address are recognizable;
  • the message contains only one primary action;
  • no shortened or unfamiliar URL makes the request look suspicious;
  • the customer can ignore the request without another immediate message.

If the platform requires an account, do not hide that fact. Let the customer decide whether the process is worth completing.

5. Follow up once, then stop

One courteous reminder may recover requests that arrived at a bad time. Repeated reminders turn a voluntary request into pressure.

Use a short follow-up after a reasonable interval:

A quick follow-up in case the earlier message was easy to miss. If you would like to share an honest review of the faucet replacement, here is the direct link: [review link]. No further reminder will be sent.

Record that the follow-up was sent. If the customer does not respond, close the request. Do not move them into another campaign, contact them from a second channel, or have an employee ask again unless the customer initiates the conversation.

Honor opt-outs and communication preferences across the business, not just inside one spreadsheet.

6. Never trade something for a review

Do not offer a discount, gift, contest entry, refund, priority service, or other benefit in exchange for a review. Do not ask employees, relatives, vendors, or customers to post reviews that do not reflect a genuine experience.

Avoid instructions such as “leave us five stars” or “only review us if you were happy.” Ask for an honest account and let the customer choose the rating and wording.

Platform policies can change, so confirm the current rules for every review destination you use. Your internal workflow should be stricter than the temptation to chase a short-term rating increase.

7. Respond to reviews with the same discipline

A response is public customer service. It should acknowledge the review without revealing private details or arguing about the customer’s motives.

For a positive review:

Thank you for taking the time to share this. We appreciate the feedback and are glad the agreed work met your expectations.

For a critical review:

Thank you for raising this. We want to understand what happened and review it against our service record. Please contact us at [support route] so we can discuss the details privately.

Do not confirm addresses, appointment dates, health information, payment details, or the specifics of a dispute in public. Move case-specific resolution to an appropriate private support channel.

8. Measure the workflow, not just the rating

Track operational signals that the business can actually control:

  • eligible completed services;
  • first requests sent;
  • one-time follow-ups sent;
  • review links opened, when the channel supports lawful measurement;
  • reviews received;
  • requests suppressed because support was unresolved;
  • duplicate or failed messages;
  • response time for new reviews.

Do not claim that this process guarantees more reviews, higher rankings, or additional revenue. Measure what happens over a defined period, compare it with the previous process, and change one variable at a time.

Use a repeatable review-request system

A strong process is easy for a team member to audit: they can see why a customer was eligible, which message was sent, whether a follow-up remains allowed, and whether an unresolved service issue stopped the request.

Before buying anything, use the free review-request workflow sample. It shows the actual eligibility, timing, suppression, and follow-up decisions in the editable system. No email or account is required.

Fireproof Studio’s Local Trust & Conversion Kit turns that process into editable request templates, response patterns, suppression rules, Business Profile content planning, service-page copy controls, and a measurement ledger. It is a $47 one-time purchase with a single-business commercial license.

Whether you build your own workflow or use the kit, keep the standard the same: ask consistently, ask honestly, make the action easy, and respect the customer’s decision not to respond.