← Back to Blog
Review operations3 min read

App Review Alert Rules: Star Ratings, Locales and Ownership

Use the filters ReviewBot actually supports, then decide who should read and act on the delivered reviews.

Published August 1, 2026Updated September 8, 2026By ReviewBot Editorial Team

Separate product rules from your team’s process

Notification Flows select star ratings and one country or language. Global Scanning covers all available scope as a paid add-on. Translation is optional and paid. Keyword, topic and release-version filtering are not currently offered.

Set up a low-star triage Flow

Choose New Flow and review notifications, select one public listing, connect the destination, and select one- and two-star ratings. Choose the scope the recipient supports, review add-ons, then save. Check the introduction message and subsequently a new matching review.

Choose an owner for each stream

A useful starting split is a low-star support channel and, only if someone needs it, another Flow for higher-rated feedback. A separate listing or destination requires another Flow. Classifying billing, crashes and feature requests happens after delivery.

  • Support checks the low-star stream during its normal queue review.
  • Product reads selected examples in a weekly discussion.
  • Praise is shared only when someone owns that task; an unused channel is unnecessary.

Adjust after reading the results

Record how many delivered reviews were relevant and how many led to action. Change one setting at a time. If the source has little new feedback, waiting for new reviews is more useful than repeatedly rebuilding the connection.