jev-ticketing-demo
CLI ticket system where one Jev call answers category, priority, escalation and refund questions and Python routes the ticket.
Overview
Jev Ticketing System Demo is a CLI support-ticket system that uses Jev to triage incoming tickets. Each new ticket goes to Jev in one parallel call with four typed questions: category (Choice), priority on a 0 to 3 Score, whether to escalate (Noul) and whether it is a refund request (Noul). A plain Python router then picks the team queue, sets SLA hours, flags escalations and sends low-confidence results to manual review.
The separation is explicit: Jev decides what a ticket is, the router decides what to do about it. Tickets are stored in a JSON file, sample tickets can be loaded from the menu, and router tests run with pytest. Without an API key the app runs in an offline mock mode using keyword rules, so the demo always works. Setup instructions target VS Code with Python 3.10+.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Choice | Which category does this ticket belong to? | — |
| Score | What priority is this ticket (0-3)? | 0 · 1 · 2 · 3 |
| Yes / no | Should this ticket be escalated? | — |
| Yes / no | Is this a refund request? | — |
How it works
- New ticket enters the CLI
- One Jev call answers four questions
- Router sets queue, SLA and escalation flags
- Low confidence goes to Manual Review
Strengths
- Clear split between classification and business rules
- Offline mock mode for demos
- Router unit tests
Caveats
- Demo with JSON storage, not a production system
- Mock mode uses keywords, not Jev
Getting started
pip install -r requirements.txt, optionally add your key to .env, then `python main.py` and choose option 5 to load sample tickets.At a glance
- Type
- App
- Status
- prototype
- Language
- Python
- Runtime
- CLI
- Has code
- yes
- Has tests
- yes
Use cases and integrations
How curated lists describe it
AI-powered support ticket triage and routing system using JEV, with automated…
wh000wh000/awesome-jev-live
Frequently asked questions
What does Jev decide?
The ticket's category, priority, whether to escalate and whether it is a refund request.
Who decides routing and SLAs?
The plain Python router in app/router.py.
Does it work without a key?
Yes, offline mock mode uses keyword rules.
Related projects
.NET 10 and React 19 ticket triage where Jev answers five typed questions in one call and .NET business rules make the final routing.
ProjectprototypeC#Cloudflare Flue agent example that adds a validated route_with_jev tool for typed support routing through AI Gateway.
ServiceprototypeTypeScriptE-commerce support sandbox where Jev classifies intent, emotion and escalation and blocks risky agent replies before sending.
AppprototypeTypeScriptExperimental lab for semantic business gates: each gate is an independent Jev Noul that code maps to NO, REVIEW or YES by threshold.
ProjectprototypeLangGraph student-support agent with PII masking and hybrid RAG, where Jev verifies drafts before auto-reply or human review.
ProjectprototypePythonProvider-independent .NET decision engine with a separate TypeSafe Jev provider package mapping Choice, Score and Noul to /v1/systemone.
LibrarybetaC#