Skip to main content
GoodMarksGoodMarks
Built to comply with FTC + Google
All guides
The operator's field guide · 40 tactics

Train your team to ask for Google reviews

Verbal asks, role-specific scripts, coaching drills that don't humiliate anyone, FTC + Google guardrails in plain English, and the metrics that prove the training stuck.

22-min full read5 chapters · 40 numbered tacticsFTC + Google compliant throughout

$30/mo · 7-day free trial · no credit card

Who this guide is for

Owners and managers who know reviews matter but watch their field teams skip the ask because nobody trained them. It scales from two-person shops (you plus one tech) to multi-location groups rolling out a single standard. Compliance is built in, staff are taught routing, not gating, from day one.

How to read this

Read chapters 1-2 if you need scripts tomorrow. Read chapter 4 before anyone says a word to a customer about stars, the FTC and Google lines have to live in muscle memory. Chapter 5 is for after the first month when you want proof the training worked.

  • → I need scripts I can hand out at tomorrow's stand-up

    Jump to chapter 2. Copy the scripts for your roles, trim words until they sound like your shop, and rehearse once aloud. Come back to chapter 4 the same week, compliance isn't optional because the script sounds friendly.

  • → My techs are uncomfortable asking

    Start with chapter 1 (why the verbal ask still wins) and chapter 3 (coaching without shame). The discomfort is usually fear of sounding salesy; the fix is specificity and permission to skip the ask when the job went sideways.

  • → I'm worried about gating or incentives

    Read chapter 4 before you train anyone. The rule your team needs: every customer hears the same choices, public review options stay available regardless of how they rated the visit privately. Pair with the compliance reference at /no-review-gating if you want the line-by-line version.

  • → I need to prove ROI to a partner or DM

    Skip to chapter 5. Track asks attempted, SMS clicks, and reviews attributed to ask-source where your tooling allows. The goal isn't perfect attribution, it's showing movement month over month after training lands.

What this guide deliberately doesn't cover

  • Pay-for-review, contest-for-review, or gift-card-for-review programs. Staff should never mention rewards tied to posting, that's incentivized reviews under Google's policy and 16 CFR § 465.
  • Performance pay purely tied to star averages. Tying compensation to public rating invites gating behavior even when nobody intended it. Chapter 5 covers healthier scorecards.
  • Replacing a structured post-service SMS or email flow. Verbal asks amplify digital follow-up; they don't replace the compliance-safe routing page customers land on after they tap the link.
  • Union or jurisdictional labor topics where asking for reviews could intersect with collective bargaining. Get counsel if you're in that context.

Chapter 01 / 05

Why the verbal ask still wins

Software can schedule texts; it cannot make eye contact. The highest-converting review requests in field businesses still include a human sentence spoken at the right moment, then the automated link does the compliant routing work. These eight tactics cover the conversion math, when to skip the ask, and why generic pep talks fail.

  1. 001

    Face-to-face beats inbox for intent

    Customers who hear a specific, grateful ask from the person who did the work convert to clicks and reviews at several times the rate of contacts who only get an email later. The inbox ask competes with fifty other messages; the on-site ask competes with nothing but the drive home.

  2. 002

    You're training permission, not pressure

    The goal of the verbal layer is to make the upcoming text feel expected and welcome, 'they asked me to look for that message', not to guilt someone into five stars. Staff should sound like they're offering a favor the business actually needs, not collecting a debt.

  3. 003

    Pair every verbal ask with a digital follow-up

    Nobody converts from memory alone. The verbal ask sets context; the SMS or email delivers the tap-through link. Training that stops at 'mention Google' without ensuring the follow-up message fires is training for frustration, customers forget the brand name before they park.

  4. 004

    Skip the ask when the visit went sideways

    If the customer is unhappy, the team's job is recovery, not solicitation. Make it explicit in training: partial refunds, callbacks, and managers take precedence over any review script. Asking in that moment trains customers to associate your brand with tone-deafness.

  5. 005

    Specificity beats enthusiasm

    Staff don't need cheerleader energy; they need one concrete detail from the visit, the outlet they rewired, the haircut length, the deadline you hit. Specificity reads as authentic; generic enthusiasm reads as corporate mandate.

  6. 006

    One owner sponsored this training

    Rolling asks out as 'corporate policy from HQ' without the owner ever modeling it kills credibility. Record a 60-second Loom or close the week with the owner delivering the script once. Teams mirror tone from the top, not from the handbook PDF.

  7. 007

    Why 'I'll send the link' beats 'can you review us'

    Customers fear friction. Promising that you'll send a short text with the link reduces imagined hassle, they don't have to hunt for the business name or spell anything at the curb. Train staff to always pair the ask with that promise.

  8. 008

    Coach outcomes loosely, inputs tightly

    You can't control whether someone posts. You can control whether your team attempted a courteous ask on completed, satisfactory visits. Score the attempt rate before you score the star average, the latter invites shortcuts you don't want.

