Jev Support Inbox Router

Route supplied support tickets into fixed queues with an urgency signal, and flag the ones a human should read rather than route.

It is part of the Jev family: narrow, typed judgements on records you supply, with the code owning everything deterministic and the model owning only the judgement. Bring a TypeSafe API key as a secret input for live judgements.

What it does

• Assigns each supplied ticket to a fixed queue you define.
• Scores urgency.
• Returns a human-review probability per ticket.
• Flags low-confidence judgements for review.

What it does not do

Scoping this honestly is the point of the family, so it is stated plainly:

• It never reads your inbox.
• It never sends a reply.
• It does not connect to your helpdesk — you supply the tickets.

Output fields

Field	Description
index	Position of this row within the run.
sourceId	Your identifier for the ticket.
ticket	The ticket as it was judged.
queue	The queue this ticket was routed to.
urgency	Urgency score for this ticket.
humanReviewProbability	Probability this ticket needs a human.
status	Outcome for this row.
minConfidence	The weakest judgement confidence behind this row.
judgments	The full structured judgement.
model	Identifier of the model used.

Sample output

{
  "index": 1,
  "sourceId": "tkt_5510",
  "ticket": {
    "subject": "Charged twice"
  },
  "queue": "billing",
  "urgency": 0.91,
  "humanReviewProbability": 0.55,
  "status": "completed",
  "minConfidence": 0.83,
  "model": "jev-latest"
}

How it works

Each supplied record is turned into a question set and sent to the TypeSafe Jev model, which answers with a choice, a score, or a probability. Those answers are mapped onto fixed output fields, and every row carries the confidence of the judgements behind it.

status reports the outcome per row. When the minimum confidence falls below your threshold, or the model's own uncertainty is high, the row is flagged for review rather than presented as a settled answer. minConfidence records the weakest judgement that produced the row, so you can see how close it was.

Safe mode. With no TypeSafe key the Actor sends nothing upstream and returns a single row with status: "no_api_key" — a successful run that tells you exactly what to add, never a failed one.

Pricing

Pay per event: you are charged per result written to the dataset, plus the near-zero start event. In safe mode no judgements are produced, so the run is effectively free. Bring your own TypeSafe key; you pay TypeSafe separately for the model calls.

FAQ

Does it need a TypeSafe key? For real judgements, yes — add it as a secret input. Without one it runs in safe mode and returns no_api_key instead of guessing.

Does it call any other service? No. It reads your supplied records and calls the Jev model. It does not fetch, scrape, crawl or contact anything.

What does review mean? The judgement was not confident enough to stand on its own. Treat those rows as needing a human, not as answers.

Can I tune the threshold? Yes. Raise the confidence threshold to get fewer, more certain results; lower it to see more rows with more of them flagged for review.

Is the output deterministic? The mapping and the fields are fixed. The model's judgement is probabilistic, which is why every row carries a confidence and why low-confidence rows are flagged rather than hidden.

Use cases

• Triaging a support backlog.
• Routing tickets consistently instead of by whoever reads them first.
• Finding the tickets that need a person, not a queue.

Related Actors

• Jev Lead Qualification Scorer
• Jev Review Intelligence

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• Jev Support Inbox Router declares all 12 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of Jev Support Inbox Router include state, questions, index, sourceId, ticket and queue.
• Jev Support Inbox Router needs no API key, login or account of any kind before its first run.
• Every one of Jev Support Inbox Router's 3 inputs is optional, so it runs with no configuration at all.
• Jev Support Inbox Router documents state as: Current state of this record in its own lifecycle.
• Every number published about Jev Support Inbox Router is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• Jev Support Inbox Router is filed under ai and business so that it is found by the people looking for that job, not by its internal name.

Limitations

• Jev Support Inbox Router reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.