Most apps respond to reviews with the same three template replies, which makes the brand sound like an outsourced helpdesk. These 15 prompts generate human, specific responses that often convert 1-2 star reviewers into rating updates. Coverage: angry reviews, bug reports, false-claim reviews, feature requests, glowing reviews, and the silent middle band (3 star) that holds the most rating-lift potential.
Who this is for
Mobile-app founders managing reviews themselves, support leads at app studios, growth teams tracking rating velocity, and customer ops teams that own App Store / Play Store replies.
When not to use these prompts
Do not use these to manufacture replies for reviews you have not read. Do not use them to dispute a refund or take a legal position — escalate those off-platform.
Prompt anatomy / structure formula
A review-response prompt should always carry six elements:
- Role: who the AI plays (senior PM / solo founder / product designer / indie dev / growth lead).
- Context: stage (idea / MVP / growth / scale), team size, traffic or ARR, platform (web / iOS / Android), audience, constraints.
- Goal: one concrete deliverable — one PRD section, one user-story set, one experiment design, one launch post.
- Constraints: timeline (this sprint / this quarter), scope cuts, must-not-break (existing flows, billing, compliance).
- Output format: table, checklist, ticket-ready JSON, or labeled blocks you can paste straight into Linear / Notion / Jira.
- Examples / signal: 1-2 reference docs or competitors you like, plus 1 anti-example you want to avoid.
Best for
- 1-2 star angry-review recovery
- Bug reports with not-enough-detail
- 3-star “almost there” rating lift
- Feature-request acknowledgements
- 5-star reply that does not waste the moment
15 copy-ready prompt templates
1. Angry 1-star recovery
The single highest-leverage template. Goal: get them to retry and update the rating.
You are a founder responding personally to a 1-star review of {app}. The user is angry. Write a reply that: (1) starts by acknowledging the specific frustration, no apology theater, (2) names what you understand happened in one sentence, (3) offers one concrete action you took or will take, (4) gives a direct contact ({email}), (5) does NOT ask them to update the rating. Less than 120 words. Voice: human, slightly humble.
Review: {paste}Variables to swap: app, email, review
Optimization: If the reply sounds corporate, add: “Rewrite so a friend would believe this came from a real person, not a support queue.”
2. Bug report with insufficient detail
The reviewer reports {app} is broken but gives no detail. Write a reply that asks for exactly 3 specific items ({device + OS, steps to reproduce, error text or screenshot}) without sounding like a form. Less than 90 words. End with one warmth signal.
Review: {paste}3. False-claim review (feature exists)
Reviewer claims {app} lacks {feature} but the feature exists. Write a reply that: never says "you are wrong", points to where the feature lives (1 line), and includes a tip that makes them feel smarter for finding it. Less than 90 words.
Review: {paste}4. Feature request acknowledgement
Reviewer asks for {feature}. Write a reply that: thanks them in 1 line (no gushing), tells them honestly whether it is planned / under consideration / not on the roadmap, and asks one curious question to learn more. Less than 80 words.
Review: {paste}5. Pricing complaint reply
Reviewer says {app} is too expensive or refused to pay. Write a reply that: validates the price concern, names what the price includes in 1 sentence, mentions any trial / free tier honestly, and does NOT discount. Less than 100 words.
Review: {paste}6. 3-star “almost there” lift attempt
Reviewer gave 3 stars and listed 1-2 things they wished worked better. Write a reply that addresses each point concretely, mentions what is in the next release, and treats them as the most valuable reviewer you have (because 3-star is the lift opportunity). Less than 110 words.
Review: {paste}7. 5-star reply that earns referrals
Reviewer left 5 stars and a short positive note. Write a reply that: thanks them by referencing one specific thing they said (NOT "we appreciate it"), shares one small upcoming feature they will love, and softly invites them to share with a friend. Less than 80 words.
Review: {paste}8. Privacy / data-fear reply
Reviewer raised a privacy concern about {app}. Write a reply that: states exactly what data is and is not collected (no marketing fluff), links to the privacy policy, and offers a way to opt-out or delete their data. Less than 130 words. Voice: precise, non-defensive.
Review: {paste}9. Crash / data-loss reply
Reviewer reports the app crashed and lost data. Write a reply that: acknowledges the severity, asks 3 diagnostic questions, offers a manual recovery path if any exists, and gives a direct human contact. Less than 130 words. Voice: urgent, accountable.
Review: {paste}10. Localization-needed reply (non-English review)
Below is a 1-2 star review in {language}. Write a reply in the same language that: addresses the specific complaint, names a concrete action, and offers a contact. Then provide the English back-translation so the team can audit. Less than 100 words in the target language.
Review: {paste}11. Competitor-comparison review
Reviewer compares {app} unfavorably to a competitor. Write a reply that: never names the competitor, acknowledges what they value about that experience, points to one specific thing {app} does that the competitor does not. Less than 100 words.
Review: {paste}12. Trolling / abusive review
Reviewer left an abusive or trolling review of {app}. Write a brief, neutral, public-facing reply that: does not engage with the abuse, states the facts, leaves a contact for legitimate concerns. Less than 60 words. Note: also recommend whether to report the review under {Apple, Google} guidelines.
Review: {paste}13. Reply pack for a major outage
We had a {duration}-hour outage that triggered a wave of 1-star reviews. Write 4 variants of a public reply addressing the outage: (a) acknowledge + facts, (b) what we fixed, (c) what we are changing process-wise, (d) credit / compensation if any. Each less than 110 words.14. Update-broke-things reply
Reviewer is upset that an update changed or removed a feature they used. Write a reply that: validates the disruption, explains why honestly in 1 sentence, offers a workaround, and asks if they would join a small group to test the next revision. Less than 110 words.
Review: {paste}15. Tone audit pass on a batch
Below are 10 draft review replies our team wrote this week. Audit them on 5 dimensions: (1) reads human, (2) addresses the specific review, (3) has a concrete action or fact, (4) honest about limitations, (5) ends warmly without being saccharine. Score each 1-5 and rewrite any below 3.
{paste 10 replies}Common mistakes
- Pasting the same template reply on every 1-star review — readers see right through it.
- Apologizing five times and never naming a concrete action.
- Asking the user to update their rating in the reply — most stores discourage it and it reads needy.
- Arguing with the reviewer in public — even when they are wrong, the audience is other potential users.
- Replying days late — reviewers check whether you replied within 48 hours.
- Generic warmth signoffs (“we appreciate you”) with no specifics from the review.
- Skipping replies on 5-star reviews — they are your best chance to deepen advocacy.
How to push results further
- Always reply in the same language as the review.
- Quote one phrase from the review back to them — proof you read it.
- Name a concrete action with a date if possible (next release, this week, by Tuesday).
- Keep replies under 130 words; users do not read long ones on mobile.
- Reply within 48 hours; rating updates correlate strongly with fast response.
- Maintain a public-tone style doc and run template 15 weekly.
- For repeat themes (5+ reviews on the same bug), fix the bug first, then reply — replies without a fix burn trust.
FAQ
- Does replying actually change the rating?: Yes for 2-3 star reviewers especially. Industry data suggests 5-15% update their rating after a thoughtful reply within 48 hours.
- Can I ask the user to update their rating?: No. Apple’s guidelines discourage it and Play Store users react badly. Make the experience better and they update on their own.
- Should I respond to every 5-star review?: Pick the ones with specific content, not just emojis. A specific 5-star reply often turns into a referral.
- How fast should I reply?: Within 48 hours. Beyond a week, the rating-lift effect drops sharply.
- Can I delete a review I disagree with?: Only via the store’s formal report mechanism, and only when it violates guidelines (abuse, spam, off-topic). Otherwise, reply.
Related
- App store listing prompts
- App onboarding copy prompts
- Release notes prompts
- Churn analysis prompts
- App Store Review — the Rejection Reasons You Can Avoid in Advance
- AI App Review Appeal Draft: Resubmit Without Sounding Like You’re Begging
- How to Reply to App Store Reviews With AI Without Sounding Like a Bot
- Product, App & Startup Prompts hub