!

Common mistakes in this chapter

What operators get wrong here

  • Turning the ask into a quota hammer

    Monthly contests for 'most reviews collected' push selective solicitation even when nobody said the quiet part aloud. Public leaderboards on star counts amplify the same failure mode. Keep recognition tied to consistent process, not outcomes you don't fully control.

  • Scripting without rehearsal

    Paper handouts die in gloveboxes. Run live practice, two employees trade roles for five minutes weekly, until the words sound conversational. Awkward reads as robotic; robotic reads as insincere.

Chapter 02 / 05

Scripts by role, techs, desk, stylists

Same company, different moments. Field techs close at the truck; receptionists close at payment; stylists close at the mirror. The ten tactics below give role-specific language, trim until it fits how your shop actually talks.

  1. 009

    Residential trade, at the truck

    Lock eye contact before tools go in the van. Thank them for trusting your crew with the specific job. Promise a short follow-up text with a link if they'd be willing to share how it went, no pressure on the spot.

    Home services, tech closing script

    Thanks again for having us out, we know letting someone into the house is a big deal.
I'm going to text you in a little bit with a quick link. If everything looked good today, a sentence or two on Google helps the next homeowner find us. If anything felt off, hit reply on that text and I'll get it fixed, that's the fastest line to me.
  2. 010

    Commercial trade, at sign-off

    On commercial jobs the purchaser may not be the person who watched the work. Direct the ask to whoever controls the relationship, property manager, facilities lead, and mention the business name clearly for when the text arrives.

    Commercial, account-facing script

    Appreciate you clearing us for the punch list today.
I'll send a short text with our name in it, if the building team is happy with the outcome, Google feedback helps us on the next bid. If something still isn't right, reply on that text before posting publicly and we'll route it to the PM on call.
  3. 011

    Front desk after payment

    Reception owns cash-out warmth. The script should take ten seconds, reference the service product, and mirror the verbal promise that a text or email follow-up is coming, especially when the customer never saw the technician's face.

    Front desk, checkout script

    You're all set, thanks for choosing us today.
You'll get a quick message later with a link. If we earned it, a Google note helps neighbors find us. If we missed anything, that same message is the fastest way to reach the manager, no phone tree.
  4. 012

    Salon chair, mirror moment

    Stylists should ask while the customer is still processing the reveal, not after they've mentally checked out at reception. Keep it optional; beauty clients are sensitive to pressure. Offer Yelp or Google depending on where your shop actually needs density.

    Salon, stylist script

    I'm so glad we got the shape you wanted, send me a selfie later if you try that braid.
I'm going to have the desk text you a link. If you loved today, a quick Google or Yelp line helps us stay booked. If anything settles weird, text back on that message before you post, we can tweak it.
  5. 013

    Restaurant, manager table touch

    Only managers or owners should verbal-ask in dining rooms, servers already manage tip dynamics. The table touch thanks the party for choosing you tonight, acknowledges one highlight the server mentioned, and sets up the printed receipt QR or SMS program you already run.

    Restaurant, manager touch (30 seconds)

    Thanks for hanging with us tonight, hope the ribeye hit the temperature you wanted.
If you have thirty seconds later, the QR on the receipt jumps straight to Google, honest stars keep us cooking for the neighborhood. If something missed, grab me before you walk out, I'll fix it tonight.
  6. 014

    Auto repair, at keys handoff

    Customers pick up vehicles distracted, kids, rain, time pressure. One sentence at key handoff, then SMS backup. Never imply you'll withhold warranty or service based on whether they review.

    Auto, advisor script

    You're back on the road, thanks for trusting us with the brakes.
I'll text you the follow-up survey link in about half an hour when you've had a chance to drive it. Google feedback keeps small shops like ours visible; if anything squeaks, reply to that text before posting and we'll get you right back in.
  7. 015

    Medical and dental, staff boundaries

    Clinical staff should stay clinical; the coordinator owns the ask in HIPAA-safe language, satisfaction with the visit, not outcomes. Never tie reviews to faster appointments or discounts.

    Dental, coordinator script

    Glad we got you comfortable today, we'll see you at the next hygiene visit.
