A Steam Support request gets understood when it answers three questions in plain words: which account this is, what happened and when, and what proof you have that the account is yours. Keep it to one request, add everything to that same thread, and never paste a password or a full card number. Steam Support replies inside your request, and how long that takes varies.
Why the way you write it matters
The person reading your request has not seen your screen, does not know your history with the account, and handles many requests about similar problems. A message like "my account got hacked please help" gives them almost nothing to act on, so the first reply is usually a request for the details you could have included from the start. A clear first message removes that extra round.
It also matters where you write. Steam says it asks for card or product-code details only when you contacted Steam Support through its own support system, and Steam says its staff never contact you through chat, including Steam Chat or Discord; the only way to talk to Steam Support about your account is the Steam Support site. Open your request on help.steampowered.com, signed in if you can, and ignore anyone in chat who says they are from Support.
What to include as the owner
Think of the request as a short, factual report. The parts that help most:
- Your account name. This is the login name you sign in with, not the profile name friends see. If you are not sure, say which email address the account was created with.
- What happened, in order, with dates. For example: when you last signed in normally, when you noticed something wrong, and what changed (password, email, phone, Steam Guard, items, purchases). Approximate dates are fine; say so when you are estimating.
- What you have already tried. A password reset, a recovery code, a lock from a notification email. This stops Support from suggesting steps you have already done.
- What you are asking for. Access back, a Steam Guard authenticator removed, an explanation of a lock notice. One clear request reads better than a list of every worry.
Where proof fits in
Proof tells Support the account is yours: payment details already used on the account, or a product code activated on it. For a card, give only the last four digits. Our guide on what Steam Support accepts as proof of ownership covers each method, including why the oldest proof carries the most weight.
How to lay out the timeline
A short dated list is easier to follow than a paragraph. Put one event per line, oldest first, and mark estimates as estimates:
- Last normal sign-in: around 3 March.
- 5 March: email saying the account email was changed, which you did not do.
- 5 March: password reset tried, the code no longer reaches you.
The dates above are only an illustration of the format. Keep the story to what you saw yourself, not guesses about who did it.
How to label attachments
Give each file a plain name that says what it is, such as "card statement showing Steam purchase" or "photo of key card with ticket number", and mention each one in your message so the reader knows what to look for. Crop screenshots to the relevant part, and cover anything that is not needed, such as the middle digits of a card or unrelated transactions.
What never to include
- Your password, old or new. Support does not need it to verify you.
- Steam Guard codes or your recovery code. These are for signing in, not for tickets.
- The full card number. Steam's proof of ownership article says in bold not to provide it. The last four digits are what it asks for.
- Other people's details, such as a scammer's address or personal data you dug up. Report the account through the official tools and leave the rest to Steam and, for theft, to local police or your national fraud reporting service.
Before you send proof, make sure the email linked to Steam is secure. Steam warns that if your computer or email is compromised, someone else can get hold of strong proof, including proof you sent in an earlier ticket, which makes recovery much harder.
One request, one thread
It is tempting to open a new request every day when nothing seems to happen. That usually works against you: the same case ends up split across several threads, and each new one starts without the history of the others. Keep one request per problem.
When you remember a detail, find another receipt, or Support asks a question, reply in that same thread. Open your existing request on help.steampowered.com while signed in and add to it there. Steam's instructions for proof also say to add it to your existing ticket rather than starting over.
If your account is under a lock placed by Support, the same rule applies. The page on a Steam account locked by Support explains what the lock notice means and why making a new account does not solve it.
Realistic expectations
- Timing varies. Steam does not publish a response time, and nobody outside Steam can promise one. Contested ownership cases, Steam says, take significant time.
- Replies come inside your request. Check the thread and the email linked to your account, including spam.
- Support decides. A well-written request helps Support understand your case; it does not guarantee a particular outcome. Some things, such as a VAC ban applied while someone else was using the account, stay in place regardless of who was playing.
- No one can speed it up for a fee. Anyone offering to "push" your ticket or recover the account for money is not part of Steam Support.
What to do next
If someone took over your account, start with the order of steps in what to do when your Steam account is hacked: secure the email, try the official reset, then open one request with your proof. Gather that proof using the proof of ownership guide, write the request with the account name, dates and what you are asking for, and keep every later detail in the same thread.