My tech is great at their job but terrible at asking. Do I really need to force it?

You don't need every tech asking. If one tech generates great reviews through their work alone (customers mention them by name organically), they earn their bonus through the Named-Tech Rate, not Ask Rate. Adjust the metric weighting per-tech if needed.

What if customers complain that my techs "always ask for reviews"?

That's real feedback — either the script sounds sales-y (adjust tone) or the team is asking the same customer multiple times (fix CRM tagging so repeat customers aren't asked on every visit). Fatigue is a real risk.

Do bonuses need to be per-ask, or can I do a flat monthly bonus for 85%+ ask-rate?

Either works. Per-ask is more motivating daily; flat monthly is simpler to administer. Test both if you want. Many ops teams settle on: small per-ask + monthly milestone bonus stacked.

Can I incentivize 5-star reviews specifically?

No. Violates Google + Yelp policy, creates selection bias (techs only ask happy customers), invites filter algorithms to flag your reviews as manipulated. Pay for asks and named mentions, not star counts.

What do I do about techs who get negative reviews?

Treat them like any other performance data. If a tech has 2 one-star reviews out of 40, that's noise. If they have 5 one-star out of 20, that's a signal — ride along, coach, retrain. Use our negative review response playbook to handle the posted reviews themselves.

Playbook

How to Train Your Team to Collect Reviews

⚡ TOO LONG, DIDN’T READ — The best review-collection teams: (1) have one 90-second script everyone uses, (2) ask at the right moment (immediately after delivering value), (3) measure per-tech ask rate + conversion rate, (4) pay bonuses for specific mentions (tech name in review = bonus), (5) coach not punish when numbers dip.

Why Your Team Beats Automation Alone

Automated SMS review asks convert at about 8-12%. A tech asking face-to-face, in the moment, immediately after doing a great job? 30-50%. The math:

100 jobs/month × 10% automated = 10 reviews
100 jobs/month × 40% human + automated follow-up = 40 reviews

That’s the difference between “we’re rated 4.3 with 80 reviews” and “we’re rated 4.8 with 600 reviews” over a year. Same customer base, same product — different collection muscle.

But most business owners can’t get their team to ask consistently. The reason isn’t laziness. It’s:

Awkwardness — techs feel weird asking
No script — they improvise, fumble, give up
No measurement — they don’t know if they’re doing it
No incentive — their pay doesn’t move whether they ask or not

This playbook addresses all four.

The One Script

Do not let your team improvise. One script, memorized, universal. Here’s the format:

The Universal Review Ask

SCRIPT · 90 SECONDS

1. ACKNOWLEDGE SPECIFIC WORK (15 sec):
"All set! Your {specific thing we fixed} is working again. I also {bonus detail: checked the connections, cleaned up, etc.}."

2. CHECK SATISFACTION (15 sec):
"Is there anything else you need from me before I head out?"
[Wait for answer. Address anything that comes up.]

3. MAKE THE ASK (20 sec):
"If you're happy with today, the biggest thing that helps {Owner name's family-owned} shop is a quick Google review. I can text you the direct link right now — takes 30 seconds. Would you mind?"

4. GIVE THE DIRECT CTA (10 sec):
Tech hits "Send Review Ask" button in app → SMS fires with direct link.
"Just texted it — takes 30 sec when you have a moment."

5. PARTING WARMTH (30 sec):
"Thanks for trusting us — we don't take it for granted. If you ever need anything, {tech's direct line or shop line}."

Critical parts of this script:

“Happy with today” not “if we earned a 5-star review” — keeps it about their experience, not the rating
“I can text you the direct link right now” — removes friction, not a “check your email tomorrow”
“Family-owned shop” (or equivalent) — human framing, not corporate
Send the SMS in front of them — they see it arrive, much higher conversion

Timing — When to Ask

Timing is as important as the ask itself. Universal rule: ask at the moment of peak relief/satisfaction.

Industry	Ask timing	Why
Home services (repair)	Immediately after tech confirms the fix works	Peak relief moment
Home services (install)	After final walkthrough + customer tests it	Customer owns the success
Cleaning (weekly)	On first-of-month visits only, not weekly	Avoid ask fatigue
Restoration	Final walkthrough, punch-list complete	Long project close-out
Restaurant (dine-in)	When server drops check	Meal satisfaction + payment trigger
Retail	After sale at register, before bag	Purchase confidence peak
Salon/spa	After seeing self in mirror + pay	Visible transformation moment
Appliance repair	After customer operates the appliance themselves successfully	They confirm the fix

⚠️ DON’T ASK IF — The job went poorly, a callback happened, the customer showed frustration, or the tech has a bad feeling. Asking for a review in those moments invites a 1-2 star review. Instead: pulse-survey them first (1-10 rating), route based on response. See our 24-hour response rule playbook for why.

The 60-Minute Training Session

One-time, 60 min, all team. Do this in person, not via Zoom, not via email. Structure:

The Why (10 min)

Show the team your current Google/Yelp/Facebook ratings. Then show top-rated competitors. Then show your actual review growth with + without asks (pull the data from your CRM). Make it concrete and personal: “If we get to 4.8★ with 300 reviews, we add {X} leads per month, which means {Y} more jobs for you all.”

The How (15 min)

