TrustedQueue CS2Sign in with Steam
Support

What matters: Get help privately without creating public accusations or exposing evidence.

Submit request
Support

Get help without public accusations

TrustedQueue routes support through the right private workflow. Verification, lobby setup, reports, appeals, and privacy requests are handled without exposing accusations or private evidence publicly.

Route the issuePrivate where needed

Choose the right support path first

Most problems are fastest through the exact product surface that owns them. Use private support for account-specific help, appeals for restrictions, and completed-lobby reports for serious player issues.

Send support request
Support pages

Help, appeals, privacy, and terms from one support hub

Use this page as the support entry point. The cards below separate live help, restriction appeals, privacy information, and platform terms.

Common first questions

Most users need one of these answers first

Start here before sending a support request. These answers cover setup, invites, contact reveal, reports, and appeals without exposing private moderation details.

Check updates
Guide

Why does Steam need to be public?

Steam sign-in verifies identity, but richer stats and game-data checks need Steam profile and Game details visibility set to public.

Open visibility guide
Guide

Do I need FACEIT?

No. FACEIT is optional because not every CS2 player uses it. Linking FACEIT can add verified CS2 skill/Elo and extra trust context when available.

Review FACEIT linking
Action

Where are invites and contact details?

Invites appear in notifications, dashboard, and the lobby hub. Contact details stay hidden until current lobby members pass preflight.

Open lobby hub
Guide

Why can I not report anyone?

Reports are gated behind completed TrustedQueue lobby membership so serious claims stay tied to a real shared platform lobby and private evidence.

Open completed lobbies
Guide

How do appeals work?

Queue restrictions and bans can be appealed privately where policy allows. Reporter identity and private evidence are not shown publicly.

Open appeals
Choose the right path

What to do when a live flow is stuck

Start with the page tied to the issue, then use private support only when the guided path does not clear it. Keep reports and appeals in their protected workflows.

Check status first
Self-service

Steam sign-in or session issue

You signed in, but a protected page still asks for Steam login or redirects unexpectedly.

TrustedQueue never asks for Steam passwords or personal Steam API keys.

Self-service

Verification or stats are limited

Your profile shows limited verification, missing stats, or no FACEIT skill context.

FACEIT is optional. Linking it can strengthen context, but not having FACEIT is allowed.

Self-service

No teammate matches yet

Discovery is empty or filters return very few players.

Small early pools are normal; discovery only shows real eligible accounts.

Self-service

Lobby contact details are hidden

A lobby exists, but invite or contact details are still hidden.

Contact reveal depends on fresh source and platform checks for every lobby member.

Private workflow

You need to report a player

Something happened in a TrustedQueue lobby and you want it reviewed.

Reports, reporter identity, and evidence stay private and are not public profile content.

Private workflow

Queue access is restricted

Your account cannot join queue or lobby flows because of a restriction.

Appeals are reviewed privately and moderation evidence remains protected.

Try this first

Fast fixes for common setup issues

These cover the most common Steam, FACEIT, queue, and lobby problems before you need a private support request.

Check service status

Signed in at the top, but a page asks again

Check service status first, then sign out and sign back in if the session looks stale after a deploy.

Check status

Steam stats look limited

Steam profile and game details need to be public before richer public stats can be pulled reliably.

Open Steam visibility step

Verification has not updated

Use the guided verification page to refresh Steam checks and optional FACEIT context from the server.

Refresh checks

FACEIT is missing

FACEIT is optional. Linking it can improve trust context and show verified CS2 skill/Elo when available.

Open FACEIT linking

No teammate matches yet

Save complete queue preferences and try broader region, language, role, or skill filters while the player pool grows.

Edit preferences

Contact details are hidden

Lobby contact reveal happens only after every member passes fresh Steam, linked FACEIT, and platform account checks.

Review lobbies
Guide

Verification or FACEIT linking

Refresh Steam checks, confirm Steam profile visibility, and optionally link FACEIT for stronger trust and verified CS2 skill context.

Common issues

  • Steam checks show limited because the profile or game details are private.
  • FACEIT is not linked yet, or the FACEIT account cannot be matched confidently.
  • A recent source check failed temporarily and needs a manual refresh later.

