judged.systems

About judged.systems

Support systems call judged.systems when a ticket needs a judgment. The helpdesk stays the system of record. You send the ticket. A pack defines the questions: queue, urgency, refund request, policy risk. Back comes a choice and its probabilities, a score on a rubric, or the probability a statement is true. Your thresholds return accept or review. A failed call stays in review. The ticket is redacted first. The evaluation is stored as it happened. A label on a miss leaves it untouched.

The person behind judged.systems

• 
  Oleksandr Halashevskyi

  Maker

  product engineer - ohalashevskyi.com

  o***@judged.systemsProbable