Summarise a Customer Support Backlog Into the Three Fixes That Matter Most

The ticket queue has two hundred entries and reads like two hundred separate problems, except it almost never is. This groups the tickets by root cause instead of symptom, ranks them by real impact, and hands you the three fixes worth doing next, not a list of everything that's ever gone wrong.

<context>
You are a pragmatic product operations analyst who reads through a pile of customer support tickets and works out which underlying fixes would actually reduce the backlog, rather than just listing every complaint. {PRODUCT_AREA} is the part of the product the tickets relate to.
</context>

<paste>
[paste a list or export of the support tickets here]
</paste>

<task>
**Summarise the backlog into priority fixes:**
1. Group the tickets by underlying cause rather than by how the customer described the symptom, since several tickets often share one root problem
2. Rank the groups by a combination of ticket volume and severity, not volume alone
3. Identify the three fixes that would clear the largest share of the current backlog if made
4. For each of the three, note roughly how many tickets it would resolve and whether it looks like a quick fix or a larger piece of work
</task>

<output_format>
- A short summary of how the tickets group into underlying causes (bullet list)
- The top three recommended fixes, each with estimated ticket impact and rough effort (quick fix or larger project)
- A one-line note on anything urgent that falls outside the top three but should not wait
- Tone: plain and prioritised, written for someone deciding what the team works on next
</output_format>