This FAQ is the page we point you to when a question pops up mid-session. We've gathered the things you actually ask us — about account setup, the...
We wrote this FAQ the way we'd answer you in chat. The questions are grouped so you can scan: account questions sit near the top, then lobby behaviour, then the payment chip row, then how our support team picks up. If a question here doesn't match yours exactly, head to the support card lower on the page and we'll pick it up
directly. Treat the chips below as quick context for the payment items you'll see referenced throughout the answers.
Three quick anchors before you scroll. Each one points to the kind of question we answer further down, so you know which block to read first.
Sometimes a question is too specific for a general answer. These are the three paths we keep open so you can reach a human quickly.
This FAQ is maintained by the same team that runs the lobby, not a third-party writer.
Every answer here is drafted by our own product and support leads, then checked against the live lobby so the wording matches what you actually see on screen.
When we change a lobby behaviour or adjust a chip, the matching FAQ entry is rewritten in the same sprint so the answer never drifts from the product.
We avoid jargon. If a term has to appear, we explain it in the same answer so you're not bounced off to a glossary mid-question.
The FAQ reads the same on phone and desktop. No mobile-only shortcuts, no desktop-only footnotes — one answer set for both sessions.
Where an answer depends on regional access we say so plainly, using supported-regions wording rather than vague phrasing that leaves you guessing.
Each block ends with a path back to a human. The FAQ is a starting point, not a wall — if it falls short, support is one tap away.
A short side-by-side so you know what to expect from this page versus a typical help centre.
These are the visible elements our FAQ keeps pointing back to. Knowing them upfront makes the answers below easier to follow.