Evally
Start free
Product

Product feedback triage

Sort feedback into bugs, requests, confusion and praise, and surface what's critical.

Every piece of feedback gets a type, a product area and, for bugs, a severity. Data-loss bugs and users threatening to leave are pulled out so they don't wait in the backlog.

Use this judgeCustomize it

Try it live

Real calls to Jev. Pick an example or paste your own.

Examples
142
No verdict yet

Pick an example or paste your own input, then run it.

Under the hood

Every question and rule, in the open. Fork it to change any of them.

What it asks

Reads feedback, then asks 4 questions in one call.

  1. Q1TypePick one

    What kind of feedback is this?

    BugFeature requestUX confusionPraisePricingQuestionOther
  2. Q2SeverityScore

    If the feedback describes a problem, how severe is it?

    1. 0No problem, or cosmetic
    2. 1Annoying
    3. 2Blocks a task
    4. 3Data loss or a security issue
  3. Q3AreaPick one

    Which part of the product is it about?

    OnboardingBillingCore workflowIntegrationsPerformanceMobileOther
  4. Q4Might leaveYes / no

    Does the user suggest they might stop using the product over this?

How it decides

Rules run in code, top to bottom. The first one that matches gives the verdict.

  1. 1
    If Severity ≥ 2.5 of 3Critical bugreview
  2. 2
    If Might leave ≥ 0.7User at riskreview
  3. 3
    Otherwisethe answer to “Type”
  4. ·
    DefaultOther

Call it from your code

Every template runs as-is with an API key, no setup: POST /api/v1/judges/feedback-triage/run.

curl -X POST https://tryevally.com/api/v1/judges/feedback-triage/run \  -H "Authorization: Bearer $EVALLY_API_KEY" \  -H "Content-Type: application/json" \  -d '{  "input": {    "feedback": "After the update, every doc I edited offline yesterday is gone. Three days of work. If this isn'\''t fixed I'\''m moving the team to something else."  }}'

Seen in the wild

Community builds on Jev that use this pattern. Not affiliated with Evally.

More in Product