Team
Send the message to an approved team or queue without inventing new labels.
Give every incoming message a route, a priority and a clear answer to the question: does a person need to step in?
Write the labels
Score impact
Watch repetition
The queue
The useful output is not a paragraph. It is a small set of fields your help desk can act on immediately.
Send the message to an approved team or queue without inventing new labels.
Use your own impact and urgency levels instead of relying on tone alone.
Flag churn, money, safety or repeated-contact signals for a human.
Measurement
Review false routes, missed escalations and queue imbalance before changing the threshold.
Write the labels
Describe each team and queue with examples that match your operation.
Score impact
Separate time pressure from the business impact of waiting.
Watch repetition
Repeated contacts and unresolved issues can change the escalation decision.
Keep a review path
Unknown or high-risk cases should not disappear into automation.
Triage a support ticket
Review false routes, missed escalations and queue imbalance before changing the threshold.
{
"state": "Charged twice again. I already wrote last month and nobody replied.",
"questions": {
"team": { "type": "choice", "instructions": "Which team should handle this?", "criteria": { "billing": "payments and refunds", "technical": "product bugs", "account": "access and profile" } },
"priority": { "type": "score", "instructions": "How urgent is this?", "criteria": ["routine", "today", "urgent", "critical"] },
"escalate": { "type": "noul", "instructions": "Should a human review this now?" }
}
}FAQ
Yes. Define the options and their descriptions in the request instead of training a fixed label set.
It should not. Include business impact, deadlines, account history and policy in the state.
Your application can apply the typed result. Keep a review path for uncertain or high-impact tickets.