You'll get a quick email with a feedback link. Sharing your experience on Google helps families choose care, if anything about today's visit concerned you, call us directly first so we can respond privately.
  8. 016

    Team translation for multilingual crews

    If the technician and homeowner don't share a first language, pair the verbal moment with a bilingual card or have the lead tech deliver the ask. Don't push review responsibility onto family members translating for free.

  9. 017

    When two employees are on site

    Choose one voice, usually the senior tech or the customer-facing lead. Dual asks feel staged; zero asks because both thought the other handled it is more common. Nail the handoff explicitly: 'Jamie sends the text on our behalf.'

  10. 018

    Escalation lines live next to the ask

    Every script reserves a path for dissatisfaction, reply SMS, manager reach-around, callback. That's not legal ornamentation; it's how you keep routing distinct from gating. Train staff that offering private relief first is service recovery, not suppression.

!

Common mistakes in this chapter

What operators get wrong here

  • Reading the script word-for-word under stress

    Customers forgive imperfect words; they don't forgive robotic cadence. Teach bullet intent instead, gratitude, promise of link, relief valve, and let experienced staff paraphrase within those rails.

  • Letting vendors improvise brand-new promises

    Subcontractors who promise discounts or expedited service 'if you leave five stars' create liability the owner never approved. Either train subs with the same compliance deck or keep them off customer-facing asks.

Mid-guide checkpoint

Scripts are half the system, timing is the other half

Chapters 3-5 cover coaching, compliance, and measurement. For the SMS window that pairs with these verbal asks, read the 30-minute rule , then wire the follow-up through GoodMarks so every customer still sees routing, not gating.

Chapter 03 / 05

Coaching without shame, drills and accountability

Scripts on paper don't change behavior, reps do. These eight tactics cover micro-drills, scorecards that reward effort not stars, and how to debrief missed asks without humiliating anyone in front of the crew.

  1. 019

    Two-minute Tuesday drills

    Weekly, pair people who don't usually work together. Person A plays an irritated homeowner; Person B delivers the ask including recovery language. Rotate roles. Keep it short enough that nobody dreads showing up, consistency beats intensity.

  2. 020

    Record one good example quarterly

    With consent, clip a real customer interaction where the ask landed naturally, audio only if video feels invasive. New hires hear pace and tone better from a teammate than from leadership theater.

  3. 021

    Shadow rides for managers

    Owners should ride along monthly, not to catch mistakes but to model curiosity. Ask the tech afterward what felt off; don't lecture in the driveway. Feedback delayed ten minutes hits better than critique through the earpiece.

  4. 022

    Make 'skip logs' normal

    When someone skips the ask, a one-line reason in the dispatch notes ('customer rushing to ER,' 'dog bite incident') prevents suspicion that they're lazy. It also surfaces systemic barriers, unsafe neighborhoods, language gaps, you can fix with process.

  5. 023

    Debrief privately first

    Public stack ranking on who drives reviews trains gamification you don't want. Coach individuals offline with two stars worth of feedback: what worked in tone, what to tighten next time.

  6. 024

    Tie recognition to documentation

    Celebrate crews who consistently note 'ask attempted' in CRM fields, not crews who 'won the month on Google.' You're reinforcing discipline, not outcomes.

  7. 025

    Rotate the coach

    If only the owner teaches the drill, teams hear performance theater. Let senior techs lead occasional sessions, teaching the script deepens their own adherence.

  8. 026

    Seasonal refresh before rush

    Before holiday dining spikes or HVAC peak season, rerun chapter 2 scripts, seasonal hires forget faster than full-timers. Pair refresh with updated SMS templates so verbal and digital layers stay aligned.

!

Common mistakes in this chapter

What operators get wrong here

  • Punishing missed asks without diagnosing why

    Sometimes dispatch stacked jobs too tight; sometimes customers genuinely fled. Ask what blocked the moment before you assume negligence.

  • Training once during onboarding only

    Behavior drifts. Quarterly refresh plus lightweight drills keeps standards from decaying silently.

Chapter 04 / 05

Compliance guardrails your staff must internalize