Before submitting

  • Open verification and run a fresh Steam check.
  • Confirm your Steam profile and game details are public if you want richer stats.
  • Link FACEIT only if you use FACEIT and want that extra trust context.

Verification labels describe source checks and platform history. They do not promise perfect player safety.

Open verification
Guide

Queue, discovery, or lobby help

Review setup progress, queue preferences, active lobby invites, preflight status, and contact reveal requirements.

Common issues

  • Queue preferences are incomplete or too narrow for the current player pool.
  • A lobby invite is pending, expired, or waiting for the other player.
  • Contact details are hidden because lobby preflight has not passed for every member.

Before submitting

  • Save queue preferences with region, language, mode, and roles.
  • Check dashboard for active lobby invites and setup progress.
  • Run lobby preflight before expecting contact details to reveal.

Lobby safety messages use public-safe reasons and do not expose private reports or moderation notes.

Open dashboard
Private flow

Report a player privately

Reports are only available for players from the same completed TrustedQueue lobby. Serious reports require evidence and go to private moderation.

Common issues

  • The player was not in one of your completed TrustedQueue lobbies.
  • The report category needs stronger detail or evidence before review.
  • Serious claims need private moderation review before they affect account status.

Before submitting

  • Open the completed lobby where the issue happened.
  • Use the structured report flow attached to that lobby.
  • Include match links, round numbers, timestamps, demo links, or other relevant evidence.

Reports are never used as public accusation pages. Reporter identity and evidence stay private.

Open completed lobbies
Private flow

Appeal a restriction

Queue restrictions and bans can be appealed where policy allows. Reporter identity, evidence, and private moderation notes are not shown publicly.

Common issues

  • Queue access is restricted after a moderation action.
  • The public reason is brief because private evidence and reporter identity are protected.
  • An appeal needs the moderation action selected before it can be reviewed.

Before submitting

  • Read the public reason shown on your account or appeal page.
  • Explain what you believe should be reviewed and include any safe supporting context.
  • Avoid asking for reporter identity or private evidence disclosure.

Appeals are reviewed privately and do not reveal protected moderation details.

Open appeals
Private flow

Privacy or data request

Signed-in users can request account data review, correction, export support, or privacy handling through a private admin case.

Common issues

  • You want to review what account data TrustedQueue stores.
  • You need help correcting refreshable public Steam profile data.
  • You want guidance on data export or privacy handling.

Before submitting

  • Open account privacy and check the available self-service actions.
  • Include the specific data area you want reviewed.
  • Do not include passwords, personal Steam API keys, or unrelated private credentials.

Privacy requests are handled privately and API keys are never requested from users.

Open account privacy
Guide

Safety and moderation policy

Read how TrustedQueue handles private reports, manual review, public-safe labels, and evidence without publishing accusation walls.

Common issues

  • You want to understand why reports are private.
  • You want to know which labels can appear publicly.
  • You want to understand why one unverified report does not automatically restrict a player.

Before submitting

  • Read the safety and moderation policy first.
  • Use private support for account-specific questions.
  • Use completed-lobby report flows for player-specific incidents.

TrustedQueue shows public-safe trust labels, not raw risk scores or public accusation feeds.

Read safety policy
Private intake

Send a support request

Use this for account, verification, FACEIT linking, queue, lobby, policy, or bug help. Player reports still need the completed-lobby report flow so evidence and membership checks stay attached.

Do not include passwords, personal Steam API keys, private credentials, or public accusations. SteamID, page name, lobby ID, and public-safe error details are enough to start.

Sign in with Steam to submit private account support. Public visitors can still read the support routes and safety policy.

Recent support requests

This only shows public-safe status context for your own support cases.

No support requests yet.

Submitted support requests will appear here after you sign in and send one.

What support cannot do publicly

TrustedQueue does not publish public accusation pages, raw risk scores, private report history, reporter identity, or moderation evidence. Serious claims are reviewed privately and only confirmed source bans or admin-confirmed platform actions can restrict queue access.

Support | TrustedQueue CS2