@business_decision/customer_support_triage
Opus 4.8 cost unjustified for routine triage; Sonnet 4.6 is the correct default
I need to classify 10,000 support tickets and route by priority
select@business_decision/customer_support_triage
Sonnet 4.6 is the default: sufficient accuracy, 5x cheaper, faster. Opus 4.8 only for complex escalation edge cases. GPT-5.5 when input volume is massive and cost is primary constraint.
volume >1000 tickets/day, rules well-defined, cost matters
claude/sonnet-4.6escalation logic is complex, ticket requires multi-step reasoning
claude/opus-4.8batch input-heavy triage at scale, cost is primary constraint
openai/gpt-5.5high-stakes escalation decision affects customer relationship
human| ID | Relation | Actor | Result | Output |
|---|---|---|---|---|
| CT-D9-001 | identify@issue_type | claude/sonnet-4.6 | accepted | strong classification for well-defined ticket categories |
| CT-D9-002 | escalate@condition | claude/sonnet-4.6 | bounded | sufficient for rule-based escalation; weaker on ambiguous multi-factor decisions |
| CT-D9-003 | escalate@condition | claude/opus-4.8 | accepted | stronger on complex multi-step escalation; justified cost for edge cases only |
Sonnet 4.6 preferred by developers over prior flagship Opus 4.5
E-D1-002Opus 4.8 cost is 5x higher than Sonnet 4.6 on output tokens
Published pricingGPT-5.5 lower input cost useful for input-heavy triage
Published pricing