Getting Started
First-day checklist for operating Phoenix Prediction
Use this page when your team is opening Phoenix Prediction admin for the first time.
The goal is not to create many markets immediately. The goal is to understand what you control, review the live experience, and publish only markets your team can confidently resolve.
1. Confirm Your Access
Before operating markets, confirm:
- You can sign in to the correct operator organization.
- Your role allows the workflows you are responsible for.
- You know which environment is production and which is for review.
- You know who can approve market launches and resolutions.
- You know where support and finance teams review settlement questions.
2. Learn the Main Areas
| Area | What it is for |
|---|---|
| Markets | One-off market review, publishing, closing, voiding, and resolution |
| Series | Recurring market schedules created from reusable templates |
| Player experience | Configuration that controls what players see |
| Comments | Moderation queue and market discussion review |
| Stats | Volume, wagers, players, GGR, and settlement health |
| Admin users | Operator team access and permissions |
3. Review the Player Experience
Before creating markets, open the player-facing experience and check:
- The operator brand, theme, and support links are correct.
- The visible categories match the operator launch plan.
- Empty states make sense if there are no live markets yet.
- Logged-out and logged-in players see the expected actions.
- Mobile layout is usable for the main player flow.
4. Create One Review Market First
Start with one low-risk market in a review environment.
Use it to confirm:
- The title and outcomes are clear.
- The market appears in the expected category or topic.
- Trading opens and closes at the expected time.
- The resolution rule is specific enough for support.
- Settlement status is visible after resolution.
5. Establish a Daily Routine
At minimum, operators should check:
- Markets going live today
- Markets closing soon
- Markets waiting for resolution
- High-volume or one-sided markets
- Settlement warnings
- Player comments that need moderation
6. Know When to Escalate
Escalate to the technical or platform team when:
- Markets are not visible even though admin settings look correct.
- Many players cannot place predictions.
- Settlement remains delayed longer than expected.
- Admin access or permissions block a time-sensitive workflow.
- A market outcome cannot be resolved fairly from the published rule.