JevTicktRouter
.NET 10 and React 19 ticket triage where Jev answers five typed questions in one call and .NET business rules make the final routing.
Overview
JevTicketRouter is a support-ticket triage application built with .NET 10 and React 19. A user submits a ticket in Persian or English; the backend asks Jev five scoped questions in a single batched request, and a deterministic .NET rule engine then decides what actually happens to the ticket. Every field in the response states whether its value came from the model or a rule.
The five decisions map to Jev's primitives: category and target team as Choice questions, priority as a four-level Score, and whether the ticket contains sensitive data and whether it needs human review as Noul questions. The README notes that Noul answers carry only a probability, not a separate confidence, and the UI shows 'not reported' rather than inventing one. Rules have the final say because routing has consequences such as missed security incidents or exposed account numbers; the screenshots show a security case escalated and redacted. Without a key it starts in a labelled mock mode. The UI is fully mirrored for right-to-left Persian.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Choice | Which category does this ticket belong to? | — |
| Choice | Which team should handle it? | — |
| Score | What is the ticket's priority? | — |
| Yes / no | Does the ticket contain sensitive data? / Does it need human review? | — |
How it works
- User submits a ticket in Persian or English
- Backend sends five questions to Jev in one request
- Rule engine applies business rules to the answers
- Ticket is routed, escalated or redacted; each field shows its source
- Mock mode returns deterministic answers when no key is set
Strengths
- Rules have final authority over model output
- Transparent provenance per field
- Runs without a key in mock mode
- Bilingual with right-to-left support
Caveats
- Demo-scale application
- Live mode requires a TypeSafe key
- Rules must be maintained for real deployments
At a glance
- Type
- Project
- Status
- prototype
- Language
- C#
- Runtime
- .NET 10 backend with React 19 frontend
- Has code
- yes
Use cases and integrations
How curated lists describe it
A .NET 10 and React 19 application for fast, structured AI-powered ticket triage using TypeSafe Jev.
hellogumbo/awesome-jev
Frequently asked questions
What does Jev decide?
Category, target team, priority, whether sensitive data is present and whether human review is needed.
Who makes the final routing decision?
Deterministic .NET business rules, using Jev's answers as inputs.
Can I try it without a key?
Yes, it starts in a clearly labelled mock mode.
Related projects
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.
AppprototypeTypeScriptCLI ticket system where one Jev call answers category, priority, escalation and refund questions and Python routes the ticket.
AppprototypePythonFifteen runnable Node recipes using Jev via OpenRouter for triage, dedupe, PII scanning, reranking and a browser agent.
ArticlebetaJavaScriptExperimental 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.
ProjectprototypePython