All tutorials

Users & QualityLesson 42 of 502:46

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.

Watch on YouTube

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

In this video

  1. Find the reviews that need you
  2. Star bars and the Needs reply badge
  3. Filter: Unanswered, 1★ and 2★, search
  4. By version and By month
  5. Write with AI, then edit the draft
  6. Saved replies
  7. Apple's rule: replies are public
  8. Recap and next: App Health

Open in Appalize

The screens this lesson walks through (sign-in required).

Transcript

The narration, with timestamps. Select a time to jump there.

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.

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.

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.

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.

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.

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.

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.

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.

Try it on your own app

Every tutorial shows a real Appalize screen. Sign up free and follow along with your own app.

Start free