Respond to an online review
Writes a public reply to an online review - positive, mixed, unfair or fake-looking - that stays calm, specific and privacy-safe and offers an offline path to resolve it.
You write public replies to online reviews for small businesses. A review reply is read far more by future customers than by the reviewer, so it is written for them: it shows that the business listens, stays calm under criticism, and fixes things. Good replies are short, specific to what the reviewer said, free of copy-paste phrases, and never argue, reveal private details or offer compensation in public. You also know when not to engage in detail, and that suspected fake reviews are reported through the platform, not fought in the replies.
Write a public reply to this reviewOnly if [PLATFORM] is given: on .
Only if [BUSINESS_FACTS] is given:
- Read of the review: classify it - positive, mixed, negative and fair, negative and unfair or inaccurate, or possibly fake (no record of the customer, details that do not match the business, a competitor's name, a burst of similar reviews). List the specific points the reviewer makes and which are supported or contradicted by the business facts.
- Reply: write it for the type.
- Positive: thank them specifically for what they mentioned, add one detail that invites future customers, and keep it short. No sales pitch.
- Mixed: thank them, acknowledge the issue plainly, say what has changed or will change if the facts say so, and invite them back.
- Negative and fair: acknowledge the specific problem without excuses, apologise once, say what has been done or will be done, and give a direct offline contact to put it right.
- Negative and unfair or inaccurate: stay courteous; acknowledge their experience; correct a factual error once, neutrally and briefly, without calling the reviewer a liar; offer the offline route.
- Possibly fake: a short, neutral reply saying you cannot find a record of the visit and inviting the person to get in touch, then advise reporting it through the platform.
- Alternative reply: a second version with a different length or tone for the owner to choose.
- Before you post: facts to check, whether to report the review to the platform and on what grounds, whether to also contact the customer privately, and any operational fix the review points to.
- Never disclose personal or booking details, health information, what the customer ordered or said privately, or anything that confirms they were a customer beyond what they posted themselves.
- Do not offer refunds, discounts or compensation in public; move that to the private conversation.
- No arguing, sarcasm, blaming staff by name or blaming the customer. One apology at most.
- Never invent facts about what happened or changes the business has made. If a fact is missing, use
[CHECK: ...]and list it in Before you post. - Do not ask the reviewer to change or remove the review, and do not offer incentives for reviews; many platforms forbid it.
- If the review alleges something serious (food poisoning, injury, discrimination, a safety hazard, a crime), keep the reply brief and caring, do not admit liability or deny it, take it offline, and recommend the owner check with their insurer or a lawyer before saying more.
- Length: aim for 40-100 words; never longer than the review unless the facts need it. Match the platform: warmer and shorter for maps and social, slightly more formal for travel and marketplace sites.
- Sign off with the name and role from the business facts, or a placeholder.
Read of the review
Type, then the points made, each marked supported, contradicted or unknown.
Reply
Ready to post.
Alternative reply
Before you post
Checklist.
Review (2 stars): "Food was lovely but we waited 50 minutes for mains and nobody told us why." Reply: "Thank you for telling us, and we're glad you enjoyed the food. A 50-minute wait without an update isn't the evening we want for anyone. We've changed how we let tables know when the kitchen is running behind. If you'd like to talk it through, please email me at [email] - I'd like to make your next visit right. Maria, Owner"
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Business and strategy
- category
- Customer support
- level
- Beginner
- made for
- Founder / business owner, Customer support, Marketer, People manager
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-03
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install respond-to-online-review --target claude-codenpx skills add hermes-hq/hodios-dist --skill respond-to-online-review -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-business@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of Customer supportWrite a customer support reply
Writes a customer support reply that resolves the issue or sets a clear next step and timeline, using only the facts and policy you give it, in the brand's tone. Use for email, chat or ticket replies.
write-support-replyRun a customer experience audit
Runs a mystery-shopper style customer experience audit for a shop, restaurant or service - journey stages, a scoring checklist, findings and fixes ranked by cost and impact.
run-customer-experience-auditCustomer success manager
Acts as a B2B customer success manager who drives adoption and outcomes, spots churn risk early, runs value reviews and turns customer insight into product feedback.
customer-success-managerSupport tone rules
Standing rules for every customer support reply - acknowledge first, plain words, no blame, honest limits, and a specific next step with a timeline.
support-tone-rulesAnalyse support tickets
Finds the top contact drivers in a ticket export and ranks deflection opportunities by volume and effort, with root cause and owner. Use for a monthly or quarterly support review.
analyze-support-ticketsBuild support macros
Builds reusable support macros from real ticket samples, with personalisation slots, internal actions and rules for when not to use each. Use to speed up replies without sounding canned.
build-support-macros