What do players contact gaming support about?
Players write in about four things: something they paid for, an account they can't get into, a decision they disagree with and a game that isn't working. Agent can close most of the first and last groups. Account security and enforcement decisions stay with people.
| Conversation type | Can Agent resolve it? | Hand off when | Data Agent needs |
|---|---|---|---|
| Purchase or currency didn't arrive | Yes. Re-grants the item when payment cleared but delivery failed. | Payment can't be found, or the receipt belongs to a different account | Order and receipt IDs, entitlement and inventory records, platform |
| Refund request | Partly. Refunds web store purchases within policy; explains store refund routes. | Outside policy, a parent reporting purchases a child made, or a chargeback already filed | Purchase channel, refund policy, playtime or consumption flags |
| Can't log in or lost 2FA | Partly. Sends the reset link and checks for an auth outage. | Email on the account changed recently, or the player can't reach the email on file | Login history, linked platform IDs, auth service status |
| Hacked or stolen account | No. Locks the account if permitted, then hands off. | Immediately | Recent logins, devices, email and password changes, trades and gifts |
| Ban or suspension appeal | Partly. States the policy category and opens the appeal. | Always, for the decision itself | Enforcement record: category, date, length, appeal status |
| Bug or crash report | Yes, for known issues, with the workaround. | A new issue with no match, or a bug that cost the player progress or items | Known issues list, build version, platform, crash or error code |
| Server outage, lag or matchmaking | Yes. Confirms status and applies your compensation rule. | The player was hit by an outage you haven't declared | Server and region status, incident record, compensation rule |
| Lost progress or items after a rollback | Partly. Restores items within a value limit. | Above the limit, or items traded on to other players | Inventory history, rollback window, item values |
| Harassment, cheating or player report | Partly. Takes the report; never shares the outcome. | Threats of harm, self-harm, sexual content involving a minor, or doxxing | Reporting categories, match or session ID |
| Parent or guardian request | No. Confirms receipt and routes it. | Always | Account age flag, region, request type (purchases, data, deletion) |
Platform matters as much as the question. A player who bought currency on a console or through a mobile app store usually has to ask that store for a refund, so Agent should read the purchase channel before it promises anything.
What does an AI procedure for a missing in-game purchase look like?
Start with missing purchases. The answer lives in your own receipt and entitlement records, the fix is usually a re-grant, and players who paid and got nothing are the ones most likely to file a chargeback.
Example procedure: "I bought currency and it never showed up"
- Confirm the player is signed in through the game or launcher. If not, ask for the player ID and the receipt or order number, and send a sign-in link before changing anything.
- Check the last 7 days for an email change, password reset or new device. If the player says they didn't make the change, lock the account and hand off to Account security as urgent.
- Find the purchase and read where it was made: our web store, Steam, PlayStation, Xbox, Nintendo, the App Store or Google Play.
- Paid and not delivered: re-grant the exact item or currency once, confirm the new balance and log the order ID against the re-grant.
- Payment still pending at the store: say how long that store usually takes and ask the player to restart the game to sync purchases. Give no guaranteed time.
- Delivered but already spent: show where it went from the inventory history. Do not re-grant.
- Refund asked for a direct web store purchase that is unused and inside policy: refund it through Stripe up to $50 per order. Above that, hand off.
- Refund asked for a console or app store purchase: explain that the store handles it and link its refund page.
- Escalate when the player mentions a chargeback, says a child made the purchase, writes in angry for a third time, or mentions a lawyer or regulator.
Example conversation
- Player: bought the 2,800 gem pack 20 min ago on PC, paid, no gems. order 7731-KQ
- Agent: Found it. Your payment for order 7731-KQ went through at 18:42, but the gems didn't reach your account because of a delivery error on our side. I've added the 2,800 gems now. Your balance shows 3,115.
- Player: ok they're there. will this happen again with the battle pass?
- Agent: The error was on one delivery server and the team has fixed it. If anything you buy doesn't arrive, send the order number here and I'll check it straight away.
Before replying, Agent checked security events, the order and the entitlement log. Any mismatch would have gone to a person with those lookups attached.
Write the procedure the way you would brief a new hire. Agent turns each step into a call to your receipt, entitlement and store systems.
What guardrails does an AI agent need in a game?
An AI agent in a game should be generous with status and stingy with power. It can explain, look up and re-grant within limits; it cannot unban, reveal who reported whom or keep talking to a child as if they were an adult.
What Agent must never do
- Ask for secrets. Put passwords, 2FA codes, recovery codes and "log in to my account for me" on the banned phrases list. Agent tells players your staff never ask for them.
- Decide enforcement. Agent reads the enforcement record with read-only permission. It can name the policy category and the appeal route; it cannot lift, shorten or explain the detection behind a ban.
- Disclose other players. No outcome of a report, no names, no account details for anyone other than the person writing in.
- Exceed value limits. Set a cap on currency or item re-grants per conversation and per player per month, and a cap on web store refunds.
- Give advice. No medical, legal or financial advice; those questions go to people.
What triggers an immediate handoff
- Takeover signals: "someone changed my email", unknown trades or gifts, items missing after a login from a new device.
- Safety signals: threats, self-harm, grooming or sexual content involving a minor, doxxing. These go to trust and safety, never into a queue that waits for business hours.
- Money disputes: chargebacks, a parent reporting unauthorized purchases, or repeated charges.
- Escalation language: lawyers, regulators, press or a formal complaint, plus your VIP or creator tiers.
Minors, consent and data
Many players are children. The Entertainment Software Association reports that 83% of US children aged 5 to 12 play video games weekly. In the US, the FTC's COPPA Rule governs personal information collected from children under 13. In the UK, the ICO's Children's code applies to online services likely to be accessed by under-18s. Configure Agent to stop asking for personal details once a player's account is flagged as under your age threshold, and route parent and guardian requests to people who can verify them.
Billing behaviour is also under scrutiny. In its 2022 settlement with Epic Games, the FTC alleged that the company ignored more than one million complaints about unwanted charges and locked the accounts of players who disputed charges with their card issuers. Tell players they are talking to AI, keep the route to a person visible and make refunds easy to ask for.
Every connector permission is explicit and revocable. Aftersales offers a GDPR data processing agreement and hosts data in the US, with SSO on Scale (see security). None of this makes a studio compliant by itself.
Which support channels matter for gaming companies?
The best channel is the one inside the game, because the player is already signed in and Agent knows the platform, build and region before the first message.
- In-game and in-app chat. Identity, platform and build come with the conversation. Put the support entry point in the pause menu, not only on a website.
- Web chat on your support site. For players locked out of the game, which is exactly when they need you.
- Email. Ban appeals, parent requests and anything with attachments such as receipts or screenshots.
- Social DMs. Players report outages on social first. Answer, link the status page and move account issues to a signed-in channel.
- Discord and community forums. These are not Aftersales channels. Pin a link to in-game or web support in your server, and have moderators send account issues there rather than handling them in public threads.
Agent reads intent, platform and item names from the first message in 31 languages, which matters when a global launch opens every region at once.
What systems should a gaming AI agent connect to?
Connect what your player support team already opens in other tabs: the account service, entitlements, store records and server status. Studio systems connect through the Aftersales API or webhooks; confirm specific connectors on a call.
| System | What Agent uses it for | Permission |
|---|---|---|
| Player account and identity service (API) | Player ID, linked platform accounts, age flag, login and device history | Read; lock account |
| Entitlements and inventory (API) | What the player owns, delivery status, item history | Read; re-grant within limits |
| Web store payments, Stripe where you use it | Order status and refunds for direct purchases | Read; refund within limit |
| App store and console store notifications (webhooks) | Refund and revocation events from the stores | Read |
| Enforcement and anti-cheat records (API) | Ban category, length and appeal status, never detection detail | Read only |
| Server status and incident tooling (webhooks) | Outages by region and platform, compensation rules | Read |
| Known issues list (API or Knowledge) | Workarounds for live bugs | Read |
| Jira and Slack, through Workflows | New bug pattern into a Jira issue, outage alert to live ops | Create issue, post message |
| Shopify, for a merch store | Order lookup and replacements for physical merchandise | Read; create replacement |
Apple's App Store, for example, sends your server a notification when it refunds an in-app purchase, so you can revoke the item. Feed those events to Agent and it can explain a missing item that was actually refunded. For direct sales, Steam's own refund policy sets the window, so describe it to Agent in plain language rather than inventing your own.
How much does AI customer service cost for a game studio?
At list prices, an indie studio with 1,500 conversations a month would pay about $740 a month. A live-service game with 12,000 conversations would pay about $6,920, and its launch month at 40,000 conversations about $22,760, with no extra seats. These are Examples with the assumptions shown.
| Line item | Example: indie studio | Example: live-service game | Example: same game, launch month |
|---|---|---|---|
| Conversations per month | 1,500 | 12,000 | 40,000 |
| Assumed Agent resolution rate | 45% | 50% | 55% |
| Seats, billed annually | 3 Starter × $24 = $72 | 10 Growth × $69 = $690 | 10 Growth × $69 = $690 |
| Agent resolutions at $0.99 | 675 = $668 | 6,000 = $5,940 | 22,000 = $21,780 |
| Copilot at $29 per rep | Not added | $290 | $290 |
| Monthly total | $740 | $6,920 | $22,760 |
| Cost per conversation | $0.49 | $0.58 | $0.57 |
List prices checked October 2026. Monthly billing adds 20% to seats.
The launch column is the point: Agent never needs a seat, so a spike costs resolutions rather than temporary hires, and conversations Agent can't help with are free. We assumed less than Aftersales' median of 71% resolved after 90 days because appeals, safety reports and account takeovers go to people by design. See pricing.
How do you roll out an AI agent for player support in 30 days?
Go live a few weeks before a content drop, not on launch day.
- Days 1 to 7. Connect accounts, entitlements, store records and server status read-only. Write procedures for missing purchases, known bugs and outages. Add banned phrases, the AI disclosure line and the under-age flag rule, and build Account security, Appeals, Player safety and Parents queues (see helpdesk setup for gaming companies).
- Days 8 to 14. Switch Agent on in in-game chat for one platform during staffed hours. Read every handoff daily and tighten the takeover check first.
- Days 15 to 21. Turn on re-grants within limits, web chat for locked-out players and email. Use Monitors in Insights to check every conversation for banned phrases and missed safety handoffs.
- Days 22 to 30. Add the other platforms and languages, rehearse an outage with a pre-written compensation rule, and review resolution rate and cost per conversation by intent before the next update ships.