Panel: Increasing the Value of Your Games Through Better Player Support
summary
First five minutes determine day-two retention and planning player support up front avoids scrambling. Case studies: custom bots and smart FAQs deflect spikes, one studio scales from zero to 17 agents in 24 hours (24 then 60) while keeping core agents for high-value cases. Stack: Helpshift platform, SDK metadata, Keywords BPO and KantanAI machine translation for nine priority languages. Typical starting model is an 80-hour/month FTE, teams report multimodal automation (some reach >90% automated) and measurable faster resolution.
AI-written summary · about
chapters (9)
- 0:00Player support panel intro
- 4:28Player support impact
- 6:57Scaling support for launches
- 12:31Localizing support globally
- 19:32Efficiency vs cost in support
- 25:35HelpShift and Keywords Studios
- 33:50Human touch in automation
- 35:56Localizing your app
- 38:45Key takeaways
related talks
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
11mThe Early Agent Gets the Worm
52mPanel: Doubling Down on Repeat Players- Moving to Retention as a Focus to Making Money
47mMaintaining development costs while meeting the growing expectations of consumers
42mMaximising Impact with AI: Ethical Strategies for Developing a Top-Rated Game on a Modest Budget
52mLet's Talk About LiveOps
21mIncreasing retention with live game services
29mPanel: The Toxic Content Dilemma – Is In-game Game Chat a Lost Case or Can it be Saved?