What 200 Support Tickets Reveal About Your Help Center
How seven cluster categories drive 80% of DTC support tickets
The CX dashboard says you're winning. First response time is down quarter over quarter; CSAT holds. And yet ticket volume keeps climbing, the agents look stretched, and the headcount conversation gets harder. The dashboard isn't lying — it's measuring the wrong layer. The ticket pattern is.
The Cost-Center Illusion
Most DTC CX programs optimize the wrong layer. FRT moves; CSAT holds; deflection rates read reasonable; and underneath, the team writes the same answers over and over while volume grows. The dashboard rewards speed, not source.
About 80% of ecommerce support volume traces back to the same recurring categories — shipping status, order changes, returns and exchanges, sizing, refund timing, discounts and stock, payment friction, and policy ambiguity (Gorgias industry data). The agents handle it. The categories don't shrink.
Why per-ticket SLA is the wrong primary metric at scale
Per-ticket SLA tells you how fast your team is responding. It tells you nothing about whether the next ticket should have existed at all. At sub-$30M DTC scale, this gap is where most CX budgets quietly underperform.
The "responding to symptoms" pattern hiding inside healthy dashboards
A "where is my order" ticket gets answered. Twelve hours later, another "where is my order" ticket gets answered. By the end of the month, the team has written 800 versions of the same explanation that could have lived in one tweaked shipping confirmation email. CX leads who've run the pattern-detection workflow usually spot this kind of cluster in the first ten minutes.
The metric you actually want to move: contact-per-order
Contact-per-order is the wallet metric. Drive it down by half a point and your support cost structure changes shape. FRT can be perfect while contact-per-order quietly grows — meaning your team is getting faster at answering questions that shouldn't exist in the first place.
What 90 Days of Tickets Actually Reveal
Run a clustering pass on 90 days of tickets — not by tag, by meaning — and the same 5–7 questions account for the majority of volume. The volume isn't random. It's structured.
Customers describe the same problem in dozens of different ways. — Cobbai CX analytics, on root cause analysis from ticket data
The 5–7 cluster categories most DTC brands find when they look
Shipping anomalies (lost, label-only, delivered-but-missing). Returns process friction (mobile UX, where-to-send, refund timing). Sizing or fit uncertainty (apparel, footwear, beauty). Refund timing transparency. Discount and stock confusion. Payment errors. Policy ambiguity. Most brands find five of these dominating; a few find seven.
Why semantic clustering beats keyword search every time
"Where is my order" and "tracking says delivered but nothing here" name the same underlying issue. Keyword tags split them; semantic grouping merges them. That difference is the gap between "the inbox is noisy" and "we have five problems."
Each cluster traces to one or two upstream fixes
A shipping-anomaly cluster maps to your confirmation email cadence and tracking-page copy. A sizing-uncertainty cluster maps to your size chart and PDP photo set. A refund-timing cluster maps to one paragraph in your post-return email. Bell Canada's published RCA program reduced calls per event by 16% and churn by 6% by addressing root-cause clusters this way; the logic ports cleanly to DTC support.
What the agent ships when you run it
A 3-item CX priority list, ranked by ticket volume. Each cluster carries verbatim quote samples for verification, a root-cause hypothesis, a draft FAQ entry, a draft macro, and a TRUE/FALSE flag for ops vs CX ownership. Plain text — paste straight into Gorgias macros, Zendesk help center articles, or your PDP FAQ.
One paste. One run. One priority list. Once a month — first Monday, after every launch, before every CX headcount conversation. Clusters that point at upstream fixes are headcount conversations you don't need to have.