A policy-compliant solar reputation management workflow for US installers: when to request reviews at real job milestones, how to respond within Google and FTC rules, and what to measure.
Solar reputation management is the discipline of earning and responding to reviews across a sale that takes weeks or months, not minutes. If you run a US solar installation company, this is the workflow for asking at the right job milestones and replying inside Google and FTC rules.
Get the timing wrong and you either nag a homeowner who has not seen a working system yet, or you go quiet for the exact months when trust is being built. Get the rules wrong and a discount-for-reviews offer, or a public argument over an inverter, can create a bigger problem than a one-star review.
This guide stays inside the lines: the milestones that legitimately trigger a request, the consent and channel rules, how to respond and route complaints, how to handle fake or competitor reviews, and what to measure without promising counts, ratings, rankings, or revenue.
Here is what you will learn:
- Why solar reputation behaves differently from emergency trades and appointment businesses
- The exact job milestones that make a review request legitimate
- Consent, channel, and message rules that keep the ask compliant
- How to respond and route warranty, inverter, and production complaints
- How to document and report fake or competitor reviews within the rules
- What to measure, and which promises to never make
Why reputation behaves differently for a solar installer
Solar reputation management differs from other trades because the purchase is planned, permitted, high-ticket, and low-urgency. A homeowner decides with a spouse, an HOA, a lender, and a utility across weeks or months. Trust builds through referrals and reviews over that cycle, not at one emergency moment like a burst pipe.
The sales cycle is the difference. A solar install is a five-figure, permitted project that touches the roof, the electrical panel, the utility meter, and often a loan. The homeowner rarely decides alone. A spouse, a homeowners association, a lender, and the utility all weigh in before anyone signs, and that can take weeks or months.
Because nothing happens at an emergency moment, trust is earned slowly. Referrals, photos of completed installs, and public reviews carry more weight than a fast arrival time. Google's eligibility rules require real in-person customer contact during stated hours and exclude lead-gen or online-only entities, which fits how installers actually survey roofs and commission systems. A federal residential clean-energy credit can shape how buyers frame the purchase; the IRS sets current eligibility and rates, so confirm there rather than rely on a fixed figure. For the generic, non-vertical view of this work, see our guide to SEO reputation management.
The solar job milestones that legitimately trigger a review request
A solar company may request a review only after a genuine, completed, positive service moment. The legitimate triggers are a finished site survey, a signed proposal, an approved permit, install day, a passed inspection, utility permission to operate, and the first monitored production month. Asking earlier manufactures pressure, not proof.
Map every requestable moment to a milestone the customer can feel. A request is legitimate only when real service was delivered and the experience was positive. Asking at contract signing, before the crew has done a thing, manufactures pressure rather than proof. The table below fixes the trigger, the consent gate, the channel, the owner, and the evidence that the milestone truly finished.
| Milestone | Request eligible | Consent gate | Channel | Owner | Evidence it completed |
|---|---|---|---|---|---|
| Site survey done | Yes, if positive | Recorded opt-in | Email or onsite | Operations | Signed survey report and photos |
| Proposal signed | Yes, if positive | Recorded opt-in | Sales | Executed contract and deposit | |
| Permit approved | Yes | Recorded opt-in | Operations | Authority permit approval notice | |
| Install day | Yes, end of day | Recorded opt-in | Onsite or SMS | Crew lead | Completed job card and site photos |
| Inspection passed | Yes | Recorded opt-in | Email or SMS | Operations | Inspector sign-off record |
| Permission to operate | Yes | Recorded opt-in | Operations | Utility interconnection and PTO letter | |
| First production month | Yes | Recorded opt-in | Retention | Monitoring data for month one |
Two milestones deserve extra care. Install day captures crew quality, cleanliness, and schedule. Permission to operate and the first monitored production month capture whether the system performs as promised. Choose the moment that matches what was actually delivered, and log it against the job.
Turn your job milestones into a compliant review rhythm. theStacc's Local SEO module monitors and replies to reviews and watches local visibility, so the operational half of this workflow stays covered while your crews stay on the roof.
Consent, channel, and message rules for the request
Ask only genuine customers, and pick the channel by consent: email, SMS, onsite, or a post-service handoff. Email used commercially triggers CAN-SPAM duties. Use one clear ask, one owner, no incentive, no sentiment condition, and no gating. Log the source, milestone, consent basis, and timestamp every time.
Google permits asking genuine customers for reviews, prohibits incentives and fake engagement, and expects privacy-aware public replies. The ask itself is simple: one clear request, from one owner, with no reward and no condition on the rating. For general phrasing you can adapt, see our guide on how to ask customers for reviews and our playbook to earn more Google reviews for a local business; keep the solar timing rules here when you do.
Email used commercially triggers CAN-SPAM: an accurate sender, a non-deceptive subject, required disclosures and a physical address, and a working opt-out. SMS needs its own consent basis. Onsite and post-service handoffs rely on a recorded verbal or written opt-in. Whatever the channel, log the source, the milestone, the consent basis, and the timestamp, and suppress anyone who opts out.
| Channel | Consent source | CAN-SPAM applies | Opt-out / suppression | Owner | Stop condition |
|---|---|---|---|---|---|
| Contract or post-service opt-in | Yes, when commercial | Working unsubscribe link | Operations | Any unsubscribe or complaint | |
| SMS | Separate written text consent | No, other rules apply | Reply STOP honored | Operations | STOP reply or revoked consent |
| Onsite | Verbal opt-in at install | No | Recorded decline | Crew lead | Customer declines on site |
| Post-service handoff | Card or QR at closeout | No, unless emailed | Suppression list | Retention | Duplicate or prior opt-out |
Responding to positive, mixed, and negative reviews
Assign one response owner and answer every genuine review in a calm, specific voice. Thank positive reviewers, acknowledge mixed feedback, and move complaints offline fast. Never expose a customer's system, address, or financing details in public. Route warranty, inverter, and production complaints to service rather than arguing them in the reply.
Replies are public and permanent, so treat them as part of the service record. Thank positive reviewers by name and reference the milestone without repeating private details. Acknowledge mixed feedback and offer a path to fix it. Move anything negative, financial, or technical offline quickly. Our review management guide covers the generic mechanics; the solar twist is that warranty, inverter, and production complaints belong to service, not to a public argument.
| Review type | Response owner | Public vs offline | Privacy limit | Documentation step |
|---|---|---|---|---|
| Positive | Reputation owner | Public thank-you | No system or address detail | Log reply and date |
| Mixed | Reputation owner | Public, then offline | No financing terms | Note the fix offered |
| Negative | Reputation owner | Offline fast | No personal data | Open service ticket |
| Warranty or defect | Service lead | Offline only | No serial or address | Warranty case number |
| Suspected fake | Reputation owner | Do not argue | No accusations in reply | Screenshot and report |
| Competitor | Reputation owner | Report, minimal reply | No public claims | Evidence file saved |
Fake, incentivized, and competitor reviews: detection and handling within the rules
The FTC Consumer Reviews and Testimonials Rule and Google's policies prohibit fake reviews, bought reviews, and incentives conditioned on positive or negative sentiment. Document suspected fake or competitor reviews with screenshots and dates, then report them through the platform. Do not buy counter-reviews, offer offsets, or publish fabricated rebuttals under any condition.
The FTC Consumer Reviews and Testimonials Rule prohibits specified fake and false reviews and any incentive conditioned on positive or negative sentiment. Google's review policy bars fake engagement and incentivized reviews. Together they mean you cannot buy reviews, gate unhappy customers away from public platforms, offer a discount or gift for a review, or coach a rating.
When a review looks fake or appears to come from a competitor, slow down and document. Capture screenshots, the URL, the date, and the reason it seems non-genuine. Report it through the platform's removal process and keep the evidence. Do not publish a fabricated rebuttal, do not buy counter-reviews to bury it, and do not threaten the reviewer. If the platform declines removal, escalate with the same record rather than litigating in the reply box.
What to measure (and what not to claim)
Measure inputs and operations, never promises. Track milestone-tagged request rate, response coverage and time, and funnel linkage from a qualified enquiry to a booked and completed job. Treat review count and rating as inputs, not outcomes. Report no ranking, Map-Pack, lead, conversion, or revenue claim from this program.
Treat reviews as inputs to a longer funnel, never as the result. The numbers worth watching are operational: how often a completed milestone produced a compliant request, how fully and how quickly genuine reviews received a public reply, and whether a qualified enquiry can be linked to a review surface. Where GA4 is configured, map separate lead events such as generate_lead, qualify_lead, and close_convert_lead and let the business define when each fires.
Keep every funnel stage separate. An impression, a click, a call click, a form, a qualified enquiry, a booked job, and a completed job are different events with different sources and owners. A review, a click, or a form is never a booked or completed job. The dictionary below holds the line.
| Stage | Business rule | Source system | Owner | Timestamp |
|---|---|---|---|---|
| Impression | Profile or page was shown | GBP insights, Search Console | Marketing | Event date |
| Click | Viewer opened the site or profile | GBP insights, analytics | Marketing | Click time |
| Call click | Viewer tapped the call button | GBP insights, call tracking | Marketing | Tap time |
| Form | Review or quote request submitted | Form tool, CRM | Intake | Submit time |
| Qualified enquiry | Meets area, service, and budget rules | Intake, CRM source field | Intake owner | Qualification time |
| Booked job | Signed contract or scheduled install | CRM | Sales owner | Booking time |
| Completed job | Install passed inspection and PTO or commissioned | Job management, CRM | Operations | Completion time |
The formulas below are the only ones approved for this program. Keep every field when you report them, and never turn them into portable benchmarks or rating promises.
| Formula | Numerator | Denominator | Evidence window | Source system | Owner | Exclusions |
|---|---|---|---|---|---|---|
| Milestone request rate | Unique completed milestones that triggered a compliant request | All unique completed milestones of that type in the window | One declared 30-day window | Job-management and CRM milestone log plus request log | Operations or retention owner | Milestones without completed service, duplicate requests, out-of-area or unsupported jobs |
| Review response coverage | Genuine reviews that received an on-policy public reply | All genuine new reviews in the same window | One declared 30-day window | GBP or review-platform log | Reputation owner | Suspected-fake reviews under report, duplicate imports, non-customer reviews |
| Qualified-enquiry attribution | Qualified enquiries whose source includes a review surface | All qualified enquiries in the cohort window | One declared 30-day cohort plus declared lag | Intake and CRM source field, GA4 events where configured | Intake owner | Duplicates, spam, employment or vendor enquiries, unsupported geography or services |
| Booked-job attribution | Booked jobs linked to the same cohort | Qualified enquiries in the cohort | Cohort window plus sales-cycle lag | CRM | Sales owner | Reschedules counted once; cancellations before install stay booked, not completed |
Run this failure-state checklist each month before you report anything:
- Request sent before any service was completed
- Duplicate request to the same customer for one milestone
- No consent record attached to the request
- Incentivized or sentiment-conditioned ask
- Private system, address, or financing detail exposed in a public reply
- Reviewer is not a genuine customer
- Out-of-area or unsupported job included in the numbers
- Warranty complaint argued in public instead of routed to service
Measure the workflow without promising outcomes. We can help you set up milestone-tagged requests, response coverage, and qualified-enquiry tracking so you report inputs and operations, not wishful numbers.
Build vs. buy: in-house workflow, a review tool, or a service
Choose between an in-house workflow, a review tool, or a service on evidence, not claims. Require consent logging, milestone-based triggers, multi-location support, privacy controls, and suppression of duplicates. No tool can manufacture genuine reviews; it can only make a compliant ask at the right moment and record what happened.
You can run this in-house, with a review tool, or through a service. The right choice depends on volume, locations, and how disciplined your consent logging is. Judge options on evidence: do they trigger from real milestones, record consent, suppress duplicates and opt-outs, support multiple locations, and protect customer privacy. No tool can manufacture genuine reviews; it can only fire a compliant ask at the right moment and store the record.
| Criterion | What to require |
|---|---|
| Consent logging | Stored source, milestone, basis, and timestamp per request |
| Milestone triggers | Requests fire only from completed, positive service moments |
| Multi-location | Separate profiles, owners, and logs per branch or crew area |
| Privacy controls | Public replies never expose system, address, or financing detail |
| Suppression | Opt-outs, duplicates, and non-customers are excluded automatically |
| Reporting | Inputs and operations only, with no rating or ranking promise |
Where software helps, keep claims to capability. Our Local SEO module covers Google Business Profile posts, review monitoring and replies, citations, and rank tracking for local visibility. Our Content SEO module can research, draft, and queue the educational content that earns review-worthy service over a long cycle. Neither one auto-generates, buys, gates, or guarantees reviews. You can compare current plans on the pricing page.
FAQ
These answers cover the questions solar owners ask most about timing, incentives, negative feedback, fake reviews, email rules, and ownership. Each one gives a direct position first, then the reason. They reflect current Google and FTC references and are not legal advice; confirm state and local requirements with your own counsel.
When should a solar company ask a customer for a review?
Ask only after a genuine, completed, positive service moment, never before. For solar, the natural points are a finished site survey, a signed proposal, an approved permit, install day, a passed inspection, utility permission to operate, or the first monitored production month. Tie each ask to one milestone, one owner, and a logged consent record.
Can a solar installer offer a discount or gift for leaving a review?
No. Google's review policy and the FTC Consumer Reviews and Testimonials Rule prohibit incentives tied to reviews and any incentive conditioned on positive or negative sentiment. Do not offer a discount, gift, referral credit, or entry in exchange for a review, and do not condition a benefit on leaving one or on the rating given.
How should a solar company respond to a negative review about an inverter or production issue?
Acknowledge the concern, avoid exposing system, address, or financing details, and move the conversation offline to service. A production or inverter complaint is a warranty or service matter, not a debate to win in public. Give the owner a direct contact, document the issue, and let the service team resolve and follow up.
What should a solar company do about a suspected fake or competitor review?
Document it first: capture screenshots, the URL, the date, and why it appears non-genuine. Then report it through the platform's review-removal process rather than replying in anger. Do not buy counter-reviews, offer incentives to bury it, or post fabricated rebuttals. Keep the evidence so you can escalate if the platform declines removal.
Does asking for reviews by email fall under CAN-SPAM?
Yes, when the email is commercial. CAN-SPAM applies to commercial email, including B2B messages, and requires an accurate sender, a non-deceptive subject, required disclosures and a physical address, and a working opt-out. A review request sent by email should meet those duties and honor suppression so the same customer is not asked repeatedly.
Should a solar company ask for reviews at install day or after permission to operate?
Either can work if the milestone is complete and the experience was positive, but they capture different things. Install day reflects crew, cleanliness, and schedule; permission to operate and the first production month reflect that the system performs as promised. Pick the moment that matches the service delivered, and never ask before that moment is real.
Do more Google reviews guarantee more solar leads or a higher ranking?
No. Review count and rating are inputs, not promises, and no compliant program can promise a ranking, a Map-Pack position, a lead count, or revenue. Demand for the exact head term was recorded as unavailable in the brief's research, so treat any traffic or ranking forecast with caution. Measure request rate, response coverage, and qualified-enquiry linkage instead.
Who should own review requests and replies inside a solar company?
Split ownership by job. An operations or retention owner triggers milestone-tagged requests and keeps the consent log. A named reputation owner writes or approves public replies and watches response time and coverage. An intake owner tags qualified enquiries by source, and a sales owner reconciles booked and completed jobs against the same cohort.
Putting the workflow into practice
A compliant solar review program is a small set of habits tied to real job milestones, not a push for volume. Ask only after genuine service, keep one owner, protect privacy, and measure inputs rather than promises. Start with the milestone map, add consent logging, and review the failure-state checklist each month.
- Pick the milestones that match your jobs and write down the evidence that each one finished.
- Assign one request owner and one response owner, and record consent on every ask.
- Keep replies public, brief, and privacy-safe; move warranty and production issues to service.
- Report request rate, response coverage, and qualified-enquiry linkage, and nothing that sounds like a promise.
Solar reputation management rewards patience and documentation. The companies that win trust over a long cycle are the ones that ask at the right moment, answer like operators, and stay inside the rules.
Build the solar review workflow once and run it every month. Pair milestone-based requests with theStacc's Local SEO monitoring and Content SEO drafting, and keep every ask inside Google and FTC rules.
Sources & references
- [1] Google Business Profile Help — get reviews: ask genuine customers, no incentives or fake engagement, privacy-aware replies
- [2] Google Business Profile Help — eligibility requires real in-person customer contact; lead-gen and online-only entities are ineligible
- [3] FTC — Consumer Reviews and Testimonials Rule Q&A: fake/false reviews and sentiment-conditioned incentives prohibited
- [4] FTC — CAN-SPAM Act compliance guide: accurate sender, non-deceptive subject, disclosures and address, working opt-out
- [5] Google Analytics Help — recommended lead events (generate_lead, qualify_lead, close_convert_lead); business defines when each fires
- [6] IRS — Residential Clean Energy Credit: federal credit exists; current eligibility and rates set by the IRS, verify there
Rank in the Map Pack, collect reviews, and keep every location active — on autopilot.