How to Reply to App Store Reviews: Rules and Templates

You reply to App Store reviews in App Store Connect (Ratings and Reviews, then Reply) and to Google Play reviews in Play Console (Ratings and reviews, then Reply). The replies that raise ratings are fast, specific, short, and end with a concrete next step, such as a fix, a workaround or a support address. Below are the rules, the mechanics on both stores and templates you can adapt.

Why replying is worth the time

A reply is public. Future visitors read it alongside the review, so you are writing for two audiences: the reviewer and the person deciding whether to install. A calm, specific answer to a harsh review signals an active developer.

The second benefit is the rating itself. Both stores let reviewers edit their review after a reply, and a reviewer whose problem was solved often does. You cannot promise that, but you can make it likely by fixing the issue and telling them.

I will not claim a specific uplift in installs or rankings: it is hard to isolate, and nobody should promise one. Treat replies as support plus conversion hygiene. For the wider picture of how reviews fit into ratings and visibility, see App Store Reviews: Get More Ratings and Respond the Right Way.

Where to reply on each store

Apple App Store

1. Open App Store Connect and choose your app.
2. Go to Ratings and Reviews (under the App Store section).
3. Filter by rating, country or version if needed.
4. Open a review and select Reply, write your text, and publish.

Only the Account Holder, Admin, App Manager and Customer Support roles can respond, so check the team's permissions first. Each review shows one developer response at a time; editing it replaces the previous text. Apple may notify the reviewer when you reply, and they can then update their rating.

Google Play

1. Open Play Console and select your app.
2. Go to Quality, then Ratings and reviews (the menu label can shift between console updates).
3. Open Reviews, pick a review and write your reply.

Google Play also lets you filter by rating, language, app version and device, which is useful when a complaint is tied to one release or phone model. Replies can be edited later too.

A word on the wrong kind of reply: App Review rejections (the Stack Overflow questions in the results) are a different system. Those messages go through the Resolution Center in App Store Connect, not the public review page.

The rules for replies that raise ratings

1. Reply fast, starting with the lowest ratings

Sort by 1 to 3 stars and recent. A reply within a day or two reads as attentive. A reply months later still helps the visitor reading it, but the reviewer has moved on.

2. Prove you read it

Quote or restate the exact problem: "the sync fails after the 3.2 update", not "sorry for the inconvenience". Generic replies look like automation and invite more anger.

3. Keep it to three or four sentences

Structure: thanks or acknowledgement, specific answer, next step. Nothing more.

4. Apologise once, and only for a real problem

If the app crashed, say so and apologise. If the user wants a feature you will not build, explain honestly instead of apologising for your roadmap.

5. Move detailed support off the public page

Give a support email or in-app route. Never ask for passwords or personal data in a public reply, and do not paste a user's account details.

6. Do not ask for a higher rating

Asking for stars in a reply feels like pleading and may break store policies on incentivised ratings. Say that you fixed the issue and that you would welcome their updated feedback if it helps.

7. Never argue or blame

Even when the reviewer is wrong (for example, blaming your app for a carrier outage), explain neutrally. You are writing for the next hundred readers.

8. Vary the wording

The same paragraph pasted on twenty reviews is visible on your page. Keep a template as a skeleton and change the specifics.

9. Close the loop after the fix

When the bug ships fixed, edit your earlier reply: "Fixed in version 3.2.1, thanks for flagging it." This is the single move most likely to prompt a rating change.

Templates by review type

Replace the bracketed parts. Do not paste them unchanged.

What not to write

• "We are sorry to hear that." with nothing after it.
• "Please update your review." as the main message.
• Long corporate paragraphs, legal language or emojis in a serious complaint.
• Anything that blames the reviewer.

Which reviews to prioritise

You will not always have time for every review. Use this order:

1. Recent 1 to 2 star reviews that describe a specific, fixable problem.
2. Reviews mentioning a recent version, because they show active regressions.
3. Questions, since a helpful answer serves everyone reading.
4. Reviews from your largest markets.
5. Positive reviews with detail, which are quick wins for tone.

If you cover several countries, reply in the reviewer's language when you can write it well. A short, correct reply in their language beats a long, awkward one. Machine translation is fine as a first draft if a speaker can check it.

Turning replies into a repeatable process

1. Check reviews at least once a working day, or set alerts.
2. Tag each review: bug, feature, billing, praise, confusion.
3. Feed recurring tags to the product backlog. Three reviews about the same thing are a roadmap item.
4. Reply using a template skeleton and personalise.
5. After each release, search for reviews about the fixed issue and update your replies.

Searvia's review intelligence can group reviews by theme and draft AI replies you edit before posting; see how reviews work in Searvia. If you are still building the habit, ratings and review prompts are the other half: more happy users rating you dilutes the occasional bad review.

Common mistakes

• Replying only to negatives, so praise looks ignored.
• Using the same canned text everywhere.
• Promising fixes with dates you cannot keep.
• Asking users to change their score.
• Never revisiting the reply after shipping the fix.

Good replies are small, specific and honest. Do that consistently, and your review page starts to read as proof that someone is looking after the product.