Read the script together. Then role-play in pairs — one tech plays customer, one plays tech, swap. 2 rounds each. Have the skeptic / awkward team member go first — once they can do it, anyone can.

The What-Ifs (10 min)

Address objection scenarios out loud:

“Customer says they don’t have Google account” → “That’s fine, skip it; just let me know if you ever want us back.”
“Customer starts listing problems” → “Stop asking. Address their problem. Reschedule if needed.”
“Customer says ‘you can write it yourself’” → “We can’t — Google tracks IP addresses. But thanks for trusting us that much.”
“Customer forgets and never leaves it” → Automated 24-hour follow-up SMS handles it.

The Metrics (10 min)

Show the team the dashboard they’ll see: per-tech ask-rate, per-tech conversion-rate, total company volume. Explain: “We track if you asked, not if they left one. You can’t control whether they review. You can control whether you ask.”

The Incentive (10 min)

Explain the bonus structure (next section). Make it clear, make it achievable, make it visible.

The Start Date (5 min)

“Starting Monday, every job gets the ask. If you forget, that’s fine — tomorrow’s another chance. If you don’t ask on purpose, we’ll have a conversation. Questions?”

The Compensation Model

Don’t pay for reviews received — that’s a policy violation and creates bad incentives. Pay for asks made. Here’s the simplest structure:

Metric	Bonus	Why this structure
Per ask made (via app button)	$2-5	Rewards consistent effort, not outcome
Bonus per review mentioning tech by name	$10-25	Incentivizes quality service that gets remembered
Monthly top performer (most asks)	$50-100 or swag	Public recognition drives repeat
Team bonus at review milestone	$10-25 per person when company hits 4.9★ or review count milestone	Shared stake

Budget: a 10-person team, $3/ask, 3 asks/tech/day = ~$18,000/year in asks bonuses. Pays for itself in ~2-3 new customers/month from the elevated rating.

⚠️ POLICY COMPLIANCE — Never pay for the review itself (Google/Yelp forbid it). Pay only for the action of asking, tracked in your system. Never pay bonuses specifically for 5-star reviews or high ratings — creates selection bias. Pay equally whether the review turns out to be 3-star or 5-star.

What to Measure (The Dashboard)

Per tech, weekly rolling:

Ask Rate = asks made ÷ eligible jobs (target: 85%+)
Conversion Rate = reviews received ÷ asks made (target: 30%+)
Named-Tech Rate = reviews mentioning the tech by name ÷ total reviews (target: 40%+)
Avg Star Rating of reviews from their customers (coaching signal; don’t over-weight)

Per company, weekly:

Total reviews this week
Overall Google/Facebook/Yelp star trend
Ranking in local search (rank tracker)
Leads attributed to reviews (via lead-source tracking)

Post the dashboard publicly in the shop/break room. Visibility drives improvement more than coaching does.

Track per-tech performance automatically

Reveo logs asks, conversions, named-tech rates, and shows dashboards per tech + company-wide.

Coaching — When Numbers Dip

One tech is at 30% ask-rate when the team average is 85%. How to coach:

Assume it’s a tools or awkwardness problem, not laziness

Ask: “Walk me through the last job. What did the conversation look like when you thought about asking?” Let them tell you where it broke down. Usually it’s one of: forgot the script, couldn’t find the button in the app, customer was in a rush, awkward feeling.

Fix the specific friction

If they forgot the script, tape it to their phone case. If they can’t find the button, walk them through the app. If awkwardness, do a ride-along and demonstrate once.

Set a specific goal

“Get to 60% by next week, 85% by end of month.” Check in at the end of week 1.

If it doesn’t improve, have the direct conversation

“Everyone else is at 85%+. You’re at 35%. Is there something I should know?” Sometimes there’s a legit reason (shy, English-second-language, physical anxiety). Adjust the ask (SMS-based rather than in-person). Sometimes it’s attitude — then it’s a performance issue, not a training issue.

Office Staff Training

Office staff (dispatchers, CSRs) have review-collection opportunities too:

On phone closure: “Thanks for calling in — we’ll follow up with a link later, but if you’re happy with how we handled that, a quick online review helps us out.”
On email replies: signature includes a review link + 1-line ask
On scheduling confirmations: “…and after we’re done, you’ll get a quick text about reviewing — no pressure but it means a lot.”

Office staff typically drive 15-25% of total review volume when trained. Don’t overlook them.

Onboarding New Hires

When you hire a new tech: include the review-ask script in the onboarding packet (not as an afterthought — as a top-5 item). Shadow ride-along on day 3 specifically to demonstrate the ask. Set ramp expectations: full ask-rate target by end of month 2.

Don’t let review-collection become something only senior techs do. It’s part of the job from day one.

Summary: Your 30-Day Rollout Plan

Week 1: Write your one-script (adapt from above). Set bonus structure. Set up dashboard in your CRM.
Week 2: Run the 60-min training session. All hands.
Week 3: Shadow ride-alongs with each tech. Fix friction. Encourage openly.
Week 4: Review first full month of data. Celebrate wins (publicly). Coach gaps (privately).
Ongoing: Weekly 10-min huddle on the numbers. Quarterly refresh training. Update script if something isn’t working.

Or — use Reveo for the tracking + dashboards + automated follow-ups so your team only has to do the in-person ask.