A player locked out at 9pm does not open a ticket. They stop playing.
Build agents on Happyusers that read your account, purchase and entitlement systems and get a player moving again, then win back the ones who drift away. In-app, on Discord, or web chat, at whatever hour they actually play.
Players get unstuck mid-session.
Somebody is nine hours into a season with friends waiting in a lobby, and something they paid for is missing. They ask in the game, get the actual reason, and get it fixed — without a ticket, an email thread, or a support window that opens on Monday.
It only says what the account says. No invented refund dates, and no guessing whether a purchase went through.
Your team stops writing the same recovery steps.
Account holds, platform linking, missing entitlements and is-it-just-me questions are the bulk of the queue, and almost none of them need judgement. They get answered from the record, at whatever hour they arrive.
What does reach a person arrives with the account state, the purchase history and the whole thread attached — so nobody opens by asking for a player tag.
What it changes for a studio.
Happyusers reads your account, entitlement and build systems — so a player gets moving again inside the session they are already in, and nobody on your team types out the recovery steps for the four hundredth time.
Unstuck without leaving the game
Account holds, two-factor resets and platform linking handled in-app, at the hour people actually play.
Purchases that actually arrive
A failed charge, missing currency, or something bought on another platform — checked against the transaction and granted rather than escalated.
Progress restored, not apologised for
Lost saves, rewards that never granted and inventory missing after a reinstall, checked against the progression record.
Known issues, said out loud
When it is a live incident and not the player, they get told. The same reports group into one thing for your build team to fix.
Any title
Live service, premium or free-to-play, on PC, console or mobile.
Where players already are
In-app, Discord, web chat and email, kept as one thread per player.
One player record
Account, purchases and progression together, so nobody explains themselves twice.
The questions that decide whether a player comes back.
Almost none of these need a person. They need somebody to read the account, the purchase or the entitlement and say plainly what happened.
Account and access
Purchases and entitlements
Progression and rewards
Builds and connection
A person joins the same thread, and the agent steps back.
Appeals and anything touching a player's safety are not decided by a lookup. The conversation stays where it is, and the person arriving has already read it.
It answers from your systems, not from a script.
Every answer above already exists somewhere. Happyusers reads it and states it, and can be traced back to the record it came from.
Account and identity
Status, security holds, linked platforms and login history for that player.
Hold · new-region login · 12 AugPurchases and entitlements
What was bought, on which platform, and what was actually granted.
Season Pass S12 · PSN · grantedPlayer progression
Level, season progress, inventory and what carries across devices.
Level 42 · S12 · 3 devicesBuild and incident status
Known issues and live incidents, so a player is told it is not just them.
Live incident · login queueModeration record
Sanction status and where an appeal has reached, without guessing.
2 sanctions · both upheldAppeals and player safety go to a person.
Ban appeals, refunds outside policy, and any report involving harassment or a player's safety are handed to a named human immediately, with the full thread and account history attached. Happyusers does not improvise on those.
Players churn quietly.
We work with a small number of studios at a time, and we help you launch your first agent directly.