Skip to main content
Triggers determine which reviews get automatic responses and which ones don’t. Every rule starts with a required rating condition, and you can layer on any number of additional filters.
Start specific, then expand. It’s easier to broaden a narrow rule than to fix an overly broad one that’s responding to the wrong reviews.

​
Review rating

The rule builder's Trigger conditions panel: a Review rating condition set to "Is" five stars, and an Additional filters row for Review Length
Every automation requires a rating condition. Pick an operator, then a star count from 1 to 5:
  • Is + 5 stars targets exactly 5-star reviews
  • Is not + 1 star targets every rating except 1 star
Be careful with Is + 1 star rules — these users are often extremely frustrated and may benefit from manual, personalized responses.

​
Rating strategy examples

Condition: Is 5 starsUse case: Thank users who love your app, potentially ask for referrals or feature requests.
Condition: Is 3 starsUse case: Users who like your app but have specific concerns worth addressing.
Condition: Equals or less 2 starsUse case: All negative feedback requiring immediate, empathetic response.

​
Additional filters

Beyond the rating, add any number of conditions to narrow a rule further. Each one is a Review text, Language, Review length, or Featured review filter, combined with AND logic — a review must match every condition to trigger the rule.

​
Review text

Common uses:
Enter one or more keywords in the keyword editor — a review matching any of them satisfies the condition.Tips:
  • Use multiple automations for different keyword groups rather than one complex rule
  • Include common misspellings: "recieve" and "receive"
  • Consider synonyms: "bug", "glitch", "broken", "error"

​
Language

Target one or more specific languages, or exclude them:
“Language is [one or more languages]” — select as many languages as you want in a single condition. A review matching any of the selected languages triggers the rule.
  • Groups related markets into one automation, e.g. Spanish + Portuguese for Latin America.

​
Review length

Fine-tune based on how much detail users provide. Length is measured in characters, from 1 to 350:
Quick ratings with minimal text — e.g. shorter than 50 characters for brief acknowledgments to one-line reviews.
Targets reviews currently highlighted as featured on your store listing. These are the most visible to potential users browsing your app page, so pair this with AI-generated responses and detailed instructions to keep the reply polished.
Featured reviews change over time as the app store rotates them. If a review loses its featured status after your automation already responded, the response remains in place.
This is a separate switch from the “Review is featured” condition above. Featured reviews are often older than a rule’s normal live-review window, so by default a rule only reacts to the store’s live review feed. Turning on Also reply to featured reviews extends that same rule to your app’s featured reviews too, instead of requiring a second rule. It’s available on the Pro plan.

​
Combining conditions (AND logic)

The real power comes from combining the rating condition with multiple additional filters — every condition must match:
Conditions:
  • Rating Is 5 stars
  • Review text contains "feature"
  • Language is English
  • Review length longer than 80 characters
Result: Happy users providing detailed feature feedback — good candidates for beta programs or surveys.
Conditions:
  • Rating Equals or less 2 stars
  • Language is not English
  • Review text contains "bug"
Result: Non-English users reporting bugs — needs immediate AI translation.
Conditions:
  • Rating Is 3 stars
  • Review text does not contain "price"
  • Review length longer than 50 characters
Result: Neutral users with specific (non-price) concerns that can be addressed.

​
Testing your conditions

While you build a rule, the builder’s preview panel shows how many of your app’s recent reviews match your current conditions, expressed as a coverage percentage. It also pages through real example matches, each with a generated “Potential response.”
Watch the coverage percentage as you add conditions. A rule matching close to 0% is too narrow; one matching a very large share of your reviews may be too broad to give every match the attention it deserves.
Always test before going live. You can also create a rule in disabled mode, save it, and check the Reviews Feed to see which reviews would have matched, without it posting anything.

​
Debug checklist

Your conditions might be too specific:
  • Remove one condition at a time to see which is limiting matches
  • Check for typos in keywords
  • Consider synonyms and alternative phrasings
  • Verify your apps are properly connected

Actions

Configure template-based and AI-generated responses for your automations

Automations overview

See how triggers fit into the rest of an automation rule