Customer & sales

Product feedback

Classify feedback, rate its impact, and flag blocked tasks.

For product managers and small software teams

Jev AI playground

Checking availability…

Text

221 / 50,000

Try different inputs · Product feedback

Load an input to edit it. Tokens are used only when you run it.

Normal input

A clear bug with a time-consuming workaround should not be treated as a completely blocked task.

Ambiguous input

Distinguish confusing behavior from a new feature request; do not infer high impact from dissatisfaction.

Missing information

Recognize that the feature, failure, deadline, and workaround are unspecified.

Questions3

choiceChoose the main issue. Classify a previously working feature that now produces incorrect output as a bug.⌄

Question

Answer options

scoreRate the stated impact on the task. Do not assume an unknown deadline or absent workaround.⌄

Question

Scale points, from lowest to highest

Yes / NoDoes the feedback explicitly establish that the task cannot be completed using any available workaround? Extra manual work alone does not count as blocked.⌄

Question

Advanced: edit JSON

Edit or paste a question configuration.

[
  {
    "id": "feedback_type",
    "type": "choice",
    "instructions": "Choose the main issue. Classify a previously working feature that now produces incorrect output as a bug.",
    "options": [
      {
        "label": "bug",
        "description": "Existing behavior fails or produces an incorrect result."
      },
      {
        "label": "feature_request",
        "description": "A capability the product does not currently offer is requested."
      },
      {
        "label": "usability",
        "description": "The existing feature works but is confusing or difficult to use."
      },
      {
        "label": "billing",
        "description": "Charges, invoices, pricing, or refunds are the main issue."
      },
      {
        "label": "praise",
        "description": "Positive feedback with no problem or request."
      },
      {
        "label": "other",
        "description": "The message falls outside these categories or lacks enough detail."
      }
    ]
  },
  {
    "id": "work_impact",
    "type": "score",
    "instructions": "Rate the stated impact on the task. Do not assume an unknown deadline or absent workaround.",
    "options": [
      {
        "label": "0",
        "description": "No meaningful disruption is described"
      },
      {
        "label": "1",
        "description": "A small inconvenience with an easy workaround"
      },
      {
        "label": "2",
        "description": "Significant extra work, but the task remains possible"
      },
      {
        "label": "3",
        "description": "A critical task cannot be completed using the stated available options"
      }
    ]
  },
  {
    "id": "blocks_work",
    "type": "noul",
    "instructions": "Does the feedback explicitly establish that the task cannot be completed using any available workaround? Extra manual work alone does not count as blocked.",
    "options": []
  }
]

Runs use input tokens and are saved to your account.

Results

Your answers will appear here.

Add your text and questions, then run Jev.

Probabilities express model confidence, not a guarantee of correctness.

Set up this template

Identify bugs and feature requests, then check how much they disrupt the customer’s work.

What to provide

One feedback message with the affected feature, customer task, and any stated workaround.

Paste one customer comment, including the task and any workaround.
Adjust the categories and the four impact levels to match your product.
Check the feedback type, impact score, and whether the customer can finish their task.

Outputs and rules

feedback_type · choice

The main kind of feedback.

Choose the main issue. Classify a previously working feature that now produces incorrect output as a bug.

bug: Existing behavior fails or produces an incorrect result.
feature_request: A capability the product does not currently offer is requested.
usability: The existing feature works but is confusing or difficult to use.
billing: Charges, invoices, pricing, or refunds are the main issue.
praise: Positive feedback with no problem or request.
other: The message falls outside these categories or lacks enough detail.

work_impact · score

A 0–3 scale for disruption, separate from sentiment.

Rate the stated impact on the task. Do not assume an unknown deadline or absent workaround.

0: No meaningful disruption is described
1: A small inconvenience with an easy workaround
2: Significant extra work, but the task remains possible
3: A critical task cannot be completed using the stated available options

blocks_work · Yes / No

Whether the task is impossible using the available workarounds.

Does the feedback explicitly establish that the task cannot be completed using any available workaround? Extra manual work alone does not count as blocked.

Try different inputs

Normal input

A clear bug with a time-consuming workaround should not be treated as a completely blocked task.

After yesterday’s update, the CSV export still downloads, but the date column is empty. The dates are visible in the dashboard. I need to send our weekly report this afternoon and currently have to copy the dates by hand.

Ambiguous input

Distinguish confusing behavior from a new feature request; do not infer high impact from dissatisfaction.

The export now asks me to choose a date format. I expected it to remember my last choice. I can still download the report.

Missing information

Recognize that the feature, failure, deadline, and workaround are unspecified.

Something is wrong with the report. Please fix it.

Use the result

Group similar bugs for review. Use a high impact score to prioritize investigation, and ask for reproduction steps before treating the report as confirmed.

Limits to keep in mind

The impact score is based on the customer’s message, not a product test. If they don’t mention a workaround, don’t assume there isn’t one.

Jev AI playground

Your answers will appear here.

Set up this template

What to provide

Outputs and rules

Try different inputs

Use the result

Limits to keep in mind

Related tasks