Follow these steps
Complete the workflow, then verify it
- 1
Start with urgency
Use one- and two-star filters for reviews that need immediate support or product attention. Keep four- and five-star feedback available for praise, research, or reports.
- 2
Add known issue keywords
Choose a short list such as crash, login, billing, refund, or subscription when each term maps to an owner. Review the terms regularly and remove noisy matches.
- 3
Use locales deliberately
Route a locale or region only when a person can investigate it. Locale filters are most useful for translation, pricing, release, or regional support issues.
- 4
Pick the destination by action
Send urgent work to Slack or a helpdesk, and use email or a scheduled report when a stakeholder needs a lower-frequency summary.
- 5
Test and tune
Send a test alert, ask the destination owner whether the message is actionable, and revisit the rule after the first week. More filters do not automatically mean better signal.
Quick checklist
- ✓Every rule has a named owner.
- ✓Keywords are specific enough to avoid noise.
- ✓Locale filters map to a real support or product workflow.
- ✓The destination was tested.
If something does not work
A keyword rule matches too much+
Replace broad words with a phrase or combine the keyword with a low-star or locale condition where the product supports it.
Important reviews are missed+
Check spelling, language, platform, and rating filters. Use the full review view or report to discover the language customers actually use before adding rules.
Frequently asked questions
Should I alert on all five-star reviews?+
Usually keep positive reviews in the monitoring view or a dedicated praise workflow. Alert on them only when someone will share or respond to them.
How often should rules be reviewed?+
Review rules weekly during the first release cycle and after a major launch, then remove temporary rules when their owner no longer needs them.