CustomQueue

Built for smarter players

Competitive match insight for players who want more structure, clearer feedback, and less noise around the games they already enjoy with friends.

Public routes stay read-only. Member routes such as `Member Matches` and `Member Login` require existing access.

Public Contact

Contact

A stable contact route for CustomQueue staging, review, and product-scope questions without implying open public player support.

Current state

The internal workflow already operates privately. These public routes exist so reviewers can understand the product without logging in first.

Riot scope

Standard API lookup exists where useful. Riot account linking and Tournament API creation are intentionally outside this public surface.

Support email

Use the configured public support address for reviewer questions, policy clarifications, staging feedback, or access coordination.

info@customqueue.com

Recommended topics: staging/demo access, reviewer questions, current feature scope, Riot integration limits, and public-shell corrections.

Current response scope

This is a protected product contact channel, not a public player-support desk.

Questions should focus on staging/demo access, product scope, policy pages, and submission-readiness review.

The current application keeps its match operations inside a protected workspace. No public Riot onboarding flow or live Riot Tournament API support exists in this phase.

Reviewers who only need product understanding should usually start with the public player-access and public leaderboard routes before requesting internal workflow access.

Recommended review routes

These routes make the public surface easier to evaluate during a future staging deployment.

Start with the root landing page for scope, product language, and Riot-scope limits.

Use `/privacy`, `/terms`, and `/contact` for policy and communication review.

Use `/riot.txt` only as a staging verification placeholder until Riot requests a real token for customqueue.com.

First staging smoke test

A small reviewer-style pass helps confirm the deployment is coherent before sharing it.

Check that the public support email is correct everywhere it appears.

Check that the landing page, legal pages, and `riot.txt` all resolve under the intended staging hostname.

Check that `Leaderboard`, `Member Matches`, and `Member Login` still route correctly from the public shell.