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.
{
"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