Triage a backlog of support tickets
A backlog is hard to prioritize by reading. Jev assigns each ticket a team, an urgency level and a churn-risk flag, so you can start with the tickets where a customer is losing money or about to leave.
What you upload
A CSV with one ticket per row, in a column such as ticket, body or message.
What you get back
- Category: billing, integrations, bug, account or feature request
- Urgency from can wait to critical
- Churn risk flag for unhappy customers
- A sortable queue with the critical tickets on top
How it works
- 1
Upload your file
A CSV with a header row, up to 1,000 rows and 2 MB. Or start with the sample data to see the result first.
- 2
Run it
You see the credit cost before anything is charged. Rows run in chunks with live progress, and failed rows are refunded.
- 3
Read and export
A summary chart, a sortable table and a CSV with every answer and its probability.
Each row is one evaluation: 1 credit for up to 8,000 characters and 5 questions, 3 credits above that. New accounts start with 200 free credits.
Run it on your data
Answers are model judgments with a probability attached. Check a sample of rows before acting on the full result.