cooljev.中文
← Back to the ticket triage guide

PRACTICE / TICKETS

AI Ticket Triage: Department & Priority from CSV

Import text, get Jev suggestions, then confirm the results yourself.

Import a CSV, get Jev department and priority suggestions, review and export. Free beta credits; no helpdesk connection or automatic assignment.

Download a CSV with 3 fictional inputs · Workflow and criteria

The template has no assigned labels. Import it here, then label manually or choose to run Jev.

JEV / PUBLIC BETA

Suggestions you can review

One credit per item. Guests get 10 daily; signed-in users get 20 total, without stacking or rollover. Resets at midnight China time (UTC+8). Network limits are shared; the site allows 200 calls per day. Manual review and exports are free.

Example labels are authored. Import your text, or clear example labels before running.

Stopping does not cancel an already sent request. Failed-item retries send a new request; uncertain network outcomes reuse the original request ID to avoid duplicate charges. Model suggestions still need human confirmation.

Travel mug · 12 authored examplesLabels are authored. Imported tickets need manual classification. Jev is not connected.

Tickets—
High-priority tickets—
Pending review—

Department distribution

Select a department to see the originals. Each ticket has one suggested department.

Original tickets

IDTicketCategoriesStatusAction
Refreshing clears the current data. Save project JSON for lossless restoration; use CSV for spreadsheets.

Import tickets

Paste one review per line or choose a UTF-8 CSV with a review/text column. Up to 500 tickets and 1 MB. Exported review CSV files up to 8 MB can restore labels and review status.

Ticket

Confirm the department

Sign in or create an account

No email is collected. Keep your credentials safe; email recovery is not available during this beta. Credits reset daily and cannot be purchased.

From CSV to reviewable decisions

  1. Import a UTF-8 CSV text or review column. Originals remain in the current browser session.
  2. Choose labels manually, or confirm submission and use beta credits for Jev suggestions.
  3. Inspect each original, correct labels and confirm review; export CSV or save a project JSON.

Decision boundaries

Departments are billing, technical, product and other/unclear. Priority is an input-based suggestion. The workspace does not assign real agents, create tickets or close them.

Model suggestions are not an accuracy guarantee. Existing API smoke tests establish interoperability only; evaluate quality on your own labeled samples. Evaluation and review thresholds