A practical workflow for electrical contractors to request genuine reviews fairly, reply without exposing job details, manage complaints privately, and turn repeat themes into process fixes.
Electrician reputation management is not a campaign to collect praise. It is an operating routine that links a real service event to a fair request, a privacy-safe public reply, a private concern path, and a record of what the office and field team should improve next time.
That distinction matters in electrical work. A short service call, a quoted panel-upgrade project, an after-hours power concern, and a return visit do not create the same customer context. The customer may remember arrival communication, access coordination, estimate clarity, cleanup, or a missed handoff more clearly than the task itself. A useful reputation process preserves that context without publishing it.
This guide is for the owner or service manager who needs repeatable decisions, not a rating target. It uses Google and FTC policy boundaries as practical guardrails: requests should seek genuine feedback, not incentives or filtered positivity; public replies should protect private information; and disputed matters need a separate owner and record. For the broader mechanics, see our review management guide.
What Electrician Reputation Management Covers
Electrician reputation management covers the path from a documented customer event to a neutral review invitation, monitored feedback, a privacy-safe public response, private escalation, and process learning. It does not manipulate ratings, select only happy customers, bargain over criticism, or promise leads, contacts, or revenue, and it never treats a public profile as the company’s complaint file.
For an electrical contractor, the unit of work is a service event with a traceable state. That could be a scheduled troubleshooting visit, an estimate that did not become work, a larger quoted project, a return visit, or a cancelled call. The purpose is not to label a customer as good or bad. It is to make sure the same operating rule is applied to comparable events.
A review request is only one handoff. Monitoring tells the office that something was published. A reply gives the business a restrained public acknowledgement. Escalation assigns ownership for matters that need facts, records, or qualified review. Learning converts repeated themes—such as arrival expectations or estimate handoffs—into a process action instead of a debate under a review.
| Workflow stage | Electrical-service context | Output |
|---|---|---|
| Record | Service call, project state, or return visit | Complete internal service-event record |
| Decide | Consistent eligibility and communication permission | Neutral request or no request |
| Respond | Feedback mentions arrival, scope, access, or another experience | Public acknowledgement and private path where needed |
| Escalate | Technical, damage, safety, legal, or qualification allegation | Assigned owner and preserved record |
| Learn | Repeated operational theme | Named process action with an owner |
The process should sit beside, not inside, an electrical contractor’s local-visibility work. If the aim is accurate business information and local presence, use the separate electrical contractor local SEO guide. This page is about treating customer feedback as an accountable service process.
Start With a Complete Electrical Service Record
A complete electrical service record gives the office enough context to make a fair request or escalation decision without reconstructing a job from memory. It should describe the service event and its current state, while keeping sensitive customer, technical, and allegation details in the appropriate private record.
The record is not an electrical worksheet for public use. It is a handoff tool. Its fields should help the office distinguish a completed visit from an estimate-only contact, a cancelled call from an incomplete event, and a completed project from a return visit with an unresolved concern. Without that distinction, a request system becomes inconsistent quickly.
Keep the customer-visible scope in plain terms. Note whether the customer had an arrival expectation, whether access coordination affected the visit, who in the field and office owns the next action, and whether a return visit is open. Store evidence locations rather than copying private material into review tools or reply drafts.
| Record field | Why the office needs it | Handling note |
|---|---|---|
| Service category and date | Identifies the event being considered | Use internally; do not publish it in a reply |
| Job type (emergency or planned) | Separates no-power, breaker-trip, or burning-smell calls from rough-in, panel-upgrade, or warranty work | Drives request timing; keep internal |
| Permit or inspection status | Shows whether sign-off is pending or complete | An unsigned inspection keeps the request paused |
| Service area | Confirms the job sits inside the represented operating area | Exclude events outside the service area |
| Field and office owner | Clarifies who records and who follows up | Assign one accountable owner per open item |
| Customer-visible scope and state | Separates completed work, estimate-only, and return-visit states | Keep descriptions neutral and brief |
| Access and arrival notes | Provides context for schedule-related concerns | Do not disclose them publicly |
| Contact permission and complaint status | Controls whether communication can proceed | Pause promotional automation for open concerns |
| Evidence location | Lets the assigned owner review the actual record | Link internally; avoid copying sensitive details |
The record should also tag job type, permit or inspection status, and service area. A no-power, breaker-trip, or burning-smell call is not timed like a planned rough-in, panel upgrade, or warranty visit, and an inspection that has not been signed off keeps any promotional request paused.
A record also protects the field team from being asked to improvise the office’s policy. The electrician can document what happened and flag an unresolved issue. The office can then decide whether a neutral request is appropriate, whether the matter belongs in service recovery, or whether a qualified internal owner needs to take it further.
Set a Fair Review-Request Eligibility Rule
A fair eligibility rule starts with a genuine completed customer service event and applies consistently across comparable events. It does not predict sentiment, offer an incentive, pressure the customer at the jobsite, require a particular rating, or set a staff quota for reviews or praise.
Google says businesses may remind customers to leave genuine reviews and may use a review link or QR code, while prohibiting incentives for posting, changing, or removing reviews. Google Maps policy also prohibits fake engagement, biased or selective positive solicitation, and pressure to include specified content. The FTC similarly cautions against asking only people expected to be positive. Read the underlying Google review policy and FTC marketer guidance when setting the written rule.
Write a small rule that a dispatcher can apply without guessing: eligible means a real event reached its documented completed state, the contact permission is present, and no open concern is marked. That is different from deciding whether the customer sounded pleased. The rule should produce the same outcome when two similar service calls are reviewed by different staff members.
Selecting customers by predicted satisfaction, such as sending the public-review link only to people who sound pleased and routing everyone else to a private form, is review gating and is prohibited. Eligibility must come from the documented completed event and the written rule, never from a guess about sentiment.
| Eligibility rule element | What it records |
|---|---|
| Completed service event defined | The documented state that counts as a finished job |
| Job-type tag | Emergency (no power, breaker trip, burning smell) or planned (rough-in, upgrade, inspection, service call) |
| Permit/inspection sign-off status | Whether a required permit or inspection is signed off or still open |
| Contact-permission status | Whether the customer has permitted this communication |
| Pause condition | Any open concern, safety note, damage claim, or unsigned permit/inspection that suppresses the ask |
| Owner | The office or reputation owner who applies the rule |
| Source system | The job-management record and request log the decision is read from |
| Event state | Request status | Reason |
|---|---|---|
| Completed service | Eligible if permission and no open concern | A documented genuine customer event exists |
| Estimate only | Follow the written policy; do not assume | It is not the same state as completed service |
| Cancelled call | Not eligible | No completed service event is recorded |
| Return visit | Hold until the event is closed | Open follow-up can change the customer context |
| Open complaint | Pause promotional automation | Service recovery needs its own path |
| Employee or family | Not eligible | It does not represent an independent customer experience |
| Duplicate request | Do not send again | One event should not create repeated pressure |
| Unsupported job record | Not eligible | The office cannot verify a genuine event |
| Job type | When a neutral request may be appropriate | What suppresses it |
|---|---|---|
| Emergency: no power, breaker trip, or burning smell | Only after the hazard is cleared and the job is closed, if at all | Any open safety note, unresolved hazard, or follow-up visit |
| Planned rough-in | When the rough-in milestone is complete and no concern is open | An open scope question or a pending follow-up |
| Final inspection / permit sign-off | After the inspection is signed off and the record is closed | An unsigned inspection or a failed or pending re-inspection |
| Panel or service upgrade | After the project reaches its documented completed state | An open punch item, warranty note, or damage claim |
| Warranty or service call | Only after the return visit is closed with no open concern | An unresolved complaint or any active pause condition |
Neutral wording can be simple: invite the customer to share an honest experience through the chosen platform. Do not add “if you were happy,” request five stars, suggest phrases, or offer a discount, credit, drawing entry, or other consideration. For generic message formats, use our guide to asking local-business customers for Google reviews alongside this electrical-event rule.
Give Field and Office Teams a Safe Handoff
Field and office teams need separate responsibilities so a review request never depends on an electrician improvising policy at a customer’s property. Field staff record the event and any unresolved issue; the office owns eligibility, communications, public replies, escalation assignment, and the resulting process record.
That separation fits the realities of electrical work. The person arriving at a home, coordinating access with a property contact, or completing a quoted-project milestone may be focused on the immediate service event. Asking that person to judge customer sentiment or obtain praise makes the rule subjective and can put pressure on the interaction.
| Handoff card | Field team | Office team |
|---|---|---|
| Event close | Record completed, cancelled, return-visit, or open state | Check the state against the eligibility rule |
| Unresolved issue | Flag it without public commentary | Pause request automation and assign a concern owner |
| Customer contact | Record communication permission where applicable | Send a neutral request only when eligible |
| Published feedback | Route it to the office; do not argue in the field | Draft reply, preserve records, and escalate when required |
| Learning | Provide factual operational context | Code the theme and own the process action |
Give both teams a short escalation vocabulary: open concern, record needed, private follow-up, and assigned owner. Avoid a script that asks for praise or tells employees to turn a complaint around. A safe handoff is factual, time-stamped, and narrow enough that the office can locate the right record without putting customer information into a public channel.
Keep Review Requests Separate From Service Recovery
Service recovery and review requests must stay separate because an unresolved customer concern requires ownership and facts, not promotional messaging. An open concern should pause automated outreach, but it cannot become a condition that blocks a customer’s public review path or a bargain over what they say publicly.
In practice, a concern can arise after a service-call arrival window, a property-access mix-up, an estimate or scope misunderstanding, a return visit, or a customer’s claim about qualifications, damage, or a safety issue. This article does not decide those matters. It sets the communications boundary: route them privately, preserve the record, and give the assigned owner room to review the facts.
| Recovery condition | Promotional review ask | Route to | Resolution record |
|---|---|---|---|
| Open concern | Suppress until resolved | Assigned concern owner | Resolution and close recorded |
| Safety note | Suppress | Duty owner under the approved process | Safety review and close recorded |
| Damage claim | Suppress | Named damage or operations owner | Claim review and outcome recorded |
| Permit/inspection pending | Suppress until sign-off | Job or operations owner | Sign-off or re-inspection recorded |
| Refund/credit dispute | Suppress; never trade for a review | Named office owner | Dispute outcome recorded separately |
Do not write an internal rule that says, “Resolve it first, then ask them to revise the review.” Do not make a credit, discount, future service, or a response contingent on removing, changing, or posting feedback. Google’s policy prohibits incentives around reviews, and the FTC’s review guidance addresses practices that suppress or condition consumer sentiment. The public-review route and the recovery route are distinct.
Need a documented local-review workflow without turning reviews into a sales target? theStacc’s Local SEO module supports Google Business Profile posts and review replies as part of a wider local workflow. Your service records, concern decisions, and escalation policy remain your team’s responsibility.
The pause condition is specific: suppress any promotional review ask whenever the record shows an open concern, a safety note, a damage claim, or a permit or inspection that has not been signed off, and keep it suppressed until the named owner records a resolution. A simple control is a status field: “open concern—no promotional request.” The status is not a hidden score, and it does not decide whether someone may speak publicly. It stops an office automation from landing while a customer expects a follow-up. When the matter closes, the original eligibility rule—not a judgment of the customer’s sentiment—controls any later communication.
The workflow should never produce any of these states:
- A gated request sent only to customers expected to be positive.
- An incentivized review tied to a discount, credit, drawing, or other consideration.
- Jobsite pressure or a request for specified praise while staff are present.
- Public exposure of customer, job, address, panel, photo, account, or safety detail.
- A promotional review ask during an open recovery, safety note, damage claim, or unsigned inspection.
- A safety, damage, or legal reply with no named owner.
Respond Without Exposing Customer or Job Details
A safe public reply acknowledges the feedback, stays honest, and moves detailed resolution to a private channel without revealing customer, job, technical, safety, account, or allegation information. The response should be a narrow public doorway to follow-up, not an argument or a case file.
Google permits verified businesses to reply to reviews and advises protecting private information, remaining honest, and handling detailed resolution privately. That guidance is especially useful when feedback refers to a service address, a scheduled arrival, a quoted scope, a return visit, or any alleged issue. A public answer can be calm without confirming the reviewer’s version of events.
| Public-review situation | Public reply purpose | Private next step |
|---|---|---|
| Praise | Thank the reviewer without adding job specifics | No detailed follow-up required unless the record calls for it |
| Vague complaint | Acknowledge concern and invite direct contact | Locate a record only after private identification |
| Arrival or access issue | Recognize that communication matters | Review scheduling and contact notes privately |
| Estimate or scope dispute | State that the team will review the concern | Assign the record to the appropriate owner |
| Return visit | Avoid explaining the work in public | Confirm the open-event state privately |
| Qualification claim | Do not debate credentials publicly | Route to the assigned company owner |
| Damage or urgent/safety wording | Do not adjudicate or give guidance publicly | Preserve records and escalate through the company process |
| Apparent spam | Use a restrained reply only if useful | Check records and flag only policy-violating content |
Drafts should avoid names, dates, addresses, work descriptions, account facts, and statements about what happened. They should also avoid technical or safety commentary. The safer pattern is acknowledgement plus a private channel: “We take your concern seriously and would like to review it with you directly. Please contact our office so the appropriate team member can help.” Adapt it only after a policy owner checks that it reveals nothing.
Public-reply safety checklist:
- No customer, job, address, panel, photo, account, or health/safety identifiers.
- No diagnosis of wiring, fault, cause, or code compliance.
- No admission of fault, liability, or responsibility.
- Route the matter to the named owner through a private channel.
- Document the handoff in the internal record.
For general negative-feedback reply structure, see how to respond to negative Google reviews. The electrical-specific safeguard is not to turn a response into an explanation of the job, a dispute about the customer, or advice on a potential hazard.
Escalate Technical, Safety, Damage, and Legal Claims
Technical, safety, damage, legal, and qualification claims need a private escalation route with preserved records and a qualified assigned owner. The public reviewer should receive a respectful route to contact the business, while the business avoids deciding facts, offering advice, or assigning fault in a review response.
This is an operational boundary, not electrical, insurance, licensing, warranty, or legal advice. A review may contain urgent wording, a claim about property damage, a complaint about a return visit, or an assertion about credentials. None of those categories should be resolved by a marketing calendar, automated reply, or a technician’s public message.
- Preserve the review and the service-event reference. Keep the original wording and point the internal owner to the relevant record location.
- Classify the claim for routing. Use a narrow category such as technical, safety, damage, legal, or qualification claim; do not make a public finding.
- Assign a qualified internal owner. The owner decides the company’s appropriate private follow-up process and whether specialized advice is needed.
- Keep the public response brief. Acknowledge the concern and provide a private contact path without describing the event or contesting allegations.
- Record the close and learning status. Mark the concern closed only under the company’s process; do not infer closure from a deleted or unchanged review.
Ownership is named, not improvised. A technical question routes to the electrical safety subject-matter expert; a safety or hazard wording routes to the duty owner under the approved process; a damage or legal claim routes to the named company owner. The public reply never diagnoses wiring, predicts a cause, or admits fault; it acknowledges the concern and points to a private channel.
| Claim type | Named owner | Public handling |
|---|---|---|
| Technical question | Electrical safety subject-matter expert | No public diagnosis; private follow-up only |
| Safety or hazard wording | Duty owner under the approved process | Acknowledge and route; do not advise in public |
| Damage claim | Named damage or operations owner | No admission of fault; preserve the record |
| Legal or qualification claim | Named company owner | Do not debate or decide in public |
Google provides a process for flagging reviews that violate its policies. It does not promise removal because a business considers feedback unfair or disagrees with it. Use the Google reporting process only when a policy issue appears applicable, retain your own records, and do not tell a customer that a report will produce a particular result.
Use Reviews and Testimonials in Marketing Carefully
Reviews and testimonials can be reused only after the business checks that the experience is genuine, the representation remains faithful, the required permission is documented, material connections are handled, the channel is approved, and the content has not passed its intended review date or expiry.
A public review is not a blank check to move a person’s words or a jobsite image into every channel. The electrical context can make that more sensitive: a photo may reveal a residence, access point, customer property, identifying information, or service context. Treat a review excerpt and a photo as separate permissions and separate checks.
| Checklist item | Question to answer before use |
|---|---|
| Genuine experience | Does the internal record support that this was a real customer experience? |
| Faithful representation | Is the excerpt accurate, unedited in meaning, and shown with needed context? |
| Permission | Is there documented permission for this excerpt, image, and intended use? |
| Material connection | Is a disclosure needed for any relationship or consideration? |
| Channel approval | Does the planned website, social, or profile use match the permission? |
| Expiry or recheck | Has a review date or permission condition triggered a new check? |
The FTC’s consumer reviews and testimonials guidance is a useful US reference point for fake reviews, insider relationships, suppression, and disclosures. Apply it as a boundary, not individualized legal advice; fact- and jurisdiction-specific questions need qualified review. For channel planning after approval, the separate social media for electricians guide can help keep content work distinct from consent decisions.
Turn Repeated Themes Into Process Fixes
Repeated review themes should become narrowly defined process questions, not assumptions about staff or customers. Code the operational context, look for enough comparable records to understand it, assign one owner, and document the action taken so learning changes the next field and office handoff.
Electrical contractors often have feedback that clusters around the operating experience: scheduling, stated arrival expectations, access coordination, estimate clarity, cleanup, field-to-office communication, return-visit status, and after-hours expectations. These are not interchangeable. A comment about access at a managed property should not be combined with a complaint about an estimate handoff and called a single “service issue.”
| Theme code | Context to check | Possible process action |
|---|---|---|
| Scheduling | Booked state, communication timing, and office owner | Review confirmation and update handoff |
| Arrival expectation | What expectation was recorded and how it was communicated | Clarify the office-to-field status update |
| Estimate clarity | Quoted-project state and customer-visible explanation | Review the estimate handoff language |
| Access | Property-contact coordination and relevant notes | Define who confirms access details |
| Cleanup | Completed-event close process | Add a closeout check to the field record |
| Return visit | Open versus closed follow-up state | Set an office notification checkpoint |
| After-hours expectations | Communication route and stated availability | Review the published and office message boundaries |
Do not call one review a trend. A useful review meeting asks whether the records are comparable, whether the same handoff failed, whether the theme code is too broad, and what would change in the next event. The output is a closed process action with an owner—not a judgment on a reviewer or a public claim about the job.
Measure Without Chasing a Rating Target
Measurement should show whether the workflow is operating as designed without collapsing reviews, ratings, replies, contacts, qualified requests, or booked work into one score. Each stage has a different source system, owner, and meaning, so a rating target is not an adequate measure of process quality.
Four formulas describe whether the workflow is operating as designed. Each keeps its own numerator, denominator, evidence window, source system, owner, and exclusions, and none of them is a rating target, a portable benchmark, or an industry average.
| Formula | Numerator | Denominator | Evidence window | Source system | Owner | Exclusions |
|---|---|---|---|---|---|---|
| Eligible-request coverage | Completed service events that received the documented neutral request | All completed service events eligible under the written rule in the same window | One declared 30-day review window | Job-management record plus request log | Office/reputation owner | Events under an active pause condition, duplicates, test/internal jobs, jobs outside service area |
| Public-reply completion | Genuine new reviews that received a policy-safe public reply within the business response rule | Genuine new reviews received in the same window | One declared 30-day window | Review-platform inbox plus reply log | Reputation owner | Spam/fake reviews flagged for removal, reviews under legal/safety hold, duplicate notifications |
| Recovery-loop closure | Complaints routed to a named owner with a recorded resolution | Complaints received in the same window | One declared 30-day window plus the stated resolution lag | Job-management/CRM plus complaint log | Operations owner | Spam, misrouted non-customer messages, duplicates counted once |
| Theme-to-fix rate | Recurring complaint themes that produced a documented process change | Distinct recurring themes identified in the window | One declared 90-day window | Review/complaint log plus operations change log | Operations owner | One-off/non-recurring issues, themes outside the business control |
These formulas do not join a review reply to a later contact, qualified request, or booked job. Keep rating, contacts, qualified requests, and booked work in their own systems if they are tracked at all, so the workflow is inspected on its own operation rather than on a commercial outcome it does not claim to cause.
If you want help connecting this routine to a broader local process, theStacc’s Local SEO module describes its Google Business Profile posting and review-reply workflow. It does not replace the contractor’s service record, customer-consent practice, complaint ownership, or qualified review for sensitive claims.
Want to map the communication part of this workflow to your existing local-marketing routine? Bring your current request and reply process to a strategy call; the conversation can separate platform workflow from the service-record and escalation controls your company must own.
Run a 30-Day Workflow Setup Review
A 30-day setup review can establish owners, test a small neutral-request pilot, rehearse the reply and escalation path, inspect early themes, and recheck current platform rules. It is a process-review window, not a promise about ratings, review volume, local visibility, customer contacts, or booked work.
- Days 1–5: write the policy and owner map. Define completed-service eligibility, exclusions, permission handling, open-concern status, reply owner, escalation owner, and evidence location.
- Days 6–12: test the record and request handoff. Use a limited set of completed records to check that field notes reach the office and that the neutral message cannot send from an open concern.
- Days 13–19: rehearse public reply and private escalation. Test praise, vague feedback, arrival communication, estimate or scope wording, return visit, and an apparent policy-report scenario without publishing private facts.
- Days 20–26: inspect themes and actions. Review comparable records for scheduling, access, estimate clarity, cleanup, return visit, and after-hours expectation codes before assigning a process action.
- Days 27–30: recheck sources and controls. Confirm current Google and FTC guidance, verify permission handling, and document what changed in the workflow.
Frequently Asked Questions
These answers set practical policy boundaries for electrical contractors: use a consistent genuine-event rule, keep requests neutral, protect private information, route disputed matters away from public replies, and avoid treating ratings or response activity as a promised search or business result.
Can an electrician ask every customer for a Google review?
An electrician can use one consistent request rule for genuine completed customer service events, subject to platform rules and the customer contact permission. The rule must not select only customers expected to be positive, and it must pause promotional messaging when the record shows an unresolved concern.
Can an electrical contractor offer a discount or credit for a review?
No. Google prohibits incentives for posting, changing, or removing reviews, and FTC guidance addresses sentiment-conditioned incentives and related review practices. Keep any review request neutral and separate from prices, credits, discounts, or any request to change what a customer has said.
What is review gating and why is it a problem?
Review gating is steering customers based on predicted sentiment, such as sending a public-review link only to people who say they are happy while routing others elsewhere. It is a problem because Google policies prohibit selective positive solicitation, and it distorts the feedback the business relies on. Use one documented eligibility rule for comparable completed events instead of a satisfaction filter.
Should an electrician ask for a review at the jobsite?
An electrician may provide a neutral way to leave a genuine review, but the request should not create pressure while staff are present or ask for specified praise. A safer process records the completed event, confirms communication permission, and lets the office send the same neutral request under its documented rule.
How should an electrician reply to a review that alleges unsafe or faulty work?
A public reply can acknowledge the concern, state that the team wants to review it, and invite the reviewer to a private channel. It must not disclose job, address, account, technical, safety, or allegation details, and it must not diagnose wiring, predict a cause, admit fault, or decide the claim in public.
When should a review request be paused for service recovery?
Pause the request when the record shows any open concern, safety note, damage claim, or a permit or inspection that has not been signed off. The pause suppresses promotional asks until the named owner records a resolution. It never blocks the customer from posting a review on their own.
Who owns replies about technical, safety, damage, or legal claims?
A technical question routes to the electrical safety subject-matter expert, a safety or hazard wording routes to the duty owner under the approved process, and a damage or legal claim routes to the named company owner. The public reply does not diagnose wiring or admit fault and is never improvised in public.
How do you measure reputation work without chasing a star-rating target?
Use four workflow formulas: eligible-request coverage, public-reply completion, recovery-loop closure, and theme-to-fix rate, each with a numerator, denominator, evidence window, source system, owner, and exclusions. Keep rating, contacts, qualified requests, and booked work in their own systems, and publish no portable benchmark or industry average.
Close the Loop With Accountable Ownership
A reliable electrician reputation workflow closes the loop when each service event has a documented state, each concern has an owner, each public reply protects private information, and each repeated theme produces a checkable operational action. The goal is accountable communication and learning, not a promised rating or commercial result.
Start with the smallest version that your office can inspect: one eligibility rule, one service-event record, one open-concern status, one reply owner, one escalation route, and one monthly theme review. Then make the field and office handoff visible. That is more useful than a generic push for five-star feedback because it reflects how scheduled work, quoted projects, return visits, and after-hours expectations actually move through an electrical business.
As the routine settles, keep the boundary clear. Review content is public communication; service recovery is private work; technical, safety, damage, legal, and qualification claims need appropriate internal ownership. For electrical businesses that also need an overview of local marketing support, see theStacc for electricians.
Ready to review the local-marketing parts of your process without turning customer feedback into a rating chase? We can discuss how neutral requests and privacy-safe replies fit beside your existing service operations.
Sources & references
- Google Business Profile Help — Google review policy
- Google Maps User Contributed Content Policy — fake engagement
- Google Business Profile Help — read and reply to reviews
- Google Business Profile Help — report inappropriate reviews
- FTC — Consumer Reviews and Testimonials Rule: Q&A
- FTC — soliciting and paying for online reviews
Rank in the Map Pack, collect reviews, and keep every location active — on autopilot.