Skip to the content
KwernBeta
  • Pricing
Sign inGet startedDashboard
  1. Kwern
  2. Blog
  3. How to Reply to App Store Reviews (With Templates)

7 min read · 21 October 2026

How to Reply to App Store Reviews (With Templates)

Quick answer

Rules and copy-ready templates for answering 1 to 5 star App Store reviews, plus the promises a developer response should never make.

A review lands on your app page and you have no idea whether to answer it. You can, from App Store Connect, and the answer sits publicly under the review for every future visitor to read. That makes each reply a small piece of listing copy written for two audiences: the person who left the review, and the stranger deciding whether to download.

This guide gives you the rules we would follow, a template for each kind of review, and the list of things a developer response should never promise.

What a reply can and cannot do

A developer response is one public reply per review. You can edit it later, and the reviewer can change their own rating and text after reading it. That last part is the real prize: a bug report that gets a fast, specific answer is the review most likely to be revised.

Some limits shape everything else:

  • You can only answer written reviews. A bare star rating has no reply box.
  • The reply is public. Anything you write is read by every future visitor, so never put an email address, an order number or an account detail of the reviewer in it.
  • You cannot refund anyone from a reply. Apple handles refunds, and the reviewer has to ask Apple for one.
  • On Google Play, a reply is capped at 350 characters. Write the short version first, and the App Store version is easy.

Replying will not fix a rating by itself. If you want to know what moves installs, the listing matters more, from its keyword field to the screenshots, and our ASO agent page lists what we check there. Replies are the cheapest part of the listing to keep alive, which is why they are worth doing on a schedule.

Seven rules that cover most reviews

1. Answer the problem in the first sentence. Someone who writes "crashes when I open settings" wants to hear that you know about settings. Thank them second, if at all.

2. Write for the next reader. The next reader is a prospective user who sees three reviews and your replies under them. They are judging whether anyone is home. Short, specific and calm beats long and apologetic.

3. Keep a human voice, and sign it. A reply that reads like a template gets ignored by the person you wrote it for. Use their detail (the screen, the feature, the word they used) in the first line.

4. Move the conversation to support early. Give one way to reach you and say what to include. A support email on the app's page is enough. Do not ask for personal data in the public thread.

5. Never argue. If a review is wrong, correct one fact once, politely, and stop. The reviewer will not be persuaded, and the visitor reads the tone.

6. Do not ask for a different rating. Asking a reviewer to raise or remove a review in exchange for anything is against Apple's review rules, and it reads as pleading anyway. Fix the problem, say so, and let them decide.

7. Answer within days, not months. We have no study on how reply speed changes ratings, so we make no claim there. The practical case is simpler: a reply to a review from last week still reaches a reviewer who remembers the problem, and a reply to a review from last year reaches nobody.

Templates by rating

Replace the bracketed parts with the real detail. If you cannot fill a bracket with something true, shorten the reply.

1 star, a bug you know about

Thanks for the detail, [name or nothing]. The crash when opening [screen] is a bug we have reproduced and are working on. If you email [support address] with your iOS version and device, we will tell you when the fix is in a build. Sorry for the lost [time or work].

Say "reproduced" only when you have. Say "working on" only when someone is.

1 star, a bug you cannot reproduce

Sorry this happened. We could not reproduce the [problem] on our side, so we are missing something. Could you email [support address] with your device, iOS version and what you tapped before it happened? We will reply to you directly.

The honest version asks for what you need. It does not claim a fix.

1 star, wrong expectations

This is the review about a feature the app never had, or a price shown on the page.

We can see why this is frustrating. [App] does [what it does] and does not do [what they wanted], and we should have made that clearer on the page. If [alternative that works for them] is what you need, [App] is not the right tool, and we would rather say so.

You lose nothing by saying who the app is not for. It protects the next visitor from the same mistake, and it is the sort of line that convinces the right visitor.

1 or 2 stars, about the subscription or price

Thanks for being direct about the price. [App] is [price] a [period], and the [paid feature] is what it covers. Refunds go through Apple at reportaproblem.apple.com, and we cannot issue them from here. If something in the paid tier did not work, email [support address] and we will look at it.

Do not offer a discount in public unless you offer it to everyone. Do not promise a refund, since the decision is Apple's.

3 stars, a feature request

Thanks, this is useful. [Feature] is a request we have heard before. We have not scheduled it, so we will not promise a date. If you tell us what you were trying to do when you looked for it, that helps us decide.

"We have not scheduled it" is a complete and honest answer. Do not turn it into "coming soon". When the feature does ship, the promotional text is a place to thank the people who asked for it.

4 stars, with one complaint

Thanks for the four stars. We will look at [the complaint]. If you can tell us what you expected to happen on [screen], email [support address].

