Skip to content
System One

Incident triage in Box (X)

A video demo uses Jev for incident triage in Box: it answers whether an incident is customer-facing and how severe it is, then routes the file into Escalate, Monitor, or Review folders and sets a metadata template with the result. Incidents below a confidence threshold go to Review for a human instead of routing automatically.

Still from Incident triage in Box (X)Play the video in the post below
Still from x.com

Post on X

Views
144,688
Likes
44
Reposts
10

Read from X on . Counts change daily.

Box built a demo of Jev classifying and routing incident reports inside Box. The workflow pulls an incident report from Box, builds a state object from it, and asks Jev two questions: is this customer-facing, and how severe is it. Jev answers typed questions in a single pass, so there is no free-text output to parse.

Based on those answers, the file moves into one of three folders, Escalate, Monitor, or Review, and a metadata template instance is set on the file with the result. Each answer comes back with a confidence estimate, so anything below the threshold goes to Review for a person instead of routing itself. Box’s post puts the appeal this way: Jev returns booleans with probabilities, enums and scores, so there is no output to parse and no schema to keep in line.

Open on X

More like this

Use cases this is tagged with