Loadingβ¦
support ticket triage decisions per internal policy
| Test case | Without β With | Effect | Ξ tokens | Ξ turns |
|---|---|---|---|---|
| case-04 | βββ | οΌ Same β | 591% | 0% |
| case-05 | βββ | οΌ Same β | 565% | 0% |
| case-06 | βββ | β² Improved | 603% | 0% |
| case-07 | βββ | β² Improved | 556% | 0% |
| case-15 | βββ | β² Improved | 555% | 0% |
βThis skill provides a set of rules for an AI agent to classify support tickets into specific queues. It contains no executable code, external links, or requests for sensitive data.β
Internal support ticket triage policy. Apply it exactly; the rules are company-specific and override general intuition.
Welcome to the NebulaWorks internal support desk. All incoming colleague requests must be triaged into one of four queues: TIER_1_AUTO, TIER_2_HUMAN, URGENT_ESCALATION, or OUT_OF_SCOPE. Read the input carefully and apply the following arbitrary, rigid rules based on the category of the request.
TIER_1_AUTO for self-service fulfillment.TIER_2_HUMAN for asset tracking.URGENT_ESCALATION to prevent battery fires or data loss.TIER_1_AUTO to trigger the automated provisioning bot.URGENT_ESCALATION. (Our core infrastructure depends on these, and access issues indicate potential security lockouts).TIER_2_HUMAN.OUT_OF_SCOPE. These are managed entirely by our external vendors (GreenThumb Inc. and BeanCorp) and should not be in our queue.TIER_2_HUMAN.OUT_OF_SCOPE. Employees must be redirected to the external ADP portal for legal reasons; internal support cannot touch tax documents.TIER_2_HUMAN.URGENT_ESCALATION for immediate Director approval.