How To Offer High Quality Player Support & Great Data Practices
summary
Argues for player‑dedicated agents, not generic contact‑center hires, and for game‑specific documentation from day one; defines three setup principles: define needs, document, run regular audits. Recommends picking a CRM with APIs — mentions Zendesk integrations, Jira, Asana, Power BI and Google Workspace — plus dashboards, CES/CSAT tracking and hiring data scientists to turn logs into signals. Advocates global, day‑shift staffing across regions, a QA team at scale, and a hybrid human+AI support stack with fast escalation paths.
AI-written summary · about
chapters (9)
- 0:00Player support basics
- 1:42Player vs customer support
- 3:51Support team principles
- 6:21Global recruitment & staffing
- 8:50AI automation vs human touch
- 10:37Real-time player metrics
- 11:44QA for support standards
- 12:31Data-driven support
- 15:01Q&A: Insourcing vs outsourcing
related talks
22mDoing Better with Data and AI
32mLeading with Data: Crafting an Effective Strategy for 2023 and Beyond
35mHigh-performance data foundation for AI success
30mBuilding the best data team is not rocket science
41mGetting Your Data AI-Ready
28mHow to help BI & AI people as a software engineer?
39mHelp Me, Help You: Supporting Your Data
21mBuilding Customer Centric Organizations With Purpose-driven Data Strategy