Google Play reviews in Slack
A Google Play one-star is a bug report with the evidence attached: the build it was written on, the device, the Android version, the language. Put it in the channel that shipped the build, the hour it lands.
Set up in under five minutes • No demo required
The reviews arrive before the release does
Google Play holds a new review back from the public for around a day. You can read it and answer it the minute it is written, and nobody else can see it yet. A staged rollout at ten percent produces its first one-stars inside the hour, while nine users in ten are still on the old build.
Every card carries the version the review was written against, so three one-stars on v.4.12.0 in forty minutes read as what they are: a build, not a mood. Reviewflowz posts each new Google Play review to the channel you choose, most inside the hour, with the stars, a colour bar (red at two and below, amber at three, green from four), the full text, the reviewer and the language.
That is early enough to halt the rollout in Play Console before it reaches the other ninety percent, and early enough to answer before the review is public. When it does go public a day later, your reply is already under it.
Without the alert, the same review surfaces when someone opens Play Console or when the star average moves, and by then the rollout has finished.
One handset, or the whole release?
Google sends the device model and the Android version with every Play review, and Reviewflowz keeps both on the review record. Seven one-stars that all come from a Galaxy A54 on Android 14 are one fix. The same seven spread across every phone are a rollback. That distinction is the difference between a bad Monday and a specific ticket.
Play Console measures crash and ANR rates per phone model, and above an eight percent threshold on one model it can cut your visibility for users on that model. A review spike on one device is usually the same fault, arriving in words a few hours before it arrives in Android vitals.
Reviewflowz ships an MCP server. Connect it to Claude or ChatGPT and ask the question in plain English: which devices are this week's one-stars on, and what do they say? The answer comes back from your live Google Play reviews with the device, the Android version and the language on each one, plus the quotes it is based on.
Read-only by design. The assistant can read and count your Google Play reviews and cannot publish a reply as you. Publishing stays in Slack and in Reviewflowz.
Each language is its own channel
A Google Play review arrives in the reviewer's language, and the star rating your next user sees is specific to their country. The same crash reads as a two-line rant in German and a shrug in Portuguese, and the person who can tell the difference is the one who speaks it.
Google Play alerts get a Languages panel. Pick German and the alert carries only the German reviews, into #play-reviews-de, where the German-speaking support agent sits. Pick Portuguese for #play-reviews-br. Leave the panel empty and the alert carries every language.
Rating is the other filter. Set Send to two stars or less, all languages, and point it at #android-oncall, so the engineer on call sees every bad review in every market and nothing else. Keep one alert with everything in it for #play-reviews-all.
One alert sends to one channel, and a channel can receive as many alerts as you like. Play Console asks for the language filter every time you open the reviews page. Here it lives on the alert, so it is set once and every card that lands is already the right market.
Reply from the thread. 350 characters, published on Google Play.
Every card has a Reply button. It opens a window with the review, a box to write in, and a Suggest an AI answer button. The draft lands in the box as editable text, in the language the review was written in, and nothing reaches Google Play until you press Submit.
Google Play caps a developer reply at 350 characters. Drafts target 320, anything longer is condensed before it reaches the box, and the box counts down as you type, so the reply that reads well in Slack is the reply that posts.
The draft is written from the replies you already published on Google Play, including the ones you posted from Play Console before you had an account here. Reviewflowz picks the five to ten that best match the review on rating and language, and ranks replies you wrote by hand above ones it wrote itself.
Google Play notifies the reviewer by push and email when you reply, and they can change their rating after reading it. The reply posts back into the thread under the card, labelled with who sent it. A posted Google Play reply can be edited later from Reviewflowz, and a second reply replaces the first.
Let a rule take the five-stars that say “great app”
Every Google Play review that reaches you has words in it, because Google's API does not return bare star ratings. Most of those words are “great app” and “works fine” under five stars. There is nothing in them to get wrong, so let a rule answer them and keep your people for the reviews that describe a bug.
Reply rules run top to bottom and the first match wins. Scope a rule by star rating and platform, then choose: reply automatically, hold it for a person, or ignore it. By default nothing posts on its own. The catch-all rule at the bottom holds everything for you.
Each rule can use its own agent, so the five-star thank-you and the one-star apology are never written by the same prompt. A reply the agent posts on its own comes back into the Slack thread like any other, and into your queue as Unread until someone gives it a thumbs up or down.
Before a rule goes live, step the agent through your own past Google Play reviews one at a time and read what it would have said. It posts nothing while you look.
Forty people read the channel. Four can publish.
Allow replies is a switch on each alert, not on the workspace. Leave it off on the alert feeding #play-reviews-all and the whole company can read every Google Play review without any of them able to post as the app. Turn it on for the four people in #android-oncall and the Reply button appears on their cards only.
Same review, two channels, two sets of rights. Visibility is wide, because the product team, the founders and whoever writes the release notes should all see what a build did. The right to put words under your developer name on Google Play stays with the people accountable for them.
Typing in the thread never publishes anything. The reply window is the only route to Google Play, so a stray message in the channel stays a message.
Watching a Google Play listing needs nothing more than a search for the app. Connect the Google account that has Play Console access once, and every alert can publish. Replying from Slack is on Pro and Premium.
Translate the card. Answer in the reviewer's language.
A Google Play listing collects reviews in every language the app is installed in, and the person on call reads two of them. Pick one of six languages from the Translate to menu on the card and the translation posts as a threaded reply, so the channel keeps one card per review. Or set the alert to translate every card before it arrives.
The AI draft comes back in the language the review was written in, unless you pin an agent to one language. The next reader in that market reads your reply in their own language too.
The examples the agent works from are matched on language as well as rating, so a Portuguese reply is continued from your Portuguese replies, not translated from your English ones.
One card, one thread, both languages in it. The colleague who reads the channel next sees the review, its translation and the answer that went out, without opening a second tool.
Put the build number in the channel that shipped it
Set up in under five minutes. No demo required.
Can I reply to Google Play reviews from Slack?
Yes, once the Google account with Play Console access is connected. Turn Allow replies on for the alert, and every card gets a Reply button that opens a window with the review, a Suggest an AI answer button and a Submit button. Google Play caps a reply at 350 characters and the box counts down for you. Replying from Slack is on Pro and Premium.
How quickly does a Google Play review reach Slack?
Google Play does not push new reviews to anyone, so every tool in this category polls, ours included. Most reviews reach your channel well inside an hour, worst case about three. Google Play itself holds a new review back from the public for around a day, so it is usually in your channel before it is on the store listing.
Does the Slack card show the device the review was written on?
The card shows the app version and the language. The device model and the Android version are kept on the review record and come back through the MCP server, so you ask Claude or ChatGPT which handsets a cluster of one-stars is on rather than reading it card by card.
Can I route Google Play reviews by country?
Google Play reviews carry the reviewer's language, not their country, so alerts filter Google Play reviews by language and by star rating. App Store reviews carry the territory instead, which is why that page routes by country.
Do bare star ratings reach the channel?
No. Google's API returns only reviews with text, so every card that lands in Slack is one you can answer. Require review comment is there for the other platforms on the same alert.
Do I need a demo to get started?
No. You search for your app on Google Play and pick Slack yourself, in under five minutes. 14 day free trial, no credit card.