Skip to content
LocalASO

Guide

How to Respond to App Store Reviews: Rules, Triage and Templates

Reply publicly in App Store Connect to reviews where you can add information: a bug you fixed, a feature that exists, a question you can answer. Apple notifies the reviewer, who can then update their review. Keep each reply short, factual and written for the next person who reads the page, because only one response per review appears there.

Updated

How replies work on the App Store

  • You can publicly respond to a review, edit your response and delete it.
  • Only one response per review appears on your product page.
  • Responses can take up to 24 hours to appear. Until then they show as pending in App Store Connect.
  • Edited responses carry a note that they were edited.
  • The roles that can respond are Account Holder, Admin and Customer Support.
  • Apple says the reviewer is notified when you respond and can update their review. Only the latest review and response from each user display on the product page.

Apple also says ratings and reviews influence how an app ranks in search, and that the summary rating shown in search and on the product page is specific to each territory. Reviews are therefore read by people deciding whether to download, in their own country.

Triage: whom to answer first

BucketExample scenarioReply?
Bug you fixedA crash that the latest version resolvedYes, first. Say which version fixed it
Missing feature that existsThe user asks for something already in SettingsYes. Point to where it is
Missing feature that does not existA request you may or may not buildYes, briefly and honestly
Abuse or off-topicA review about a different appRarely; a short factual note at most

Start with the first bucket. A reply that tells the reviewer the problem is fixed gives them a reason to revisit and update their review, which Apple allows.

Steps

  1. Check reviews on a schedule. A weekly pass is enough for most small apps.
  2. Sort by storefront and language. Reviews are per territory, so reply in the reviewer's language when you can.
  3. Write for the next reader. Many readers will see your reply beside the review. Do not argue.
  4. Say what changed. Name the version and the fix, without promises you cannot keep.
  5. Offer a support route. Give an address or in-app path rather than a long thread in public.
  6. Edit when you ship. If you replied "coming soon" and it shipped, edit the reply.
  7. Track what repeats. Three reviews about the same issue are a roadmap item, not three replies.

Reply templates

Replace the details with your own facts.

  • Fixed bug (scenario: crash on opening reminders): "Thanks for telling us. This crash is fixed in version 2.4. If it still happens after updating, write to support@example.com with your device model." (147 characters)
  • Feature exists: "You can turn that on under Settings > Reminders. If you cannot find it, tell us what you tried and we will help."
  • Feature not planned: "We do not have that yet. We have noted it and will post in the release notes if it ships."
  • Language: reply in the reviewer's language. A machine-written reply you cannot read is a risk.

Do not put personal data in a public reply.

Worked example

A hypothetical habit tracker, Streakly, receives five reviews in a week from the same cause: reminders arrive an hour late after a time-zone change. Streakly ships a fix in 2.4, then replies to all five with the same fix note, adjusted to each reviewer's language, and names the fix in its release notes; see writing What's New. The next review that mentions the issue gets a link to the version that solved it.

Next step

Reply habits work with the prompts you show; read how to ask for ratings. For the listing text itself, LocalASO can upload drafts to App Store Connect for you to review; see the App Store Connect docs.

Sources

Do this for every country, in minutes

LocalASO checks your rank, volume and difficulty for every keyword in 50+ App Store countries, in each local language. It runs on your Mac. $29 once, no subscription.