How to reply to iOS App Store Reviews (with Screenshots)

Triage before you draft

Start with recent low-star reviews, outage or billing language, and reports that appeared after a release. Keep a separate queue for feature requests so urgent support issues do not disappear in volume.

• Prioritize one- and two-star reviews.
• Group duplicates around the same release or incident.
• Assign an owner before the response is written.

Use a four-part reply

A reliable structure is: acknowledge the specific issue, explain what you know, give the next step, and invite private follow-up when account details are involved. Templates should provide structure, not replace the customer’s words.

• Thank the reviewer without sounding automated.
• Never request private account information in a public reply.
• Link to support or the next release only when it is genuinely available.

Close the loop after the fix

When the underlying issue is fixed, update the internal ticket and decide whether a public follow-up is useful. Track themes by platform, locale, release, and rating so product teams can see whether the response changed the trend.

A tested ReviewBot handoff

A practical setup is to send low-star or issue-keyword reviews to a focused team destination, keep the original review link and version context in the alert, and use the dashboard’s reply path only when the connected account supports it.

• Send one test alert before enabling the Flow for the whole team.
• Keep private account details out of the public reply.
• Record the release or support ticket that owns the follow-up.