review-manager
Manage online reviews — generation strategies, response playbooks, reputation monitoring, and turning reviews into growth.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- review-manager
- category
- business-marketing
- description
- Manage online reviews — generation strategies, response playbooks, reputation monitoring, and turning reviews into growth.
03 SKILL.md 正文
Overview
Reviews are modern word-of-mouth: they drive local SEO, purchase decisions, and trust. This skill covers the full review practice — generating authentic reviews at scale, responding to positive and negative reviews, monitoring reputation across platforms, and using review insights to improve the business.
Reviews are the new word-of-mouth at scale: 90%+ of buyers read them, and star ratings directly move conversion. Review management is both defensive (responding to negatives, catching fake reviews) and offensive (generating authentic positives systematically). It is a compounding asset — every review works for you indefinitely.
When to use
-
Increasing review volume and ratings
-
Responding to negative reviews
-
Building a review generation system
-
Monitoring brand reputation
-
Improving local search via reviews
-
Turning reviews into marketing assets
-
Recovering from a negative review crisis
-
Building review generation into the customer journey
-
Monitoring brand sentiment across platforms
-
Managing reviews across 100+ locations
-
Responding to viral negative incidents
-
Building review programs for B2B services
Core concepts
The review funnel. Ask → make it easy → follow up → respond → showcase. Most happy customers never review unless asked; most unhappy ones review unprompted. Systematic asking corrects the negativity bias.
Asking well. Timing (right after positive moments: delivery, successful support, 5-star NPS), channel (email, SMS, in-app, in-person with QR codes), and simplicity (direct links to the right platform, no multi-step processes). Never incentivize with payments for positive reviews — it's against most platforms' policies and often illegal; you can incentivize honest reviews in some contexts, but check platform rules first.
Response playbook. Positive: thank personally, mention specifics, invite back. Negative: respond quickly (24–48h), empathize publicly, take resolution offline, follow up publicly when resolved. Never argue, never be defensive, never fake.
Platform strategy. Prioritize where your customers look: Google (local SEO + trust), industry-specific (e.g., G2/Capterra for software, TripAdvisor for hospitality), then secondary. Claim and complete every profile — unclaimed profiles collect unanswered complaints.
Reputation monitoring. Alerts for new reviews and mentions, sentiment tracking over time, competitor review benchmarking. Speed matters — a negative review unanswered for weeks signals indifference.
Reviews as assets. Showcase top reviews on site/social/ads (with permission where needed), mine reviews for messaging (customer language is copy gold), and feed recurring complaints to product/ops as improvement priorities.
The review request moment. Ask when satisfaction peaks: after delivery confirmation, after a resolved support ticket, after a milestone achieved in-product. Never ask after a complaint or a failed interaction. In-product prompts at the moment of delight convert 5–10x better than post-purchase emails.
Responding to negatives (the HEARD method): Hear them out (acknowledge specifically) → Empathize (genuine, not scripted) → Apologize where warranted → Resolve (offer a path forward) → Diagnose (fix the root cause). A thoughtful response to a 1-star review influences every future reader more than the review itself.
Platform strategy. Google (dominant for local), Yelp (influential, filtered aggressively), Facebook (social proof), industry-specific (TripAdvisor, Healthgrades, G2). Prioritize by where your customers actually decide — not all platforms matter equally per vertical. Claim and complete profiles everywhere relevant; optimize effort toward the top 2–3. Review velocity. Steady streams beat bursts: 5–10 new reviews monthly per location sustains rankings and trust. Systematize asks (post-transaction triggers) rather than campaigning sporadically. Monitor velocity per location; stalled locations need intervention. Sentiment analysis. Categorize feedback themes (service, product, price, staff) → track trends → route insights to operations. Reviews are free market research — aggregate them into operational improvements. Share positive themes with teams; recognition reinforces what works.
Practical workflow
- Audit. Current ratings per platform, review velocity, response rate and time, sentiment themes, competitor comparison. Find the gaps.
- Claim and optimize profiles. Every relevant platform: complete info, photos, accurate hours/services, correct categories. Unclaimed profiles are reputation liabilities.
- Build generation systems. Post-transaction email/SMS sequences (ask happy customers at the right moment), in-store QR codes, staff training (ask in person — highest conversion), and review links in receipts/follow-ups. Target steady velocity, not bursts.
- Respond systematically. Daily monitoring, response SLA (24–48h), templates as starting points (personalize every response), escalation path for serious complaints, and a process for flagging fake/defamatory reviews.
- Showcase and leverage. Review widgets on site, top reviews in ads and social, case studies from detailed reviews, and "you asked, we fixed" posts when reviews drive improvements.
- Analyze and improve. Monthly: rating trends, sentiment themes, response metrics, competitor movement. Quarterly: feed top complaint themes to operations with data.
Negative review response template: acknowledge specifically → empathize genuinely → take it offline (name + direct contact) → resolve → follow up publicly. "We're sorry to hear about [specific issue]. This isn't the experience we want. I'm [name], [title] — please reach me at [contact] so I can make this right."
Review generation system: map the customer journey → identify 2–3 peak-satisfaction moments → build asks into those moments (in-product, email, SMS) → make leaving a review frictionless (direct links, no account creation) → thank reviewers personally → showcase reviews in marketing. Measure: review velocity, average rating trend, response rate, and response time.
Crisis protocol: negative review velocity spike → assess validity (real issue or attack?) → respond publicly with HEARD → fix root cause → follow up privately → if fake/coordinated, report with evidence. Never offer incentives for removing negative reviews — it violates most platforms' policies.
Multi-location program: centralized platform (monitoring, response templates, analytics) → location-level ownership (managers respond within 24h) → escalation paths (serious complaints to senior staff) → monthly scorecards per location. Balance central efficiency with local authenticity — templated responses to everything feel robotic. Viral incident response: assess scope and validity → respond publicly (acknowledge, empathize, commit to action) → take detailed discussion private → implement fixes → follow up publicly with resolution. Speed matters, but accuracy matters more — verify facts before responding publicly.
Common pitfalls
- Never asking. Relying on organic reviews guarantees negativity bias. Ask systematically.
- Fake or incentivized positives. Platform penalties, legal risk, and destroyed trust when exposed. Earn reviews honestly.
- Arguing with reviewers. Public defensiveness amplifies damage. Empathize and move offline.
- Ignoring reviews. Unanswered reviews — especially negative — signal you don't care. Respond to all negative, many positive.
- Review gating. Only soliciting from happy customers (against most platforms' policies). Ask everyone; fix what you learn.
- Burst campaigns. 50 reviews in a week then silence looks manipulated. Steady velocity wins.
- Not acting on feedback. Reviews revealing the same complaint for months with no fix. Close the loop operationally.
- Incentivizing only positive reviews. Asking only happy customers skews ratings and violates FTC/platform rules. Ask everyone; earn the positives.
- Ignoring reviews. Unanswered negatives signal indifference. Respond to 100% of negatives and a sample of positives.
- Fighting fake reviews emotionally. Public accusations backfire. Report through proper channels with documentation; respond professionally regardless.
- Fake review panic. Obsessing over competitors' suspicious reviews. Report with evidence, then focus on earning genuine reviews — authenticity wins long-term.
- Ignoring positive reviews. Only responding to negatives. Thanking positive reviewers builds loyalty and encourages more reviews.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).