Why do generic helpdesks struggle with player support?
Generic helpdesks treat one email address as one customer and one order as one record. A game has a single player spread across several platform accounts, purchases held by stores you don't control, and decisions you are not allowed to fully explain.
- Identity is fragmented. The same person may play under a Steam ID, a PSN name, an Xbox gamertag and your own account. Reps need the linked IDs on the ticket, or they ask the player to prove who they are three times.
- Someone else owns the refund. Console and mobile purchases are refunded by the store, often without telling you why. Apple, for example, lets players ask Apple Support, use its self-service site or go to their card issuer, and notifies developers afterwards.
- Appeals need evidence and discretion. Enforcement teams must review chat logs or match data without revealing how cheats are detected or who made a report.
- Volume arrives in waves. A patch, a season reset or an outage produces thousands of near-identical tickets within an hour, and a flat first-in, first-out queue buries the hacked account behind them.
- Many players are children. Parents write in about purchases and data, and safety reports need people trained for them around the clock.
- Support can become a billing story. The FTC's case against Epic Games alleged the company ignored more than one million complaints about unwanted charges. Complaint trends belong in reporting, not lost in a closed-ticket archive.
How should a game studio set up its support inbox?
Route by risk first and topic second, and give the risky queues their own clock. Use ticket fields for player ID, linked platform accounts, platform, build version and region so every view can filter on them.
| Queue | What lands there | SLA target (first response) | Owner |
|---|---|---|---|
| Player safety | Threats, self-harm, grooming or child safety concerns, doxxing | 15 minutes, 24/7 | Trust and safety |
| Account security | Hacked accounts, unknown email or password changes, stolen items | 1 hour, 24/7 | Security specialists |
| Purchases and refunds | Missing items, web store refunds, chargebacks, store refund questions | 4 hours | Payments team |
| Parents and privacy | Unauthorized purchases by a child, data access or deletion, age questions | 1 business day | Privacy lead |
| Ban appeals | Suspensions and bans the player disputes | Acknowledge within 1 business day; decide within your published window | Enforcement team |
| Bugs and technical | Crashes, progression blockers, performance, new issues | 1 business day; tag to known issues | Technical support, QA on Lite seats |
| Creators and partners | Streamers, creator program, esports and B2B partners | 4 hours | Partner managers |
| General | How-to, game rules, events, account settings | 1 business day | Tier 1 |
Routing rules worth setting on day one
- Keywords such as "hacked", "someone changed my email" or "stole my skins" route to Account security and jump the queue.
- Any message from an account under your age threshold, or mentioning a child, carries a tag that limits what reps ask for.
- During a declared incident, tickets that match the incident tag merge into one view with a bulk reply, so the rest of the queue keeps moving.
- Bug reports with a new error code create a Jira issue through Workflows; side conversations in Slack bring QA or a producer into the thread.
- Round-robin assignment (Growth and up) spreads appeals evenly so no single reviewer sets the tone.
What should player support reps say in the hardest conversations?
These are the conversations reps rewrite from scratch every time. Adapt them to your policies; placeholders are in braces.
Hacked account, recovery under way
Hi {player_name}, thanks for reporting this quickly. We've secured your account so nobody can sign in, trade or spend while we look into it. Please change the password on the email address linked to your account now. Our security team will review recent activity and contact you from {official_email} within {time}. We'll never ask for your password or a 2FA code, in game, on Discord or anywhere else.
Ban appeal upheld
Hi {player_name}, a member of our enforcement team has reviewed your appeal for the {length} suspension issued on {date}. After checking the evidence, we're keeping the decision in place under our rule on {policy_category}. We can't share detail on how violations are detected. Your account will be available again on {end_date}, and you can read the full rules at {rules_link}.
Refund for a console or app store purchase
Hi {player_name}, I'm sorry the {item} wasn't what you expected. Because you bought it through {store}, the refund has to be requested from {store} directly, and they make the decision: {store_refund_link}. If they approve it, the item will be removed from your account automatically. If the item didn't arrive at all, reply with your receipt and we'll fix that on our side.
Parent reporting purchases a child made
Hi {parent_name}, thank you for letting us know, and I understand this is frustrating. To look into these purchases we need to confirm you are the account holder or the payment owner: {verification_steps}. Once confirmed, we'll review each charge and tell you what we can refund and how to set spending limits on {platform}. Please don't share card numbers or passwords in this conversation.
Known launch issue
Hi {player_name}, thanks for the report. This is a known issue affecting {platform} players since {time}, and the team is working on a fix now. Live updates are at {status_link}. Your progress and purchases are safe. {If compensation applies: Players affected will receive {compensation} automatically once the fix is out.}
Harassment report received
Hi {player_name}, thank you for reporting this. Our safety team will review it, and we take action when our rules are broken. For privacy reasons we can't tell you what happens to another player's account. If you ever feel unsafe or someone threatens you, please also contact local emergency services.
How should a player support team be staffed for launches and seasons?
Player support follows the release calendar more than the business calendar. Plan staffing around launches, patches and seasons, and keep safety and security covered every hour.
Structure
- Tier 1 generalists by language and time zone for how-to, bugs and purchase questions.
- Specialist pods for account security, payments and enforcement appeals, with clear rules for when Tier 1 hands over.
- Trust and safety on call around the clock, with training and wellbeing support for reviewing difficult content.
- Community managers, producers and QA on free Lite seats (20 on Growth, 50 on Scale), so they can comment and approve without a paid seat.
Peaks to plan for
- Launch and early access. Login queues, crashes and missing pre-order items arrive together. Run a launch war room with support, live ops and community in one Slack channel.
- Patches and season resets. New bugs and battle pass or progression questions. Publish patch notes before the queue reads them.
- Outages. Declare the incident, post the status message and tag tickets in bulk.
- Holidays and gift cards. New consoles, redeemed codes and parents setting up accounts for children.
- Evenings, weekends and school holidays. Players write in when they play, so weekday office hours alone miss the busiest windows.
Where does AI help a player support team?
AI takes the repetitive part of a launch week off the team so specialists can spend their time on appeals, hacked accounts and safety reports.
- Copilot drafts replies that cite their sources, so a rep can check a refund window or compensation rule came from current policy. Teams using it on every conversation see a 2.4× faster median reply, by Aftersales' own measure.
- Summaries condense a long appeal or recovery thread into a handover note for the next shift or for enforcement.
- Translation in 31 languages, including right-to-left scripts, lets a single team answer a worldwide launch.
- Monitors in Insights score every conversation rather than a sample and flag banned phrases or missed safety escalations. Helio Energy's quality scores rose 14 points after Monitors replaced sampling.
- Agent handles the routine share, such as missing purchases, known bugs and outage questions, and passes everything else to this inbox. The conversation map and an example procedure are on AI customer service for gaming companies.
Which metrics should gaming support teams track?
Measure player support against the release calendar. Split each metric by platform and queue, and compare launch weeks with launch weeks rather than with quiet months.
| Metric | Formula | Target guidance |
|---|---|---|
| Contact rate | Conversations ÷ daily active players × 1,000 | Falls between launches; a jump after a patch points at a regression |
| Time to secure account | Time from first takeover report to account lock | As short as your security team can make it; review outliers weekly |
| First response, safety queue | Median time from ticket creation to first human reply in Player safety | Report nights and weekends separately |
| Appeal turnaround | Median days from appeal received to decision | Inside the window you publish to players |
| Appeal overturn rate | Appeals overturned ÷ appeals decided | Watch for spikes by rule; a high rate can point at a detection problem |
| Incident share of volume | Tickets tagged to an incident ÷ all tickets in the period | Use it to size the next launch war room |
| Compensation and refund cost per incident | Currency, items and refunds granted ÷ incidents | Set a budget per incident before launch |
| CSAT by queue | Satisfied responses ÷ all responses, per queue | Expect appeals to score lower; compare against their own trend |
| AI resolution rate | Conversations resolved by Agent ÷ all conversations | Track by intent; see the resolution rate guide |
Insights reports cost per conversation as one unit cost covering seats, resolutions and channels. The Events API and CSV export work on every plan, and Scale syncs to Snowflake, BigQuery or Redshift if your player data already lives there.
How do game studios switch helpdesk software?
Studios often start on a general-purpose helpdesk such as Zendesk or Freshdesk, an in-game support SDK, or a shared email inbox, with bug reports in Discord and appeals in a spreadsheet. You can add AI to what you have or move the inbox in stages.
Option 1: keep your helpdesk
Agent can work inside an existing Zendesk, Salesforce Service Cloud or Freshdesk setup with no seats to buy and nothing to migrate, at $0.99 per resolution against a minimum monthly commitment.
Option 2: move to Aftersales Inbox
- Export open and recent tickets, macros and help center articles.
- Map custom fields: player ID, linked platform accounts, platform, build version, region and age flag.
- Rebuild the queues and SLAs from the table above, and connect Slack and Jira.
- Move appeals out of spreadsheets into their own queue so turnaround is measured.
- Switch channels one at a time, starting with email, and avoid doing it in the weeks before a launch.
Most teams finish migration in an afternoon; we run the migration with you on Growth and Scale. Growth ($69 per seat a month, billed annually) adds unlimited team inboxes, round-robin and a multilingual help center; Scale adds SSO and a multi-brand messenger and help center for publishers running several titles. See pricing or our multilingual support software roundup.