Why Can't I Reply to Reviews in Google Play Console? (Permissions, Decoded)

If the reply button is missing or greyed out in Google Play Console, the cause is almost always a permission: the Reply to reviews access hasn't been granted to your account. The next two most common reasons are a rating with no written text (there's literally nothing to reply to) and an app-access mismatch — you're signed into a Google account that doesn't have that permission on this specific app.

The account Owner holds every permission by default, so if you're the Owner and still can't reply, skip past the permission section and check the no-text and app-availability causes below. If you're a teammate — a support agent, a contractor, a marketer added to the console — it's the permission nearly every time. Here's the full list, in the order worth checking, so you can fix it in a couple of minutes instead of filing a support ticket.

Replying is a permissioned action in Play Console, and it's a separate checkbox from just being able to see reviews. A teammate can have full read access to the Ratings and reviews section, open any review, and still find no way to answer it — because viewing feedback and responding to it are two different permissions. The one you need is called Reply to reviews.

Permissions live under Users and permissions (reachable from the left navigation on the account home, outside any single app). Whoever manages access opens that page, selects the user, and grants Reply to reviews — either as an account-level permission that applies to every app, or scoped to specific apps on the app-permissions tab. Only the account Owner or someone with the permission to manage users can hand it out. Google reshuffles the exact menu labels and groupings in Play Console every so often, so if the wording near you differs slightly, look for the reviews-related permission rather than the exact string.

One trap worth naming: an invite that's still pending looks active in the list but can't actually post. If a teammate swears the permission was granted and the reply option still isn't there, confirm they accepted the invite and then had them sign out and back in — the console caches permissions per session.

You can only reply to reviews that contain written words. A star-only rating — someone tapped three stars and left, no comment — never exposes a reply field, because a developer response has to attach to review text. If you're staring at a silent one-star and hunting for the button, that's why it isn't there. Nothing is broken; there's just no comment to answer.

This trips people up most right after a rating prompt drives a wave of installs to rate the app. You'll see the average move and the rating count climb, but only the subset who typed something are answerable. The number of reviews you *can* reply to is almost always smaller than the total rating count, and that gap is entirely star-only ratings.

Two variations of the same mistake. First, the wrong Google account: if you're signed into a personal Gmail that was never added to the developer account (or you're in the wrong developer account entirely, common for anyone who consults across several), you'll see the app publicly but have no console controls for it. Check the account picker in the top-right corner and confirm you're in the developer account that actually owns the listing.

Second, app-scoped access that doesn't include this title. On teams that grant permissions per app rather than account-wide, it's normal to be able to reply on the flagship app and hit a wall on a newer one that nobody remembered to add you to. The permission exists on your account — it just wasn't extended to that app. The person who manages users can fix it in the same Users and permissions screen by adding the app to your access. The App Store and Google Play differ in a handful of these visibility and permission mechanics, and we lay the full comparison out in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).

Sometimes the field shows up fine and the problem is at submit time. The most common reason a reply refuses to save is length: Google Play enforces a hard 350-character limit on developer responses, and text over that cap won't post. It's a firm ceiling, not a suggestion, so a long, heartfelt paragraph gets rejected while a tight two-sentence answer goes through instantly. If your reply won't save, count the characters first.

The other two: each review holds a single developer response, so if one already exists you're editing rather than adding — posting again replaces the old text, it doesn't stack a second reply. And reviews from closed or open testing tracks are handled separately from your production reviews, so if you're looking for a specific tester's comment in the main reviews list and can't find a way to answer it, check whether it came from a testing track.

That reply is 219 characters, in the reviewer's own language, and safely under the cap — the shape every Play Console response should take. It's worth the effort for more than politeness: when Google announced recency-weighted ratings at I/O 2019, it also reported that developers who respond to reviews see an average lift of 0.7 stars. A calm, specific answer to a two-star complaint is quiet reassurance for the next hundred people reading before they install. If your users span markets, replying in their language matters more than most teams realize, and we cover the how in [reply to app reviews in any language](/blog/reply-to-app-reviews-in-any-language).

A reply you can't post is almost never a Play Console bug; it's access or a missing comment, and the six checks above tell you which in about two minutes. The harder problem is the ongoing one: staying on top of every review across both stores before the window to reply quietly closes and a fixable one-star hardens into your average. That's the part worth handing off. [Start free with ReplyArgus](/signup) — no card — and Argus drafts your first reply in minutes, in the reviewer's own language, already sized for Google Play's 350-character limit.