prompts.chatprompts.chat
Login
All classifiers
NoulOrders & returns

Reported problem confirmed

Check whether the inspection notes confirm the problem the customer reported.

F@f

Limits to keep in mind

Never reject a return or flag a customer automatically from this answer.

Problem

Defective returns are refunded, sent back to suppliers or refurbished depending on whether the fault is real. Comparing the customer's words with the inspector's notes by hand doesn't scale.

Goal

Separate confirmed faults from returns where the problem wasn't reproduced, and send every unconfirmed case to a person rather than rejecting it.

Input / state

The customer's reason and the inspector's test notes.

customer_reason
What the customer said was wrong.
inspection_notes
What the inspector tested and observed.

Decision question

NoulQuestion key problem_confirmed

Do the inspection notes confirm the problem the customer reported?

What counts as yes and no

  • trueThe notes describe testing that reproduced the reported problem or found the described difference.
  • falseThe notes describe testing of the reported problem that found it working or matching the listing.

Allowed outcomes

Decided in your code from the answer and its confidence. Thresholds are yours to set and test.

  • ConfirmedProbability of yes is above your upper threshold.
  • UnclearProbability falls between your two thresholds.
  • Not reproducedProbability of yes is below your lower threshold.

Example scenarios

Predefined demonstrations. No model is called; the outcome shown is an illustrative judgment.

Example state

{
  "customer_reason": "Won't charge.",
  "inspection_notes": "Does not power on with a known-good charger and cable."
}

Outcome

Illustrative
Confirmed

Probability of yes is above your upper threshold.

Why

The inspector reproduced the reported fault.

Using it well

  • "Not reproduced" is not a verdict on the customer. Intermittent faults are common; send these to a person who can contact them.
  • Ask inspectors to note what they tested. Notes that don't mention the reported problem should land in the unclear band.

Request definition

POST https://api.typesafe.ai/v1/systemone
{
  "model": "jev-latest",
  "state": {
    "customer_reason": "<customer_reason>",
    "inspection_notes": "<inspection_notes>"
  },
  "questions": {
    "problem_confirmed": {
      "type": "noul",
      "instructions": "Do the inspection notes confirm the problem the customer reported?",
      "criteria": {
        "true": "The notes describe testing that reproduced the reported problem or found the described difference.",
        "false": "The notes describe testing of the reported problem that found it working or matching the listing."
      }
    }
  }
}

Request shape from the System One API reference; a Kev server accepts the same body. Replace the placeholder state with your data. Requests need your own API key or server.

Version History

v1Current Versionabout 8 hours ago@f

Initial version

Comments (0)