Front-line employees won't read FTC citations, they need four memorable rules that keep your business inside Google's policy and the October 2024 trade rule. Seven tactics translate legalese into shift-meeting language.

  1. 027

    Everyone gets the same doors

    If your digital flow routes unhappy customers privately, staff still verbally promise that Google (and other public options) remain available, the unhappy customer chooses relief first; they're never trapped there. Staff language should never imply only happy customers may post publicly.

  2. 028

    Never tie money or speed to stars

    Discounts, waivers, jump-the-line service, raffle entries, all off limits when conditioned on posting or editing a review. Train staff not to negotiate with customers who propose 'five stars for X.' Escalate those conversations to ownership.

  3. 029

    Don't chase edits after comps

    Fix the problem because it's the right thing; mention once that they're welcome to update any feedback if they feel differently afterward, never tie the comp to the edit. Workers should know the safe phrase lives in management's mouth, not theirs.

  4. 030

    Family and friends count as conflicts

    Staff shouldn't solicit reviews from relatives posing as customers, Google removes conflict-of-interest reviews and may flag patterns. If cousins love you, they should actually book paid work like anyone else.

  5. 031

    Never swap reviews with other owners

    Friendly 'you review me, I'll review you' arrangements between business owners violate policy and look like networks to detection systems. Train people to decline politely when another vendor proposes trades.

  6. 032

    Keep proof of what customers saw

    Screenshot your live routing page quarterly. If regulators or platforms ask what customers were offered when they clicked through from SMS, you'll show that public options existed regardless of private rating.

  7. 033

    Escalate threats of fake negatives

    If a customer ties removing a bad review to payment, staff should stop negotiating, document and hand to ownership. Paying extortion invites repeat demands and violates policy.

!

Common mistakes in this chapter

What operators get wrong here

  • Assuming 'the software handles compliance'

    Software can't stop a tech from promising a gift card verbally. Policy has to live in training, not only in the routing UI.

  • Letting sales teams import old review habits

    B2B reps trained in aggressive SaaS cultures sometimes import sketchy incentives when they touch consumer jobs. Put them through the same compliance micro-training.

Chapter 05 / 05

Measuring what front-line asks produce

You can't improve what you don't log, but you also shouldn't turn humans into pure KPI bots. Seven tactics balance attribution honesty with momentum metrics leadership actually cares about.

  1. 034

    Track attempts, not promises

    Simple CRM checkbox: 'Review ask attempted Y/N' on closed jobs. You're measuring discipline spread across the team, before you ever judge star averages.

  2. 035

    Correlate SMS clicks with shifts

    If Monday crews outperform Friday crews on click-through, you're seeing fatigue or scheduling problems, not 'Monday people try harder.' Use the pattern to adjust dispatch or staffing instead of blaming individuals.

  3. 036

    Attribute lightly

    Customers may review days later after prompts from multiple channels. Treat attribution as directional, verbal + SMS combined lift, rather than forensic certainty.

  4. 037

    Review referral sources in stand-up

    Monthly, read aloud three great reviews and note whether the customer mentioned an employee by name. Praise specificity, it reinforces behavior better than abstract quota talk.

  5. 038

    Watch for sudden spikes

    Bursts of reviews after a pep talk may indicate selective pushes or shared devices, both risk flags. Smooth cadence beats heroic bursts.

  6. 039

    Customer complaints about asks

    Log pushback verbatim in QA. If multiple customers say 'your tech pressured me,' slow down the script, that's leading-indicator risk for reputation and compliance.

  7. 040

    Quarterly program retrospective

    Once a quarter, compare attempt rates, SMS CTR, and new reviews, did training updates correlate with lifts? Adjust scripts where data stalls; celebrate crews where attempts rose without bribery.

!

Common mistakes in this chapter

What operators get wrong here

  • Rewarding only positive outcomes

    Incentives tied to published five-stars recreate gating pressure downstream. Reward consistency and documentation instead.

  • Ignoring qualitative feedback

    Stars move slowly; customer language about your team moves fast. Mine reviews for coaching gold, mention technicians by name when they earned it.

Pair the verbal ask with compliant routing

GoodMarks sends the follow-up text your team promises.

Staff own the human moment; GoodMarks owns the timed SMS, the brand page, and the routing logic that keeps public review options available regardless of rating. $30/mo, 7-day free trial.

How routing works

Sources & further reading

Where the rules and companion guides come from

Primary FTC and Google sources, BrightLocal consumer survey context, and internal posts on timing plus the 101-tactic collection playbook.

Last updated

Need the short version? Read the blog post