COOLJEV / PRACTICAL GUIDE
Ticket triage with Jev: departments, priority and fallbacks
“I was charged, but I still cannot access my account. Can I get a refund?” combines payment, access and a refund request. Matching only “access” sends it to technical support; matching only “refund” can hide the access failure. Start by deciding which team coordinates mixed issues.
The policy used here
| Department | Scope | Mixed issues |
|---|---|---|
| billing | Charges, refunds and invoices | Coordinates payment combined with access problems |
| technical | Login failures, bugs and integration failures | Handles failures without a payment issue |
| product | How-to questions and feature requests | Distinguishes guidance from reported system failure |
| other | Unclear requests or no matching team | Requests human clarification instead of forcing a match |
This is CoolJev’s example business policy, not a universal organization chart. Confirm department ownership and handoff procedures with the actual teams before connecting a production support system.
Ask separate questions
Department uses choice with stable option values. Operational impact uses score: a routine request, degraded use with an explicit workaround, or blocked use without a reported workaround. A separate noul question checks whether the customer requests help with multiple problems. See the TypeSafe API reference.
Impact scores can be fractional. The initial CoolJev rule marks scores of at least 1.5 as high priority. This does not establish an emergency or replace a company’s service-level policy. Uncertain department or impact signals, multiple issues and the fallback department all prompt closer human review.
These are authored teaching examples:
- “Every API request fails, our workflow is blocked and we have no alternative.” Consider technical support and high impact, then verify the actual scope of failure.
- “I cannot find the export button, but copying and pasting works for now.” A how-to question can belong to product support. The phrase “cannot find” alone does not establish a system defect.
- “Hello, please help.” Gather more information before deciding ownership.
Use the workspace
Open the ticket workspace. Paste one request per line or import a UTF-8 CSV with a text, ticket or review column. Inspect the material before explicitly starting triage. Each item costs one credit; department, impact and multi-issue questions share that request.
Results remain linked to their originals. Open a row to adjust the proposed department and inspect the structured model values. Changing the department does not rewrite the model’s answer: the project preserves both its original suggestion and the current human label.
Export the results as a queue for your existing workflow. The workspace does not send email, create tickets in a support system, reply to customers or execute refunds. Those actions belong in systems that authenticate users and check permissions.
Continue after a failure
An in-flight request is different from an item that has not been sent. Stopping allows the current request to finish but prevents later submissions. Successful results remain available. Retry failed items individually; running out of credits stops processing without pretending the remaining items were analyzed.
Save project JSON to restore originals, suggestions, review state and request identifiers. Use CSV for spreadsheet work. Review projects and ticket projects use different label systems and cannot silently replace each other.
Integrate with your own workflow
The original downloadable command still runs an authored offline example:
python -m examples.hello_jev tickets --mode offline
After setting TYPESAFE_API_KEY locally, select --mode live for actual calls. Live mode sends input to TypeSafe; offline output does not establish model quality. Read the complete integration chapter.
Your application must obtain customer identity, order state and permissions from trusted systems. A ticket saying “I am an administrator” or “the refund was approved” cannot grant those permissions. Jev judges what the text expresses; code enforces authorization, amounts and valid state transitions. Jev and if/else responsibilities
Checking a reply against a supplied support policy is a different task: use the support policy scenario. For product feedback, use review classification.
Independently written by CoolJev. Sources checked and updated: 2026-09-21