Skip to main content
Two layers of review intelligence.

​
Layer 1 — Daily review summary

Every run pulls reviews from two sources and merges them:
  • Appeeky API — public reviews scraped from the App Store (since lastRunAt)
  • App Store Connect — asc_reviews table (richer: territory, response state, app version)
Surfaced in the briefing as:
Unanswered reviews are flagged so the agent can propose asc_review_reply actions (in write mode).

​
Layer 2 — Crisis Mode

A rolling 30-day baseline is maintained per app in cofounder_review_baselines:
Each run we sample the last 24 hours and compare. A crisis is declared when:
  1. ≥ 3 negative reviews (1-star) in 24h, AND
  2. The 1-star share is ≥ 3× the baseline
When triggered, the agent surfaces it above the regular briefing:
When the share is elevated but doesn’t meet the crisis threshold, the agent shows it as ⚠️ Elevated negativity instead.

​
What the LLM does with it

  • crisis field in the structured DailyReport is populated with severity (watch / elevated / critical)
  • The briefing leads with the crisis section
  • A prioritizedAction is added with priority: "critical" recommending an immediate fix
  • If a version is implicated, the agent proposes a hotfix path (e.g., a linear_issue or github_issue action)

​
False-positive guard

The minimum-3-reviews floor prevents tiny apps from triggering crises off a single bad week. The 30-day window is rolling so the baseline naturally adapts to your app’s normal review noise level.