Every month, a mid-tier studio with 500K+ MAU loses roughly $200K to what we call "preventable support volume." These are tickets that exist not because of bugs or missing features, but because of unclear communication, poor onboarding, confusing UI, or community management gaps.
The anatomy of a preventable ticket
Player submits a ticket: "How do I transfer my account to a new device?" This isn't a bug. It's a documentation gap. If the answer were visible in-game, this ticket wouldn't exist. Multiply this by 2,000 tickets/month at $8 cost-per-resolution (industry average), and you're burning $16K/month on one FAQ.
The compound effect
Preventable tickets don't just cost money directly. They clog queues, increase wait times for real issues, burn out agents, and create a negative support experience for everyone. The indirect cost is 3-5x the direct cost.
The fix isn't more agents
It's fewer reasons to contact support. Every preventable ticket is a product signal. The studios that redirect support data back into product decisions — not as a quarterly report, but as a daily input — are the ones that see their cost-per-player drop by 40-60% within two quarters.