The short version

Respond to a negative App Store review by acknowledging the specific problem, stating what you know and offering one useful next step. Keep the reply brief, avoid personal information and return with an update when you have verified a fix.

Take these with you

  • Acknowledge the specific problem and give one realistic next step.
  • Separate a confirmed fix from an issue you are still investigating.
  • Keep support independent of whether someone changes their rating.

What should you do before replying to a negative review?

Read it once for the feeling and again for the facts. Note the task the person attempted, the failure they describe and any version or device information available. Check whether you can reproduce the problem and whether support messages mention the same symptom.

Draft outside the reply box if you feel defensive. Remove sentences about how hard you worked or how few people have complained.

Then choose the right response: explain an existing feature, acknowledge a verified bug, ask for one missing detail through support, or calmly state a product limitation. Distinguish an investigation from a confirmed cause.

What does a useful App Store review response include?

Use three small parts: acknowledgement, current position and next step. Name the issue, say what is true today and give the person something practical to do.

Acknowledge the inconvenience directly. Say you are investigating only if you will investigate. Mention a release version only when you have verified that it contains the relevant fix. If you need private details, move the conversation to your support channel.

Apple's developer conduct guidelines call for respectful responses focused on the feedback, without personal information, spam or marketing. Read your draft as a future customer would: can they tell what happened and what help is available?

Which reply templates can you adapt?

These are original, illustrative templates, not actual customer exchanges. Replace bracketed details, check every statement and adapt the language to the review. Never promise a fix or support route your app does not offer.

For a bug you are investigating

I'm sorry [specific action] isn't working. I'm investigating this, but haven't confirmed the cause yet. Please use the support link on the App Store page to send your app version and what happened immediately before the problem, so I can check the same steps.

For a feature someone could not find

Thanks for explaining where you got stuck. You can [complete task] by opening [verified location] and choosing [control]. I can see that this was difficult to find, and I'll review how the app explains it. If those steps don't match your screen, please contact support.

For a pricing or feature-limit complaint

I'm sorry the purchase options weren't clear. [Specific feature] is included in [accurate plan or purchase], while [accurate free functionality] is available without that purchase. I'll review the wording you encountered. Thank you for describing the point where it became confusing.

After you have verified a fix

An update on the [specific problem] you reported: I've verified a fix in version [version], which is now available. Please update and try [relevant action] again. If it still happens, the support link on the App Store page reaches me. Thank you for bringing it to my attention.

For billing or refund requests concerning purchases billed by Apple, point the person to Apple's refund instructions. Explain how to reach the appropriate help without promising that a refund will be approved.

A good review reply gives someone a next step. It does not ask them to take back their experience.

A thought worth passing onDownload quote card ↓

How do you reply in App Store Connect?

Open Apps, choose your app and select Ratings and Reviews. Choose the relevant platform, find the review and select Reply. Enter your response and submit it.

Apple lists Account Holder, Admin and Customer Support as the roles that can reply. Responses may take up to 24 hours to appear, and only one response per review is displayed. You can edit the response when you have new information. See Apple's reply instructions.

Save a short internal note linking the review to the issue you are investigating. That makes it easier to return with a useful update after shipping, instead of leaving a public promise that quietly goes stale.

What should you avoid saying?

Avoid arguing over whether the person is entitled to feel disappointed. Replace defensive language with a factual explanation and a next step. Do not publish their email address, account details or information from a private support conversation.

  • Replace “It works for everyone else” with the specific condition you have tested.
  • Replace “Fixed soon” with the investigation status you can support.
  • Replace “Please change your rating first” with unconditional help.
  • Replace a long feature advertisement with instructions relevant to this problem.

Do not offer rewards for better ratings or route only happy customers towards reviews. Apple's discovery rules prohibit manipulating reviews. Your response should stand on its own as helpful support, even if the star rating never changes.

When should you report a review instead of replying?

A low rating or blunt criticism is not, by itself, a reason to report a review. If it contains spam, offensive content or another policy concern, use Apple's reporting process and explain the specific concern. Apple describes that option in its ratings and reviews guide.

Keep your public response focused on the app. If there is a legitimate product issue beneath an angry comment, investigate it without adopting the comment's tone. If you cannot add anything useful publicly, pause rather than extending an argument.

How can you make follow-through manageable?

Keep a simple list: review, reported issue, next action and date to check again. Prioritise people blocked from a core task, then work through recurring friction. Share the verified outcome in the response when it is ready.

Perch brings reviews from different countries into one inbox. With a connected key and suitable permissions, you can read and reply alongside your other app numbers. Follow the setup guide to connect it.

Judge your reply by its accuracy and usefulness. Your part is to make the help clear and follow through on what you said.

Common questions

Will replying to a negative review improve its star rating?

There is no guarantee. A useful response explains the situation to the reviewer and future readers even if the rating stays unchanged.

How long does an App Store review reply take to appear?

Apple says responses may take up to 24 hours to appear on the App Store. App Store Connect shows a pending state before publication.

Should I copy the same reply to every bad review?

Use a template as a starting structure, then address the specific issue. A reply about a crash should not read like a reply about price, and every statement about a fix should be verified.

Sources & further reading

Sources checked 13 October 2026. Apple’s reporting and interface can change.

  1. Apple: App Review Guidelines, developer code of conduct
  2. Apple: Respond to reviews
  3. Apple: Request a refund for apps or content
  4. Apple: View ratings and reviews