The Shelf / App Store / App Review Response Engine
App Review Response Engine
Turn App Store & Play reviews into policy-safe replies and a quote-backed roadmap.
The job: turn a stream of App Store and Google Play reviews into a worked reputation operation — a triaged reply queue, drafted replies your team approves, a roadmap built from real quotes, and an alarm when the one-stars spike. It runs end-to-end inside your own agent, on a cadence, after launch.
Most review handling fails one of two ways. Ignore the reviews and a bad release quietly bleeds your rating while the reviewers who'd have upgraded move on. Or paste the same "we're sorry for your experience, please contact support" into all of them — which users read as copy-paste, which deepens a one-star author's annoyance, and which both stores may flag as spam. The naive middle — an unattended auto-poster — is worse: it can leak a reviewer's personal info, argue with a user, over-promise a fix, or inject a price into a reply, the last being an outright App Store content violation.
What's on the tag:
- A multi-store pull that persists and diffs every run, because Google's API only exposes the last seven days — miss a window and those reviews are gone for good.
- Theme × sentiment clustering, each review tagged with its version and its verbatim quote, so a live complaint is never mistaken for one you already fixed.
- A triage formula that floats the paying, about-to-churn one-stars — the ratings actually worth saving — to the top of the queue.
- Two reply drafts per review, App Store and Google, matched to the review's own language, each passed through a filter that strips PII, promo, solicited-rating asks, and invented workarounds.
- A quote-backed roadmap: a week of reviews as an engineering-ready backlog table, not a prose summary.
- A one-star-spike alert that names the cluster driving it, plus a rating-prompt spec that catches users at a real win moment — no sentiment gating, which is its own rejection risk.
Who it's issued to: indie operators and small studios running their own post-launch reviews, who want a recurring triage pass instead of a scramble after every bad release — no per-seat SaaS required.
Why not a free review-reply prompt? A free prompt writes a reply. It doesn't know that soliciting a rating change is expellable on both stores, that a promo line is an App Store content violation, or that Google's window closes in seven days. This one was run end-to-end on a real batch, describes both stores' reply policies accurately in our own words, and is versioned — when a store moves a limit, the skill gets updated and your locker gets the new copy. Every reply is a draft; a human approves before anything posts.
FIELD REPORT real output, not a promise
From a documented run on 14 App Store reviews for PennyWise (a fictional budgeting app, v3.2), fed through the skill in draft-only mode — no ASC API key, so pulls/clustering/triage/drafts/roadmap all run and replies are staged for human copy-paste. Cold start: no reviews.json history, so no trailing baseline exists yet. Excerpted and trimmed to the strongest honest portions of the captured output.
Step 2 — Cluster (theme × sentiment)
| Theme | Sentiment | Count | Versions | Representative quote(s) (verbatim) |
|---|---|---|---|---|
| crash | negative | 3 | v3.2 (3) | "crashes every time I open the budgets tab. Unusable now."; "App crashes on the budgets tab since 3.2."; "Se cierra sola al abrir presupuestos. No sirve." |
| billing/paywall (bug) | negative | 1 | v3.2 | "Charged for Pro but the premium reports are still locked. Want a refund." |
| bug | negative | 2 | v3.2 (1), v3.1 (1) | "Face ID login stopped working after the update..."; "Sync is slow and sometimes double-counts transactions." |
| performance | negative | 1 | v3.2 | "the widget hasn't updated in days." |
| UX-confusion | negative | 1 | v3.0 | "Too many notifications, can't find how to turn them off." |
| missing-feature | neutral/positive | 3 | v3.2 (2), v3.1 (1) | "export to CSV would make it perfect"; "shared household budget feature"; "wish it synced with my credit union" |
| praise | positive | 3 | v3.2 (3) | "Love the weekly digest, keeps me honest."; "The new dark mode is beautiful."; "Best budgeting app I've tried, worth the Pro price." |
14/14 reviews accounted for.
Step 3 — Priority reply queue (1–3★ + churn-risk; 9 of 14)
| # | Review (excerpt) | Stars | Version | Signal | Action |
|---|---|---|---|---|---|
| 1 | "crashes every time I open the budgets tab... Unusable now" | 1★ | v3.2 | crash, current, churn ("unusable") | Reply now + engineering flag — P0 |
| 3 | "Se cierra sola al abrir presupuestos. No sirve." | 1★ | v3.2 | crash, current (dup, Spanish) | Reply now (Spanish) + engineering flag — P0 |
| 4 | "Charged for Pro but premium reports still locked. Want a refund." | 1★ | v3.2 | payment failure, refund, paying user | ESCALATED — draft + human sign-off — P0 |
| 5 | "Face ID login stopped working after the update..." | 2★ | v3.2 | auth regression, current, daily friction | Reply now — P1 |
| 6 | "Sync is slow and sometimes double-counts transactions." | 2★ | v3.1 | data-integrity bug + perf, fix unconfirmed | Reply now — P1 |
(v3.0/v3.1 reviews are NOT assumed fixed by 3.2 — no changelog/confirmation was supplied, so they stay in the open queue rather than getting a "fixed in vX" reply.)
Step 4 — Drafts (App Store, human-approval required before posting)
#1 (1★, v3.2, en):
"Thanks for reporting this — a crash on the Budgets tab after the 3.2 update is a real blocker, and we're sorry it's made the app unusable for you right now. We've reproduced the issue and a fix is actively in progress for an upcoming update. We won't stop until Budgets opens reliably again — appreciate you flagging it."
#3 (1★, v3.2, es):
"Gracias por avisarnos — sabemos que la app se cierra sola al abrir Presupuestos desde la actualización 3.2, y lamentamos que ahora mismo no te esté funcionando. Ya reproducimos el problema y estamos trabajando en una solución para una próxima actualización. Gracias por tu paciencia mientras lo resolvemos."
#4 (1★, v3.2, en) — ESCALATED — human sign-off required before posting:
"Sorry about this — being charged for Pro without the premium reports unlocking isn't okay, and we understand wanting a refund. We're looking into why the unlock didn't apply to your account. App Store purchases are refunded by Apple directly, so you can request one anytime at reportaproblem.apple.com. We're also digging into the unlock issue on our end."
#6 (2★, v3.1, en):
"Thanks for the detailed report — slow sync is annoying on its own, but transactions double-counting is the more serious part since it throws off your real budget numbers. We've flagged both, with the double-counting as the priority, and we're investigating now. Appreciate you calling this out specifically."
MUST-NOT filter check (all 14 drafts): no reviewer PII, no pricing/promo language, no solicited rating changes, no invented workarounds (the Face ID and sync drafts deliberately omit troubleshooting steps since none were buyer-confirmed), no over-promised dates, no hollow non-answers, no two near-identical drafts.
Step 6 — 1★-spike alert (cold start)
No trailing baseline yet — the relative 2× trigger can't be computed until the next run, and the report says so rather than inventing a trend. Raw this-run numbers: 4 of 14 reviews are 1★ (28.6%), 3 of those 4 (75%) are the same Budgets-tab crash cluster on v3.2. The absolute floor (default N=5) did not trip (4 < 5), but it's close and single-cause-dominated — recommendation is to expedite the P0 crash fix regardless of the formal alert state.
That is the shape of every run: a verbatim-quoted cluster table with full-count reconciliation, a churn-weighted triage queue that escalates billing to a human, drafts that stay honest about what's confirmed, an explicit MUST-NOT pass, and cold-start honesty about the metrics it cannot yet compute.
SERVICE RECORD living gear — updated as the factory learns
v1.0.0 — 2026-07-17
First issue. Post-launch App Store / Google Play review-response engine: multi-store pull, theme × sentiment clustering, 1–3★ triage, policy-safe two-variant reply drafting, quote-backed roadmap, 1★-spike alert, and rating-prompt timing spec. Policy guardrails (no auto-post, no solicited ratings, no promo in App Store replies) and the Google 7-day-window state-file requirement are baked in.
Every update ships free to owners — your locker always serves the latest version.
QUESTIONS
Does it post replies for me?›
No — it drafts and queues, and a human approves every reply before it goes live. With an App Store Connect API key (Admin or Customer Support role) or a Google Play service account, the skill documents the safe post path. With neither, it runs draft-only: it still pulls, clusters, triages, drafts, and roadmaps, and you paste approved replies by hand.
How is this different from the pre-submit checklist?›
Different job, different moment. A pre-submit checklist runs before you ship, to clear Apple review. This runs after launch, on a cadence, to manage reputation and mine reviews for signal. It's post-launch reputation ops, not a compliance gate and not pre-build demand work.
Do I need a paid tool like AppFollow?›
No. It runs on free, rate-limited store endpoints inside your own agent — no per-seat cost — and bakes the policy guardrails (no auto-post, no solicited ratings, no promo in App Store replies) into the drafting step instead of bolting them on.
Will it handle non-English reviews?›
Yes. It detects the language each review was written in and drafts the reply in that language — a German 1★ gets a German reply. If it can't draft confidently in that language, it flags LANG-FALLBACK and says why, rather than guessing or defaulting a reply the author can't read.