The Early Agent Gets the Worm
summary
Six months after launch the team reports a 4.43 store rating and 91% FAQ deflection by routing common queries to bots, with 51% fully automated, 48% partially automated and under 1% fully manual. Workflowly triage captures reproduction steps and device scope, BI ranks impact to justify fixes, developers ship patches, and ops compensates affected players by crediting missed rewards. Prioritize high-impact blockers early in preproduction and embed community and support into design and release plans.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:26Key metrics in player support
- 2:14Teams beyond support
- 3:38Benefits and challenges
- 4:43Prioritization strategies
- 6:07Real workflow example
- 7:08Early player experience setup
- 8:57Q&A
- 9:19Transparency in fixes
related talks
42mPanel: Increasing the Value of Your Games Through Better Player Support
51mThe subtle art of supporting mature products
58mFrom AI Sceptic to AI Sceptic Who Ships
29mTaste & Craft: A Conversation with Tuomas Artman, CTO Linear & Gergely Orosz, @pragmaticengineer
47mBumpy 12 Months Road to Transform Team of Mercenaries Into Product Minded Team
25mWhat I Learned
42mThe subtle art of supporting mature products
01h 03mHow To Do Kick-Ass Software Development