Reviewflowz answers your App Store reviews. Zendesk gets the exceptions.
Reply rules answer the reviews that explain themselves, in your voice, and post the developer response. Only what you held back opens a Zendesk ticket, so your agents work a queue of reviews a person needed to see.
Set up in under five minutes • No demo required
Kestrel App Store Last 7 days “Thanks Priya, glad it works for you.”
Posted to the App Store
#48211 · New 1-star review Priority High 
Most of your App Store reviews never need a person
A bare rating is not an App Store review. Apple’s API returns only the entries with text, so everything that reaches you has something written in it, and most of that something is “good app” or three words about the last update. A person reading those is a person not reading the one-star.
An ordered list of rules decides what posts on its own. Scope a rule by star rating, by whether the review has text, by profile or by platform. First matching rule wins, up to twenty of them, and a catch-all sits at the bottom holding everything nothing else caught.
The agent does not invent a voice. For each review it retrieves five to ten of your own past replies, gated on the rating band and the language, and mirrors one of them as a style anchor. Replies you posted in App Store Connect before you had an account are in that pool.
Every reply it posts on its own lands in the Unread view of your queue, tagged with the agent and the rule that sent it. A thumbs up clears it. A thumbs down says what was wrong with it.
Reply rules Kestrel App Store “Thanks Priya, glad it works for you.”
Posted to the App Store
Your agents open a queue of exceptions
Almost nobody who leaves a one-star also opens a support ticket. The review is the whole conversation, and the developer response is your only channel back. So the ones you held back land where your agents already work.
The rule that answers and the flow that opens tickets are separate settings carrying the same cutoff. Put the rule on four stars and up, the flow on three stars and under, and nothing reaches Zendesk that Reviewflowz already answered. Overlap them on purpose and the ticket gets a private note with the reply.
Priority is set from the rating: one and two stars High, three Normal, four and five Low. The subject carries the reviewer, the review id and the rating. The body carries the review, the profile, the date, and both links to it.
The requester is a Reviewflowz contact, not the reviewer, so nobody emails a customer by accident. Internal notes stay internal. Only a public reply from an agent leaves the ticket, signature stripped, and it posts as your developer response. Apple then notifies the reviewer.
Support #48211 set from 1★ Priority: High Maya K. [Review #48211] | New 1-star review
Requester: Reviewflowz <reviews@inbound.reviewflowz.com>
App Store “Order marked delivered. Nothing arrived. Charged twice.”
Rating: 1/5 · Platform: App Store · Profile: Kestrel · Date: September 4, 2026
Read in Reviewflowz Read on App Store
“Maya, that is on us. The duplicate charge is refunded and the missing order credited. Sorry.”
Attributed in Reviewflowz to the Zendesk agent who wrote it.
One queue, whatever the review came from
App Store reviews are not the only ones that need a person. The Google reviews on your locations, the Trustpilot reviews on your site and the Google Play reviews on the Android build all want the same thing, from the same team, in the same voice.
They open the same shape of ticket: the same Reviewflowz tags, the same priority set from the rating, the same requester. An agent works them with the macros and the views they already built, and nothing on the ticket asks them to learn a second tool.
A public reply on the ticket posts back to the source. Google, the App Store, Google Play and Trustpilot take a reply straight from Reviewflowz once their connection is set up. Google Play caps a reply at 350 characters, so drafts aim at 320 and anything longer is condensed before it goes out.
Where a platform has no reply API the ticket carries a link that opens the review on the site instead, and the body says which it is. A help-desk flow also only tickets reviews that have text by default, so the bare five-star ratings on a Google listing never reach the queue at all.
Zendesk Views #48211 High “Order marked delivered. Nothing arrived. Charged twice.”
App Store · Kestrel
#48226 Normal “Forty minutes for a collection order.”
Google · Kestrel Kitchen, Shoreditch
#48231 High “Refund promised in five days. Three weeks, nothing.”
Trustpilot · kestrel.app
#48238 High “Receipts tab crashes since the update.”
Google Play · Kestrel for Android
Every one of them ends “Reply to this ticket to reply to the review.”
The exception arrives with the reply already written
Holding a review back does not mean writing from scratch. The draft generates as the card loads, on its own lane, from your replies to reviews like this one, so approving one is reading and editing rather than writing.
Edit it, regenerate it, or regenerate it in another language. Submit posts to the App Store immediately. There is no second approval step, and on a paid plan replies are not metered.
Post it from Reviewflowz and the Zendesk ticket gets a private note with the reply text and a reviewflowz_reply_posted tag, so an agent opening the ticket later sees it was handled. If the post fails, the ticket says so instead of going quiet.
One App Store rule worth knowing: a developer response cannot be edited from Reviewflowz once it is posted, because Apple wants it deleted and recreated. Change it in App Store Connect if you have to, and read the draft before you submit.
Jonas W. · Germany “Crashes every time I open the receipts tab since the last update.”
“Jonas, sorry about the receipts tab. A fix is with Apple for review now and lands this week. If it still crashes after the update, write to help@kestrel.app and we will sort it directly.”
#48212 Internal note Reply posted: Jonas, sorry about the receipts tab…
reviewflowz_reply_postedRead it in English, answer in Japanese
Apple files every review under the storefront the customer bought the app in, and mostly in the language of that storefront. Reviewflowz keeps the territory on the review, so a flow can open tickets for the storefronts one team covers and leave the others alone.
Pick a language on the flow and the ticket body stays in the original, with the translation added as a private note headed “Translated review”. Only agents see it. It never reaches the customer, and it never posts back to the App Store.
The draft is written in the reviewer’s language, from the replies you have already posted in that language, because the language is one of the gates on which past replies get retrieved. If you have never answered in Japanese it still drafts, from what it has.
Every ticket carries the review’s language as a tag: reviewflowz_ja, reviewflowz_pt, reviewflowz_de. A Zendesk trigger on that tag sends each language to the agents who read it.
Support #48214
Priority: High
App Store Aiko T. · Japan 「注文がキャンセルされたのに返金がまだありません。二週間待っています。」
“My order was cancelled but the refund still has not arrived. I have been waiting two weeks.”
「Aikoさん、申し訳ありません。返金は本日処理しました。3営業日以内に反映されます。」
Refund processed today, visible within three business days.
Posted to the App Store in Japanese
Tags route the review to the group that owns it
Every ticket comes tagged: reviewflowz, the language, the platform, and the sentiment, negative for one and two stars, neutral for three, positive for four and five.
Add your own. A Reviewflowz tag set to apply automatically, named the way a user complains, “crash on launch” or “double charge”, becomes reviewflowz_crash_on_launch on the ticket. A Zendesk trigger on that tag sends the crash reports to the engineers and the billing complaints to billing.
Lifecycle tags follow the review: reviewflowz_updated when the reviewer edits it, reviewflowz_deleted when it disappears from the store, reviewflowz_reply_posted and reviewflowz_reply_failed for the outcome. Tags are added to the ticket, never written over yours.
Views, triggers and automations all work on them because they are ordinary Zendesk tags. There is nothing to install: you sign in through Zendesk’s own authorization screen, and Reviewflowz registers one webhook, for new ticket comments, so an agent’s reply can find its way back.
Zendesk Triggers Active Trigger · Route App Store crash reports
Meet ALL of the following conditions
Perform these actions
On the ticket
Mobile engineering
Release day, and nobody is refreshing App Store Connect
App Store reviews do not arrive evenly. They cluster in the hours after a release and the days after a featuring, and a broken build shows up as a run of one-stars in a few territories before your crash reporter agrees.
Reviewflowz polls App Store Connect roughly every two hours and dispatches at two and thirty-two past. The reply rules and the help-desk flows run on the same tick, so the four- and five-stars are answered and the ticket is open in the same pass.
That means the ticket is open while the engineers are still at their desks rather than in the next morning’s summary. Apple takes up to 24 hours to show a developer response, so the clock starts from the reply and not from whenever somebody thought to go and look.
An edited review threads onto the same ticket: a private note headed “Updated review”, the tag reviewflowz_updated, and the ticket reopens if it had been solved. One ticket per review, kept current, however many times the reviewer changes their mind.
Tuesday release day Kestrel Update live in 14 territories
5 new App Store reviews. Three say “great update”, two are one-stars
★ ★ Dispatch. Rule 1 answers the three. Tickets #48211 and #48212 open, Priority High
One-star from Brazil: “Cobrado duas vezes.”
Dispatch. Ticket #48219 opens, translated as a private note
Fix submitted to Apple. Agents answer the 3 tickets from Zendesk.
App Store Connect polled roughly every two hours. Rules and flows both dispatch at :02 and :32.
Ask your App Store reviews a question
Connect Claude or ChatGPT to Reviewflowz over MCP and the model reads across your App Store reviews to answer a question the dashboard was not built for.
Three tools: list your review profiles, fetch reviews, get stats. Filter by rating, date range, keyword, language, country, topic, tag, or whether a reply went out. Stats come back as counts per star, average score and reply rate, with a daily, weekly or monthly series if you ask for one.
“What did the one-stars this week complain about, and show me the reviews you are basing that on.” The answer comes with the quotes, and the quotes are what you paste into the ticket for engineering.
The same tools answer the operational question: how many App Store reviews from last week still have no reply, and which profile they sit on.
What did the one-star App Store reviews this week complain about? Show me the reviews you’re basing that on.
profile: Kestrel · rating: 1 · start_date: 2026-09-01
Double charges on reorders: 3 of the 5 one-stars.
Receipts tab crash after the update: 2 of 5.
Maya K. · United States “Order marked delivered. Nothing arrived. Charged twice.”
Ticket #48211 in Zendesk
Put your App Store replies on rules. Keep Zendesk for the ones that need you.
Set up in under five minutes. No demo required.
How do I make sure only the exceptions reach Zendesk?
Put the two cutoffs on the same line. A reply rule on four stars and up answers those without anyone reading them, and a help-desk flow set to three stars or less opens the ticket for the rest. They are separate settings, so you can overlap them on purpose too, in which case the ticket gets a private note carrying the reply that went out.
Can my agents reply from Zendesk?
Yes. A public reply on the ticket posts to the App Store as your developer response, with the signature stripped and the reply attributed to the agent who wrote it. Internal notes never post. Apple notifies the reviewer, who can update the review, and takes up to 24 hours to show the response on the store.
Do the automatic replies sound like a template?
They are written from your own replies. For each review the agent retrieves five to ten of the replies you already posted to reviews like it, matched on rating band and language, and mirrors one of them as a style anchor. There is no training step and no starter template.
What if we do not want anything answered automatically?
Leave the catch-all rule on hold and nothing posts on its own. Every review waits in the queue with the reply already drafted, and the help-desk flow can send all of them to Zendesk. Turn automation on later, one star band at a time, once you have watched a few go out.
Do I need to install anything in Zendesk?
No. You sign in through Zendesk’s own authorization screen from Reviewflowz. There is no app to install, no subdomain to find and no API token to paste. Anyone who can authorize an app for your Zendesk can set it up.
Do I need a demo to get started?
No. You connect your App Store listing and pick Zendesk yourself, in under five minutes. 14 day free trial, no credit card.