Hire an AI public review response manager

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A reply for each review, ready to paste
• A short list of reviews to decide first, with what to check
• Replies to unhappy reviewers checked against their words and your rules
• Repeat complaints counted, with dates, and a ranked brief for app reviews
• A log that keeps openings from repeating week to week

How it does the job well

• Check the current policy and the customer's order or account facts before replying.
• Answer the actual question in the first two lines, then explain.
• Match the customer's tone. Acknowledge the problem once, without grovelling.
• Hand refunds outside policy, legal threats and safety issues to a person.

Mistakes it avoids

• Posting, even when the platform is connected.
• Arguing with a reviewer or blaming the carrier, the app or the customer.
• Admitting fault for harm or a defect in a public reply.
• Running this for fewer than about five reviews a week. Reply by hand.
• Using it for support emails. Those need a different desk.
• Promising refunds, dates or fixes the policy does not allow.

What a good result looks like

An example, not your task: You get a handful of reviews a week and want a reply to every one, in a human voice.

• The batch. One line with how many reviews are ready, fixed and held.
• Decide first. Held reviews with the risk flag and what a person must check.
• Replies to approve. Each review with stars, type, whether it was checked, and a reply ready to paste.
• Placeholders to fill. Open slots such as your support email or a remedy.
• Repeat complaints. Complaint types with counts and dates, plus a ranked brief for app reviews.
• Notes. Reviews where stars and text disagree, or that name the wrong product page.

How the work is checked

• Every reply names one detail from its own review.
• No two replies in the batch, or in the last log, open with the same three words.
• No reply promises a remedy that is not in rules.md.
• No reply asks a reviewer to change a rating, or offers anything for it.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Read the folder. Loads your reply rules, reply log and open issues. On the first run it sets the rules and asks for your approved remedies.
• Draft a reply to each review. Writes one specific reply per review, using a detail from it, and avoids the openings used in earlier batches.
• Hold the risky ones. Reviews about health, safety, legal threats, fraud claims or bank disputes get a holding reply only and go to the top for you.
• Check unhappy replies and loop. Tests each reply to a one-to-three-star review against what they said and your approved remedies, fixes it and checks again, up to two rounds.
• Look for repeat complaints. Counts complaint types against the open issues. Three in 30 days becomes a flagged issue. For app reviews, it adds a ranked brief.
• Log and hand back. Saves the batch to the log, then stops for your yes before anything is posted.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id public-review-reply-desk only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/public-review-reply-desk/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The new reviews, pasted or exported, with stars, date, product and text
• Your support email and the remedies you have approved, the first time
• A few replies you wrote and liked (optional)

Helpful context (optional)

• Your returns and refund policy
• A list of known product issues

Tools and access

• Claude Code: It can keep the reviews folder, read the log and run on a schedule.
• Your review app or Google Business: Export or copy new reviews from here. Post the approved replies yourself.

Functions and deliverables

• Public review response manager: Draft specific replies to public reviews. Hold sensitive cases, check complaint replies and flag repeated issues.
  • A reply for each review, ready to paste
  • A short list of reviews to decide first, with what to check
  • Replies to unhappy reviewers checked against their words and your rules
  • Repeat complaints counted, with dates, and a ranked brief for app reviews
  • A log that keeps openings from repeating week to week
• Review request and reply planner: Tell it about your reviews. Get when to ask, how to word the request, and how to answer a bad review.
  • A better timing for the request
  • Wording for a review request email
  • A reply to a bad review
  • Advice on handling ratings and complaints
  Source: Checkout Page.
• Public review reply drafter: Paste reviews. Get a reply draft for each, with risky cases flagged and unapproved remedies left out.
  • One reply per review
  • Flags on risky reviews
  • A table when there are four or more
  • Placeholders where approval is needed
  Source: Pro Skill Packs.
• Angry customer reply checker: Paste the complaint and your draft reply. Get promises, facts and tone checked, plus a repaired draft.
  • Each customer point marked answered or missed
  • Each promise checked against your rules
  • Tone flags with the exact words quoted
  • A repaired draft with a clear next step
  Source: Pro Skill Packs.
• Shopify app review priority sorter: Paste public Shopify app reviews and app ownership lists. Get a draft brief of risks, repeat problems and first actions.
  • A P0 to P3 ranking of every review
  • The type of each review: incident, design problem, pricing wording or feature request
  • Groups of problems that repeat across reviews and apps
  • A first action for each review
  • The original wording kept next to each row, so you can trace it
  • A list of reviews left for a person to read
  Source: sickn33.
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one

Tasks you can use it for

• You get a handful of reviews a week and want a reply to every one, in a human voice.
• Some reviews are angry and you do not trust yourself to reply calmly or safely.
• You want to spot a repeat complaint before it becomes a pattern.

Limits to check before starting

• You get fewer than about five reviews a week: write the replies by hand, in your own words.
• You want to answer support emails: use a support inbox or a person, because this agent only handles public reviews.
• You want to learn what buyers want from your reviews: read them yourself or use a review mining step, since this agent only counts complaints.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Start a chat with the agent. In Claude Code, add it as a skill or save it in .claude/agents, then ask it to handle this week's reviews.
• The first time, give it your support email and the refunds, replacements or credits you are willing to offer, and when.
• Paste the new reviews.
• Read the held reviews first. Then approve the replies and post them yourself.
• Run it again next week. It reads the log and the repeat complaints.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/public-review-reply-desk for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.