CSAT is strong at 93.9% positive. But the 451 negative responses aren't random — they're concentrated and predictable. 77% of all negatives come from tickets that weren't resolved on first contact (reopened or reassigned). Three hotspots account for most of the damage: Customer Success operating as a routing hub instead of a resolution team (37.5% negative), L3 Developer tickets being closed before the customer confirms the fix (56% reopen rate), and Fin Ops billing queries bouncing between agents who each lack the full context (2× reassignments on negative tickets vs positive ones).
Of 24 surveyed tickets in Customer Success, 9 were negative (37.5%) vs 4.5% org-wide. It's the only group where negatives outnumber positives. Resolution SLA was violated on 62% of tickets. Median resolution: 447 hours — nearly 19 business days — vs 48 hours org-wide.
The PDF shows a clear block of negative responses in the "Violated" SLA bar. Underneath: L3 tickets violate SLA 77% of the time, L4 Bugs 59%. These two categories alone make up the bulk of the violated cohort. L3 tickets average 15 agent replies and 9 customer replies — heavy back-and-forth that's structurally incompatible with current SLA targets.
9.0% negative rate vs 4.5% org average — on tickets that are 99.8% "L1 How To's," the simplest category. The subcategory breakdown tells the story: billing queries requiring cross-team coordination (Invoice Query: 21% negative, Manual Invoice: 25% negative) are being treated as simple L1s when they actually need multiple handoffs.
L3 Developer tickets concentrate in Freshservice (26%), Freshchat (24%), and FreshworksCRM (16%). These are "functionality broken" issues — 57% tagged Major or Critical severity — that need back-and-forth debugging between the agent, the customer, and engineering. They average 15 agent replies and 9 customer replies per ticket.
The problem: agents provide an initial workaround and close the ticket before confirming the underlying issue is fixed. FCR is violated on 93% of L3 tickets. When the customer comes back — and 56% do — the ticket reopens and resolution time doubles.
The contrast is dramatic. L3 tickets that don't reopen: 1.6% negative. Those that reopen once: 11.4%. Twice or more: 18.7%. Negative L3 tickets average 26 agent replies — nearly twice the positive average of 14 — signaling extended, unresolved back-and-forth before the customer gives up.
Customer Success is functioning as a sorting desk for tickets it can't resolve. 79% of CS tickets are L1 How To's, and the dominant theme is Finance Operations — invoice queries, cancellations, upgrade/downgrade requests, and reactivations. These tickets arrive from Fin Ops (141), Support (98), and Freshservice (51), sit in CS while someone figures out where they belong, then 97% of outbound transfers go to Digital Operations (728 of 923).
The tickets don't need CS at all — they need Digital Operations directly. The CS hop adds a median 447 hours of resolution time, spreads tickets across 22 agents who each lack context, and produces 4× the org average in reassignments.
The L1 label masks the real complexity. Invoice Queries average 2.1 agent reassignments and 67% SLA violation. Manual Invoices: 2.1 reassignments, 88% SLA violation. These "simple" tickets bounce between agents because each needs both billing system access and product-specific context — a combination no single agent currently has.
The contrast within Fin Ops is telling: negative tickets average 1.95 reassignments vs 0.82 for positive ones. Same team, same ticket type — the difference is how many hands the ticket passes through.
Add a mandatory 48-hour hold or explicit customer confirmation before closing developer and bug tickets. The workaround-and-close pattern on Freshservice and Freshchat issues is creating 56% reopen rates. L3 tickets that don't reopen already achieve 1.6% negative — the resolution quality is there, the closure process is the failure point. Target: reduce L3 reopen rate from 56% → 30%.
97% of CS outbound transfers are L1 billing/finance tickets going to Digital Operations anyway — invoice queries, cancellations, upgrades. Eliminate the intermediate hop by auto-routing tickets with Finance Operations issue type or billing subcategories directly. For the 390 tickets arriving from Fin Ops and Support, build keyword-based rules that skip CS entirely. Target: reduce CS group reassignments from 1.1 → 0.3, bring negative rate toward the 5% org average.
Invoice Query and Manual Invoice tickets bounce because agents lack the billing + product combo. Designate 2–3 specialists with cross-system access. Also investigate the Portal channel — 25% negative rate suggests self-serve billing tools need improvement. Target: reduce billing reassignments from 2.1 → 0.5.