Skip to content
All Jev use cases

Prompt pack

Jev ticket triage prompts

Prompts for sorting incoming customer messages: route a message to the right request type, catch requests your team does not handle, and spot customers who are angry or confused. Each Jev ticket triage prompt was run on real Jev against human labels from public datasets, and the agreement rate is listed next to it.

Jev ticket triage sorts a customer message before a person opens it. It can route a message to a request type you supply, catch a request your team does not handle, or spot a writer who sounds angry or confused. Use Jev ticket triage for a route, a queue jump, or a refusal. It does not write the reply.

The weak line in Jev ticket triage is Spot a confused customer: 73% on 40 examples. Agreement is the share of examples where Jev ticket triage matched the human label. When Jev ticket triage is unsure, leave it in the normal queue or with a person. Replay Jev ticket triage on your own tickets before you lock the route. This site is unofficial. TypeSafe does not run it. You call Jev with your own key. Jev ticket triage here is the prompt and the test result.

How we tested these Jev ticket triage prompts

Model
typesafe/jev-1.14-20261014
Tested on
Sent as
Decisions API request (state + questions) → typesafe/jev-1.14, served by TypeSafe

We ran these tests ourselves. TheJevAI is an unofficial, independent site and is not affiliated with TypeSafe.

Free Jev ticket triage prompts

Copy a request, put your own data where the placeholders in double braces are, and send it. To send it to TypeSafe's API, add "model": "jev-1.14.0" to the request body.

Download the free prompts (JSON)

Jev ticket triage: Route a message to one of your request types

This Jev ticket triage prompt picks which of your request types a customer message belongs to, from a list you supply.

Request body
{
  "state": {
    "message": "{{message}}"
  },
  "questions": {
    "request_type": {
      "type": "choice",
      "instructions": "Which request type best matches what the customer wants in `message`?",
      "criteria": {
        "card_arrival": "An ordered card has not arrived yet.",
        "lost_or_stolen_card": "The card was lost or stolen.",
        "card_payment_not_recognised": "Does not recognise a card payment.",
        "transaction_charged_twice": "Was charged twice for the same transaction.",
        "request_refund": "Wants a refund.",
        "transfer_not_received_by_recipient": "The recipient has not received a transfer.",
        "exchange_rate": "Asks what exchange rate is used.",
        "top_up_failed": "A top-up failed.",
        "terminate_account": "Wants to close the account.",
        "passcode_forgotten": "Forgot the app passcode."
      }
    }
  }
}

Put the customer's message in `message`, then replace the ten options with your own request types: a short id as the key and a one-line description as the value. Jev routed all 40 test messages correctly, but these ten types are clearly different from each other. Types that overlap, such as a refund request and a double charge, need descriptions that spell out the difference. Add an `other` option if some messages fit none of them.

100% agreement (40 of 40): messages where Jev ticket triage picks the type annotators labeled

Dataset: Banking77 (PolyAI)License: CC BY 4.0

Jev ticket triage: Spot an angry or annoyed customer

Use this Jev ticket triage prompt to say whether the writer of a message sounds angry or annoyed, so the message can jump the queue.

78% agreement (31 of 40): anger or annoyance, agreed labels, Jev ticket triage yes from 0.5Dataset: GoEmotions (Google Research)

Jev ticket triage: Catch requests you do not handle

A Jev ticket triage prompt says whether a message asks for something outside the list of request types your service supports.

95% agreement (38 of 40): jev ticket triage matches out of scope or one of 150 intentsDataset: CLINC150 (oos-eval)

Jev ticket triage FAQ