Most apps answer reviews with the same three canned lines, which makes the brand read like an outsourced helpdesk. These 15 prompts generate human, specific replies that move 1-2 star reviewers to revise their score. A study of developer responses (Hassan et al.) found 4.4% of users raised their rating after a reply versus 0.7% with no reply — roughly a 6x lift — and apps that respond to at least half their reviews see a 0.3-0.7 star gain over 90 days. Coverage: angry reviews, bug reports, false-claim reviews, feature requests, glowing reviews, and the quiet 3-star band that holds the most upside.
TL;DR
- Apple lets you write up to 5,970 characters per response; Google Play caps replies at 350 characters. Same review, two very different drafts — the prompts below take a target platform.
- Reply within 48 hours. Apple responses appear within up to 24 hours; on Play, the user gets a push plus email notification only on your first reply (edits do not re-notify).
- Never ask for a rating bump in the reply. Make the fix, quote the user back, name a concrete action with a date, and they update on their own.
- Template 1 (angry 1-star) and Template 6 (3-star “almost there”) carry the most rating-lift leverage. Run Template 15 weekly to keep tone honest.
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. To respond on App Store Connect you need an Account Holder, Admin, or Customer Support role; on Google Play, a developer-account user with reply access.
When not to use these prompts
Do not draft replies for reviews you have not read in full. Do not use them to dispute a refund or take a legal position in public — escalate those off-platform to email or your support desk.
Platform constraints at a glance (as of June 2026)
| Constraint | App Store (Apple) | Google Play |
|---|---|---|
| Reply character limit | 5,970 | 350 |
| Time to appear publicly | Up to 24 hours | Near-immediate |
| User notified of reply | Not directly notified | Push + email on first reply only |
| Replies per review | One active response (editable) | Multiple; only first re-notifies |
| Who can reply | Account Holder / Admin / Customer Support | Developer-account users with access |
| Edit / delete later | Yes (edits are marked) | Yes |
The 350-character Play ceiling is the binding constraint: it forces you to lead with the acknowledgement and the one action, and cut everything else. Each prompt has a [platform] slot so the model sizes the draft correctly.
Prompt anatomy for review replies
Every strong review reply carries five moves, in this order:
- Acknowledge the specific frustration — quote one phrase back so the user knows you read it.
- Name what happened in one honest sentence; no apology theater.
- State one concrete action you took or will take, with a date if you have one.
- Offer a direct human contact (email or support link) for anything off-platform.
- Close warmly without asking for a rating change or sounding saccharine.
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 prompt templates
Any current model handles these well — we tested on GPT-5.5, Claude Sonnet 4.6, and Gemini 3.1 Pro (all as of June 2026). For tone work, Claude Sonnet 4.6 tends to sound the least corporate out of the box. Swap {platform} for App Store (up to 5,970 chars) or Google Play (hard 350-char cap) so the model sizes the draft. Replace every {...} placeholder with your real text before sending.
1. Angry 1-star recovery
The single highest-leverage template. Goal: get them to retry and revise the score.
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 (Template 10 handles this).
- 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).
- Size to the platform: keep Play replies under 350 characters; on App Store, stay under ~130 words anyway because users skim on mobile.
- Reply within 48 hours; rating revisions 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), ship the fix first, then reply — replies without a fix burn trust.
FAQ
- Does replying actually change the rating? Yes, especially for 2-3 star reviewers. In one analysis of developer responses (Hassan et al.), 4.4% of users raised their rating after a reply versus 0.7% with no reply, and apps that respond to at least half their reviews see a roughly 0.3-0.7 star lift over 90 days.
- Can I ask the user to update their rating? Don’t. Apple’s response guidance asks you to keep replies respectful and free of marketing or spam, and Play users react badly to it. Make the experience better and they revise on their own.
- How long is a developer response allowed to be? Apple allows up to 5,970 characters per response; Google Play caps replies at 350 characters (as of June 2026). Write the Play version first — if it fits 350, it fits anywhere.
- When will the user see my reply? On the App Store, responses can take up to 24 hours to appear and the reviewer is not directly notified. On Google Play, the user gets a push and email notification, but only on your first reply to that review — editing later does not re-notify.
- 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.
- Can I delete a review I disagree with? No. You can edit or delete your own response, but you can only get a user review removed 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