Support ticket triage

Use case · Support

← All use cases
⚑

Support ticket triage

Support

Categorize, prioritize (P1-P4), detect churn/security signals, and route every inbound ticket the moment it lands.

The routing recipe
Job typeClassification / routingPolicyFastest that passesConstraintsgroq
routes to
GPT-OSS 20B groq
groq:openai/gpt-oss-20b
89.3
match score
84.6
task fit
66.4
cost
96.4
speed
Why this model from benchmarks & capabilities
  • "Classification / routing" leans hardest on instruction; GPT-OSS 20B scores 78/100 there — #37 of 54.
  • Strength on this class of work shows up on IFEval, MMLU (zero-shot), where OpenAI (open-weight) models are competitive.
  • Cost: ~$0.244/Mtok blended ($0.07 in / $0.30 out). Speed: ~1000 tok/s on Groq LPU.
  • Chosen over Llama 3.1 8B Instant for higher task-fit (84.6 vs 75.6) & faster.
Capability the job needsWeightGPT-OSS 20BCatalog rank
instruction0.9078#37 of 54
speed0.9096#2 of 54
knowledge0.3070#40 of 54
Relevant benchmarksIFEval MMLU (zero-shot) EconomicsCost: ~$0.244/Mtok blended ($0.07 in / $0.30 out).
Speed: ~1000 tok/s on Groq LPU.
vs runner-upChosen over Llama 3.1 8B Instant for higher task-fit (84.6 vs 75.6) & faster. (Llama 3.1 8B Instant, score 88.3)
Example result
Sample input ▾
Ticket: 'Our auditor needs our evidence export TODAY and the download button 500s. We're considering other tools if this isn't fixed.'
category: bug — evidence export (500) priority: P1 team: Eng (+ Success follow-up) churn_risk: high reason: Time-critical audit blocker + explicit switch threat; page Eng and have Success reach out within the hour.
Test it on your own data
Sign in to continue

LLM Switchboard is private — sign in with Authlee to access the control room.

Sign in with Authlee
← Back to home