In this guide
Before you reply
Apple requires an Account Holder, Admin or Customer Support role for responses. Monitoring a public listing does not grant reply access. Confirm that you selected the correct app and platform.
Publish through App Store Connect
Open Apps and select your app. Go to Ratings and Reviews, choose the relevant platform, find the review and select Reply. Write the response and submit it. Apple says responses may remain pending for up to 24 hours. Check the published result rather than submitting duplicates.
Edit an existing response
Return to the same review and use Edit Response, then save the correction. Apple shows one public response per review. Keep a record of the associated support issue so a later responder knows why the text changed.
Write a specific, useful answer
Name the reported problem, describe a confirmed next step and provide a private support route when account details are involved. Do not promise a release date or fix you have not verified.
- Example, access problem: “Sorry you cannot sign in. Please contact support through the link in the app so we can investigate your account privately.”
- Example, verified fix: “The export issue is fixed in version 4.2. Please update and contact support if it continues.” Use this only when that fix is actually released.
- Example, feature request: “Thanks for explaining how you use exports. We have shared the request with the product team.” Do not imply a committed roadmap item.
Reply through ReviewBot
Create a notification Flow for your App Store listing and Slack or Zendesk destination. Open the reply setup, complete the store authorization and eligibility check, and review the add-on charge before enabling it. Replies cost $120/year or $10/month per enabled Flow, in addition to base monitoring. Use the reply action on an eligible delivered review; monitoring alone cannot publish a response.