Skip to content

Execution & RCA · Easy

Customer support tickets doubled the week after a feature release. What steps would you take?

Short answer

Read a sample of tickets first to see what users are actually saying, then categorise them: bugs, confusion about the change, or unrelated issues. Fix urgent bugs immediately and roll back if users are blocked. For confusion, improve in-app guidance or copy. Close the loop with support, and track whether ticket volume returns to normal.

Detailed answer

Framework

  1. Read raw tickets before looking at dashboards.
  2. Categorise by root cause.
  3. Triage by severity: is anyone blocked, losing money or data?
  4. Act per category.
  5. Follow up and prevent recurrence.

Worked example

A project-management tool redesigned its task view.

Reading a sample of tickets shows:

  • Many users cannot find where the "due date" field moved.
  • Some report that tasks created on mobile are missing a field.
  • A few unrelated billing questions.

Categories and actions:

  • Discoverability (confusion): add an in-product hint pointing to the new location, update help articles and give support a short reply template.
  • Bug (missing field on mobile): high priority because data is affected; fix and confirm no data was lost.
  • Unrelated: route normally.

Measure: tickets per thousand active users by category, day by day. The discoverability category should fall within days of the hint; if not, the design itself may need to change.

Prevention: for future releases, run a small usability test on changed navigation, prepare support in advance and roll out gradually so issues show up in a smaller group first.

Common pitfalls

  • Treating all tickets as one problem.
  • Explaining confusion away as "users will get used to it" without evidence.
  • Not thanking or updating the support team, who are your best early-warning system.