Skip to content
The Register

Jev Support Inbox Router — Classify Support Tickets

Route supplied support tickets to a fixed queue with urgency and review signals using a buyer-provided TypeSafe Jev key.

Jev Support Inbox Router — Classify Support Tickets returns 12 documented output fields, including state, questions, index, sourceId and ticket. Every field carries a declared type, a written description and an example value. 16 runs are recorded on Apify.

Run it on ApifyPay per result · no subscription
12
Output fields
3
Inputs
16
Runs
2026-10-15
Last run

01 — output

What it returns

Every field the extractor writes to its dataset, with its type, a written description and an example value.

FieldTypeWhat it holdsExample
statestringnullCurrent state of this record in its own lifecycle.
questionsobjectnullQuestions as recorded for this row.
indexstring | number | boolean | array | objectnullPosition of this row within the run.1
sourceIdstring | number | boolean | array | objectnullIdentifier of the input record this row came from.rec_01
ticketstring | number | boolean | array | objectnullTicket as recorded for this row.[]
queuestring | number | boolean | array | objectnullQueue as recorded for this row.[]
urgencystring | number | boolean | array | objectnullHow urgent this row is, in words.[]
humanReviewProbabilitystring | number | boolean | array | objectnullHuman Review Probability as recorded for this row.[]
statusstring | number | boolean | array | objectnullOutcome recorded for this row.ok
minConfidencestring | number | boolean | array | objectnullMin Confidence as recorded for this row.[]
judgmentsstring | number | boolean | array | objectnullThe full structured judgement returned by the model.{"stance":{"choice":"recommended"}}
modelstring | number | boolean | array | objectnullIdentifier of the model that produced the judgement.jev-latest

02 — sample

One record

Assembled from the example values declared on the schema above, not invented at render time.

{
  "state": "",
  "questions": "",
  "index": 1,
  "sourceId": "rec_01",
  "ticket": "[]",
  "queue": "[]",
  "urgency": "[]",
  "humanReviewProbability": "[]"
}

03 — input

What you give it

InputTypeDescription
recordsarrayrequiredRows containing ticket text and an optional source ID.
typesafeApiKeystringoptionalSecret — supply your own value.
maxItemsintegeroptionalHard cap on processed ticket rows.

04 — run

Run Jev Support Inbox Router on your own input

It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.

Open on Apify ↗

05 — questions

Asked before running it

12 of 12 fields described

What does Jev Support Inbox Router — Classify Support Tickets return?
It returns 12 documented output fields: state, questions, index, sourceId, ticket, queue, urgency, humanReviewProbability, status, minConfidence, judgments and model. Each field declares its type, a description of what it holds, and an example value.
What input does Jev Support Inbox Router — Classify Support Tickets require?
records is required. A further 2 inputs are optional. The full input schema, with types and defaults, is below.
Does Jev Support Inbox Router — Classify Support Tickets need an API key or login?
Yes — typesafeApiKey is marked secret and must be supplied by you. Nothing else in the input schema needs credentials.
How do I run Jev Support Inbox Router — Classify Support Tickets?
It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.