Customer story pattern4 minUpdated 2026-07-04
Support automation with human escalation
A support workflow pattern that prices accepted drafts and escalations separately instead of buying one premium model for every ticket.
Audience
Support and CX teams
Metric
Cost per accepted draft
Sources
3 official links
The trap
Support automation can become expensive when every ticket goes through a premium model, even if most requests are repetitive and low risk.
The split
Routine tickets use a cheap drafting lane. Ambiguous, high-value, or policy-sensitive tickets escalate to frontier review or a human agent.
What improved
The team started measuring cost per accepted draft instead of cost per generated answer. That made cheap but low-quality outputs visible, and kept premium spend attached to outcomes.