Overview
Platform Performance
Deposits vs. how many actually turned into a Quina ticket — 1,000 deposits with only 100 claimed means 900 members paid and never played. Always every platform, regardless of the filter above.
| Platform | Total recharges | Claimed | Unclaimed | Claim rate | Last 7 days | Volume trend | Claim rate trend |
|---|
Recharges vs Claimed — last 7 days
Claim Rate Distribution
Key Insights
Per contest
Volume per contest
Valid rate trend
| Contest | Total | Valid | Invalid | Pending | Valid rate |
|---|
Entries
| ID | Platform | Game ID | Numbers | Contest | Source | Submitted (BRT) | Status | Backed by deposit | Decided by | Override |
|---|
Member lookup — search across all platforms
Type a Game ID or WhatsApp number exactly as it appears on a screenshot or chat — this checks every platform at once, not just whichever one you'd otherwise have to pick first.
Recharge — upload or paste from platform admin
Two ways in, same result either way: paste a quick manual block below, OR upload a platform's export file as-is (the raw file with Chinese column headers — no need to retype it into columns first, this reads that format directly). Safe to redo an overlapping window — duplicates by order number are ignored, and every member touched gets re-matched against their tickets automatically.
All deposits
Shows the latest 100 by default — this table only grows, so browsing "everything" isn't a real option. Pick a platform, date, or search term to look further back. Filters apply as you type/pick — no need to press a button.
| Platform | Member ID | Order # | Amount | Occurred (BRT) | Entered by | Claimed by |
|---|
Draw results
| Contest | Draw date | Numbers | Entered by |
|---|
Winners
Every platform's winners for the contest at once — each platform has its own separate R$900 prize, so this isn't twelve questions, it's one.
| Platform | Entry | Game ID | Matches | Prize | Jackpot |
|---|
Staff (ADMIN only)
| Name | Role | Active | Last login (BRT) | Actions |
|---|
Agent allowance
Set an agent's allowance
Browse & filter
A batch is only good until the next concurso after it lands — normal days it's that same evening's 20:00 BRT draw; Saturday has no draw of its own, so Friday's and Saturday's earnings both roll to Sunday's 11:00 BRT draw instead; Sunday's earnings roll to Monday 20:00. Past that cutoff the remaining balance is hangus — it doesn't carry forward.
| Agent | Platform | Free | Used | Remaining | Valid members | Expires (BRT) |
|---|
Grant history
Every time an agent's allowance is set or a referral report is uploaded, it gets its own reference — same idea as a deposit's order number — so a ticket generated from that allowance can point back to exactly which grant funded it, not just a running balance.
| Reference | Platform | Agent | Tickets | Source | Granted by | Granted at (BRT) | Earning date | Claim cutoff (BRT) |
|---|
Referral report — paste from staff tracking
Paste the referral-earnings report as-is: columns ALL ID REPORTED, ID AGENT, TOTAL TICKET, INDICATE (comma or tab separated, header row optional). This only records the totals — the rules for which referrals count are tracked outside this system. Re-pasting an updated report overwrites each agent's free-ticket total with the new number.
Members generate their own free tickets at /agente once their
allowance shows here — there's no staff-side bulk-generate step.
Special allowance
Grant a member an allowance
Browse & filter
| Game ID | Platform | Free | Used | Remaining |
|---|
Grant history
Same idea as agent grants — every Set gets its own reference, so a ticket backed by a special allowance can point back to exactly which grant funded it.
| Reference | Platform | Member | Tickets | Granted by | Granted at (BRT) |
|---|