# Reply to App Store Reviews Without Sounding Like a Bot

> Keep up with App Store reviews without sounding like a bot. In under three minutes, you'll filter the unanswered one- and two-star reviews, see which app version the complaints come from, and get a Write with AI reply draft that you edit before it goes public.

- Lesson page: https://www.appalize.com/tutorials/reply-to-app-store-reviews-without-sounding-like-a-bot
- YouTube: https://www.youtube.com/watch?v=BzYxbfr259M
- Duration: 2:46
- Section: Users & Quality (lesson 42 of 50)
- Appalize panel pages (sign-in required): https://app.appalize.com/aso-tools/review-manager
- Updated: 2026-11-16

## What you'll learn

- Why the star bars tell you more than the average
- How to sort by priority instead of date: Unanswered, then 1★ and 2★
- How to find one theme with a single search word
- How By version shows which release caused the complaints
- Three edits that make an AI draft sound like a person
- How to use saved replies without copy-pasting the same answer
- Apple's rule: your reply is public, and Apple notifies the reviewer

## Chapters

- [0:00](https://www.youtube.com/watch?v=BzYxbfr259M&t=0s) Find the reviews that need you
- [0:17](https://www.youtube.com/watch?v=BzYxbfr259M&t=17s) Star bars and the Needs reply badge
- [0:39](https://www.youtube.com/watch?v=BzYxbfr259M&t=39s) Filter: Unanswered, 1★ and 2★, search
- [1:03](https://www.youtube.com/watch?v=BzYxbfr259M&t=63s) By version and By month
- [1:25](https://www.youtube.com/watch?v=BzYxbfr259M&t=85s) Write with AI, then edit the draft
- [1:54](https://www.youtube.com/watch?v=BzYxbfr259M&t=114s) Saved replies
- [2:10](https://www.youtube.com/watch?v=BzYxbfr259M&t=130s) Apple's rule: replies are public
- [2:33](https://www.youtube.com/watch?v=BzYxbfr259M&t=153s) Recap and next: App Health

## Transcript

Narration of the video with timestamps (minutes:seconds). On-screen steps can add detail; masked values (campaign names, money) are placeholders.

### 0:00 Find the reviews that need you

[0:00] Find the one-star reviews you haven't answered.
[0:02] See which version caused them.
[0:04] Then get a Write with AI draft you edit before it goes public.
[0:09] Reading reviews one by one in App Store Connect?
[0:12] Start here.
[0:13] First, let's see how many reviews are actually waiting for you.

### 0:17 Star bars and the Needs reply badge

[0:17] This is Review Manager in Appalize.
[0:19] Look at two things.
[0:20] First, the star bars.
[0:22] An average hides the shape.
[0:24] The bars show whether low ratings are a few reviews, or a real share of the total.
[0:29] Second, the Needs reply badge.
[0:32] Every review that carries it is a person still waiting for an answer.
[0:36] Now narrow that list to the reviews that hurt most.

### 0:39 Filter: Unanswered, 1★ and 2★, search

[0:39] Don't reply in date order.
[0:41] Click Unanswered.
[0:42] Then click the 1★ and 2★ buttons.
[0:45] The list gets shorter.
[0:47] These are the reviews that cost you the most trust, and they still have no answer.
[0:51] Want to find a theme?
[0:52] Type one word in the search box.
[0:55] Crash, for example.
[0:56] Appi tip: reply to every low-star review.
[1:00] Reply to happy ones when they mention something specific.

### 1:03 By version and By month

[1:03] Before you reply, find out where these complaints come from.
[1:06] Look at By version.
[1:08] If low stars jump after one update, that release is your suspect.
[1:12] No versions?
[1:13] It shows By month.
[1:15] Look for a trend, not one bad day.
[1:18] Before you write, don't say fixed in the next update unless the fix is shipping.
[1:23] Now you know the cause, so let's write the reply.

### 1:25 Write with AI, then edit the draft

[1:25] Click Reply on the first review.
[1:28] Then Write with AI.
[1:29] The draft already mentions this person's problem.
[1:32] Now, three edits.
[1:34] Name the problem in your own words.
[1:36] Don't defend yourself.
[1:38] Give one real next step, like a setting to check or a support email.
[1:42] Common mistake: the same copy-paste reply under every review.
[1:46] Side by side, it reads like a bot.
[1:49] It's still only a draft.
[1:51] Some replies come up again and again, so save them.

### 1:54 Saved replies

[1:54] Open Saved replies.
[1:55] Keep one for each common case.
[1:57] A known bug.
[1:58] A feature request.
[2:00] A feature people can't find.
[2:02] A saved reply is a starting point, not the reply.
[2:05] Change the details every time.
[2:07] One more thing before you press Send reply.

### 2:10 Apple's rule: replies are public

[2:10] Here's the rule.
[2:11] Your reply is public on your product page, and Apple notifies the reviewer.
[2:16] They can then update their review.
[2:18] You can edit it later.
[2:19] But write it as if everyone will read it.
[2:22] So I won't send this one here.
[2:24] Cancel.
[2:24] Without Appalize: App Store Connect, Ratings and Reviews, Reply.
[2:29] Reviews tell you what broke.
[2:31] Next, see it in the numbers.

### 2:33 Recap and next: App Health

[2:34] If you only remember one thing: filter first, find the cause, then edit the AI draft.
[2:39] Next is App Health, for the crash and quality side.
[2:42] All tutorials are at appalize.com slash tutorials.

## Topics

app store reviews, reply to app store reviews, respond to app store reviews, app store review management, app store connect reviews, ai review replies, negative app reviews, app store ratings, app store optimization, aso, indie ios developer, review manager

## More lessons

- Previous: [App Store Connect Analytics: Find Your Real Downloads](https://www.appalize.com/tutorials/app-store-connect-analytics-find-your-real-downloads.md)
- Next: [Where to Find TestFlight Crashes (Without Xcode)](https://www.appalize.com/tutorials/where-to-find-testflight-crashes-without-xcode.md)
- All lessons: https://www.appalize.com/tutorials.md

---
Source: Appalize (https://www.appalize.com). Content license CC-BY-4.0; cite the lesson page.