5 stars, a short one

Thank you. [Name the thing they liked, if they named it.]

Do not reply to every five-star review with the same sentence. Pick the ones with substance, and let the others stand.

A rude or abusive review

Reply once, factually, or do not reply. If the review breaks Apple's content rules, report it through App Store Connect instead of answering it.

What a developer response should never promise

  • A release date for a fix or a feature. Builds slip, and review times are Apple's.
  • A refund or a free month. The first is Apple's call, the second sets a precedent you did not choose.
  • That a bug is fixed. Say it is fixed in a version only once that version is live.
  • A rating change. You cannot ask for one and you cannot promise anything in return for one.
  • Anything about a person's data that you have not checked. Privacy answers belong in a private thread and in your privacy policy.

A routine that fits in ten minutes a week

You do not need a tool for this, and a small app has few enough reviews that a spreadsheet works. Launch week is the one time to write replies before the reviews arrive, which our app launch checklist does on day 4. After that:

  1. Open App Store Connect once a week and filter the reviews to those without a response.
  2. Sort the one and two star reviews first, then the three star ones with a feature request.
  3. Reply to each using the matching template above, filled with the reviewer's own words.
  4. Tag any review that names a bug and put it in your issue tracker with the review text.
  5. Check the oldest reply once a month: did the reviewer update the rating?

If you run a Google Play listing too, keep the same replies and cut them to 350 characters.

Where an agent fits, and where it should not

Review replies are a good job for a drafting agent, because the templates above are rules and the detail comes from the review text. The part that needs a person is the promise. If a draft says a fix is coming, you are the only one who knows whether it is.

That is how our ASO agent works. It reads the unanswered reviews through the App Store Connect connector (and Google Play through its own connector), drafts a reply for each, and leaves every one as a proposal in your feed. A reply goes out as the developer response only after you approve it, and you can edit the wording first. Nothing is posted on its own.

It will not know that your fix shipped on Tuesday, and it will not know that you refuse refunds in public. You still read each draft. If that suits how you work, the plans start at $29 a month and are on the pricing page. If you would rather do it by hand, the templates above will get you through the first fifty reviews.

Share this article

XLinkedInFacebook
AJ

Alexandre Joly

This article was drafted by Kwern's own Writer agent and published here through Kwern's MCP server, the way any Kwern user publishes theirs.

Related articles

App Store Promotional Text: What to Put in 170 Characters
App Store promotional text changes without a review. What its 170 characters should say after a launch, a release or a press mention, with counted examples.

13 November 2026

App Store Keywords: Filling the 100-Character Field
How to fill the App Store keyword field without repeating your title or subtitle, with a worked example that turns a wasted 94 characters into 15 new words.

6 November 2026

App Launch Checklist: The Last 7 Days Before You Ship
A seven-day app launch checklist for solo makers: listing, store console baseline, waitlist, replies and launch day, in the order that stops a quiet launch.

15 October 2026

Read on

ASO Agent
Audits the App Store and Google Play listings every week and drafts the metadata changes and the review replies worth making.
App Store Connect
What Kwern reads from App Store Connect, the two listing fields it can change, and the ASO agent that reads it.
Google Play
What Kwern reads from Google Play, the one thing it writes, and why you invite an email instead of pasting a key.
Three plans, your own model key
The three plans, what a read costs and what stays on your own key.

Someone is asking for what you built today.

On Reddit, on X, in ChatGPT's answers. Kwern finds them every morning and drafts the reply in your voice; you decide what goes out.

Product

  • Agents
  • Skills
  • Pricing
  • Connectors
  • Compare
  • Blog
  • MCP server
  • Docs

Agents

  • ASO Agent
  • Apple Ads Agent
  • SEO Agent
  • GEO Agent
  • Google Ads Agent
  • X Post Agent
  • X Reply Agent
  • X Community Agent
  • Influencers Agent
  • LinkedIn Agent
  • Reddit Agent
  • Hacker News Agent
  • Competitors Agent
  • Writer Agent

Connectors

  • App Store Connect
  • Apple Ads
  • Google Play
  • RevenueCat
  • Stripe
  • PostHog
  • Google Search Console
  • Google Analytics 4
  • Google Ads
  • X
  • Reddit
  • LinkedIn
  • GitHub

Compare

  • Best AI CMO tools
  • Okara alternative
  • Okara alternatives
  • Okara review
  • Kwern vs Okara
  • Hoox alternative
  • Hoox alternatives
  • Hoox review
  • Kwern vs Hoox
  • RiseMore alternative
  • RiseMore alternatives
  • RiseMore review
  • Kwern vs RiseMore
  • Privacy policy
  • Terms of use and sale
  • Legal notice
  • Cookies

© 2026 Kwern