Jev App Review Triage

Why Jev

One decide call returns topic, tone, severity, and refund/chargeback signals your queue can branch on. Example: offline sync broken + cancel threat → topic=bug, high severity, escalate path — without drafting a reply.

How to define the decision

State = review text (and optional star rating / app version). Choice for topic and tone; Score for severity; Noul for refund_pressure and chargeback_risk. Keep label sets identical to your CRM stages.

Sample input and output

From the live tool template. Run it in the playground for a real API response — sample labels below are illustrative until you click Run.

review: Google Play · NoteSync · ★★☆☆☆
"After the latest update, offline notes stop syncing on Android 14. Cleared cache twice — still stuck. If this isn't fixed soon I'll cancel the subscription."

Auto-route only high-confidence topic labels. Mid-confidence or high refund/chargeback Noul → human queue. Severity Score is for prioritization, not auto-refunds.

Failure modes and human fallback

• Upstream or network errors: retry with backoff; do not invent a decision.
• Low confidence: route to a human queue or safer default — never auto-act on money/destructive tools.
• Schema drift: keep a golden fixture set in CI so label changes fail the build before production.
• Never auto-issue refunds from Jev alone.
• Fail closed to human review on API errors or low confidence.
• Reply drafting stays in templates or a generative LLM.

API example

Same prepaid jv_live_ balance as tools. Output tokens are free on this host's metering model.

curl https://jevtypesafe.org/api/v1/decide \
  -H "Authorization: Bearer jv_live_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{"state":"Google Play · NoteSync · ★★☆☆☆\n\"After the latest update, offline notes stop syncing on Android 14. Cleared cache twice — still stuck. If this isn't fixed soon I'll cancel the subscription.\"","questions":{"topic":{"type":"choice","instructions":"What is this review mainly about?","criteria":{"bug":"something is broken or regressing","billing":"charges, refunds, subscriptions","ux":"confusing interface or hard to use","feature":"asks for a missing capability","praise":"positive feedback with little complaint"}},"refund_pressure":{"type":"noul","instructions":"Is the reviewer explicitly pushing for a refund?"},"chargeback_risk":{"type":"noul","instructions":"Does the reviewer threaten a chargeback or payment dispute?"},"tone":{"type":"choice","instructions":"What is the dominant tone?","criteria":{"calm":"measured and factual","frustrated":"annoyed but still constructive","hostile":"aggressive or insulting","confused":"unsure what happened"}},"severity":{"type":"score","instructions":"How severe is the product impact described?","criteria":["minor annoyance","limited impact","major workflow break","blocking / revenue risk"]}}}'

FAQ

Does this connect to the App Store API?

No. Your worker fetches reviews, calls /api/v1/decide (or the App Review tool), then applies labels in your helpdesk.

How do I try it here?

Open App Review Triage in the playground, run the sample, then reuse the same questions with a jv_live_ key.

Related use cases

• Jev Support Triage
• Jev Content Moderation
• Jev Screenshot UI Box (beta)