DetailOAR Field Manual · Reviews

How to Build an Automatic Review-Request System

Ask every eligible customer for an honest review at the right moment, automate follow-up with care, honor opt-outs, and route complaints to a private fix.

Intermediate13 min readAction: 2–4 hrUpdated July 16, 2026
Start guide
Save or use this guide
Download checklist

Review request flow that runs itself: job completed, a short wait, one polite request with a direct link, one gentle reminder — every customer asked, no gating, no bribes
Contents
01

Start

Know the outcome.

Outcome

Launch a compliant request flow with clear eligibility, smart timing, the same ask for everyone, capped reminders, working opt-outs, and measured results.

Audience, time, and cost
Who it is for

Businesses that ask only when they remember, filter requests by who seemed happy, or run automations that can message the wrong customer.

Time and cost

Setup takes a few hours; the ongoing bill depends on your email and SMS providers.

Before you start

Save the official review destination, confirm channel consent and quiet hours, decide which completed jobs count, and name a service-recovery owner.

Tools and materials
  • official review link
  • message automation
  • send log
  • eligibility rule
  • templates
  • opt-out and escalation process
02

Steps

Do the work in order.

  1. Step 1

    Define eligibility and exclusions

    Trigger only from completed jobs the customer actually received. Exclude tests, duplicates, opted-out contacts, disputes under restricted handling, employees, and invalid channels.

  2. Step 2

    Choose timing by service

    Send once the customer has seen the result and before the memory fades. Let coatings, multi-day work, and follow-up inspections run on their own timing.

  3. Step 3

    Write a neutral request

    Send: “Thanks for trusting us with [vehicle/service]. If you’d like, share an honest review here: [link]. Reply to this message if anything needs attention.”

  4. Step 4

    Limit reminders

    Cap reminders at a small documented number, and stop on a detected review where that’s reliable, a reply, an opt-out, a complaint, or manual closure.

  5. Step 5

    Route service recovery

    When a concern comes in, cut an urgent task to its owner. Acknowledge, dig in, resolve it fairly, and never tie the fix to editing or removing a review.

  6. Step 6

    Test every branch

    Run demo jobs through eligible, duplicate, opt-out, failed-send, quiet-hour, complaint, and already-reviewed states.

  7. Step 7

    Measure and audit

    Each month, review the eligible count, sends, failures, opt-outs, link use, reviews, response time, and complaint resolutions.

03

Reference

Use the detail when you need it.

How it works

Automation exists so you stop forgetting to ask, not so you can tilt the feedback. Every eligible customer gets a neutral request after a verified completion. Complaints get real service attention, and the customer keeps their independent right to review either way.

Terms used in this guide
  • Review gatingScreening customers by how they’ll probably rate you before offering the review link.
  • Eligibility eventThe verified operational moment, like a paid completion, that’s allowed to trigger the request.
Common mistakes
  • Asking “Were you happy?” before you’ll share the link.
  • Dangling a reward for five stars.
  • Firing the request before handoff happens.
  • Messaging on after a STOP.
  • Using one shared review link with no record of eligible sends.
  • Arguing with a reviewer in public.
Troubleshooting
  • Requests fire before the job is doneTrigger off a verified delivered or completed status, not the scheduled end time, and require final QC or handoff confirmation first.
  • Customers get duplicate asksKeep one request record per job and customer with an idempotent trigger, and test manual and automated sends together.
  • Reviews trickle in slowlyCheck delivery, the link, timing, message clarity, and the service itself before you reach for more reminders or incentives.
04

Finish

Check the result and close the loop.

What good looks like

  • Every eligible customer gets the same treatment.
  • The message is neutral and clearly from you.
  • Opt-outs and quiet hours actually stop sends.
  • Complaints turn into human tasks.
  • Duplicates never go out.
  • Review replies stay privacy-safe.

Final checklist

  • Official link saved
  • Eligibility and exclusions defined
  • Neutral template approved
  • Timing and reminder limit set
  • Opt-outs and quiet hours tested
  • Service-recovery owner named
  • Duplicate protection tested

What to do next

  • Reply to reviews like you mean it.
  • Invite the right customers into a referral program, separately.
  • Fold feedback themes into training.
05

More

Continue only where it helps.

Frequently asked questions
Can I ask only happy customers?

No. Picking recipients by sentiment can violate platform policies and warps your feedback. Use one consistent, neutral eligibility rule.

Can I offer a discount for a review?

Avoid incentives tied to reviews or positive sentiment. If you’re weighing any incentive at all, verify current platform, disclosure, and legal requirements first.

How many reminders are appropriate?

The fewest necessary, usually zero or one, based on consent and channel. Stop immediately on an opt-out, reply, complaint, or completion signal.

Sources and review