A sourced review-request workflow for home service operators that want more honest feedback without incentives, fake engagement, or selective positivity.
This playbook is written for a 4-10 truck home service company that needs the office, field, marketing, and money trail to agree before anyone trusts the next report.
The Operator Problem
Show how to operationalize review requests after completed jobs while respecting FTC and Google policy boundaries.
The practical question is whether the company can turn this topic into better booked work, cleaner documentation, and fewer missed follow-ups without inventing unsupported claims.
Source-Backed Checks
- The FTC warns marketers not to mislead people with fake or manipulated reviews. Operator use: Use plain policy-aware language and avoid legal conclusions.
- Google Business Profile policy prohibits fake engagement, review incentives, and selectively soliciting only positive reviews. Operator use: Mention the policy boundary directly when describing automation rules.
- Review workflows should connect to completed work and payment evidence, not just marketing vanity metrics. Operator use: Support with operator finance framing; do not imply SBA reviews policy.
Office Action
- The difference between honest review requests and reputation manipulation
- When a home service company should trigger a request
- Who should be excluded by default
- What the office should do with negative feedback
- How to connect reviews back to job, invoice, technician, and source trail
Field Action
- Ask technicians to capture the job notes, photos, approvals, materials, and exceptions that make the office follow-up defensible.
- Keep safety, tax, platform policy, and code-sensitive observations tied to qualified judgment and the cited source trail.
Customer Communication
- Use the source-backed point as the reason for outreach, then make the customer action simple: schedule, approve, reply, pay, or talk to the office.
- Do not overstate savings, compliance, incentives, or outcomes beyond what the source trail and the company's own job evidence support.
Source Trail
- Tie the article's workflow to the customer, property, call, estimate, job, invoice, payment, and follow-up records wherever those records exist.
- Keep each external claim connected to its claim marker and source marker so a reviewer can audit it before publishing.
Measurement
- Measure booked work, estimate conversion, collection movement, customer recovery, and attributed revenue without giving one message credit for the whole job.
- Compare the result against the source trail, not vanity metrics alone.
What To Avoid
- Do not publish uncited statistics, savings promises, code interpretations, tax advice, or safety conclusions.
- Do not write as if every contractor has the same tools, crew mix, weather, service area, or licensing requirements.
- Do not let the article drift away from the operating record: customer, property, call, estimate, job, invoice, payment, and follow-up.
Sources
1. Soliciting and Paying for Online Reviews: A Guide for Marketers - Federal Trade Commission. 2. Prohibited and Restricted Content - Google Maps User Generated Content Policy Help. 3. Manage Your Finances - U.S. Small Business Administration.
FAQ
Should a contractor only ask happy customers for reviews?
No. A safe workflow should not selectively solicit only positive reviews. Route unhappy feedback for service recovery, but keep review requests honest and policy-aware.
Can a company offer a discount for leaving a Google review?
The safer v1 answer is no. Google policy prohibits incentives for reviews, and FTC guidance warns against deceptive or biased review practices.