← Back to Blog
Review operations3 min read

How to Reply to App Store Reviews: Access, Steps and Examples

Reply from App Store Connect when you own the app, or connect an eligible ReviewBot Flow to reply from Slack or Zendesk.

Published December 6, 2021Updated September 12, 2026By ReviewBot Editorial Team

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 $10/month per enabled Flow, billed annually, in addition to base monitoring. Use the reply action on an eligible delivered review; monitoring alone cannot publish a response.

If a response is unavailable

Check app ownership, store role, the review’s platform and the separate reply connection. A successful Slack setup message proves destination access, not store publishing permission. If a submission is pending, check its status before trying again.

Response examples to adapt to the actual problem

These are illustrative drafts, not customer conversations. Replace the next step with your own working support route and only describe a fix after verifying it has shipped.

SituationExample response
A problem still being investigatedSorry sign-in is failing. Please contact our support team through the app’s support page so we can investigate your app version and error details privately.
A verified released fixWe fixed the sign-in issue in the latest release. Please update and try again. If it persists, our support team can help investigate.
A feature request without a commitmentThanks for explaining why offline access matters to you. We have shared the use case with our product team; we do not have a release date to announce.