Appearance
Pixi AI Admin Operator
Pixi is the assistant in the lower-right corner of the Pixup admin panel. It is intended to be an AI Admin Operator: short answers, practical shortcuts, and safe drafts for common operator work.
Pixi should feel like a calm operations partner. It should not overload the operator with theory. It should help the operator decide where to look, what to check, what to draft, and when to ask for approval.
Chapter map
| Chapter | What it means |
|---|---|
| What Pixi can do now | The current capability list inside the admin widget. |
| Supported bonus draft commands | Which bonus forms Pixi can prepare today. |
| Useful prompts | Short questions operators can ask during real work. |
| Daily operator workflows | How Pixi fits into morning, payment, bonus, risk and support work. |
| Safety rules | The checks Pixi should mention before live changes. |
| Recommended future upgrades | What should be built next when Pixi becomes more autonomous. |
What Pixi can do now
| Area | Examples |
|---|---|
| Navigation | “Open players”, “Where are bonus reports?”, “Help on this page” |
| Live signals | “Today deposits”, “This month withdrawals”, “Morning brief” |
| Bonus drafts | “Create deposit bonus”, “Create welcome bonus”, “Create cashback bonus” |
| Bonus guidance | “Bonus safety check”, “Bonus recipe”, “Bonus cost guard” |
| Operations | “Next best action”, “Risk alerts”, “Withdrawal SLA”, “Provider issue” |
| Player work | “Find player”, “Player health”, “Suspicious player”, “Churn rescue” |
| Agent routing | “Assign to VIP Agent”, “Which agent should check fraud?” |
| Governance | “Approval check”, “Audit note”, “Rollback plan”, “Compliance check” |
| Marketing | “Campaign idea”, “Campaign calendar”, “Campaign copy”, “A/B test plan” |
What each capability means
Navigation
Navigation means Pixi helps the operator reach the right admin page without remembering the menu structure. This is useful for new operators and during incidents when speed matters.
Example: “Where do I check failed deposits?”
Live signals
Live signals are short reads from the platform, such as today’s deposits or a dashboard snapshot. These answers should be brief and should point to the report where the operator can verify the number.
Example: “How many deposits today?”
Bonus drafts
Bonus drafts are prefilled forms. Pixi can prepare the starting point, but the operator is still responsible for reviewing dates, limits, images, targeting and approval.
Example: “Create 50% deposit bonus over 100 EUR max 200 wagering x10.”
Bonus guidance
Bonus guidance explains whether a campaign setup is sensible. Pixi should focus on caps, wagering, budget, eligibility, player restrictions and cost.
Example: “Is this bonus safe?”
Operations
Operations prompts help the team decide what to check first. Pixi should prioritize money movement, player impact, provider issues and risk.
Example: “What should I check now?”
Player work
Player work starts with lookup and continues into health, churn, VIP or risk. Pixi should help the operator understand the player before recommending action.
Example: “Check player health.”
Agent routing
Agent routing means Pixi explains which specialist-agent workflow fits the task. It does not require a separate UI yet.
Example: “Which agent should check churn?”
Governance
Governance means Pixi helps the operator avoid unsafe live changes. The core ideas are approval, audit notes, rollback plans and compliance checks.
Example: “Can I publish this campaign?”
Marketing
Marketing prompts help create campaign ideas, short copy, calendars and test plans. Pixi should connect the idea to measurable results, not just write text.
Example: “Give me a campaign calendar.”
Supported bonus draft commands
Pixi can prepare draft form data for these bonus types:
| Bonus type | Example prompt |
|---|---|
| Deposit Bonus | “Create 50% deposit bonus over 100 EUR max 200 wagering x10” |
| Welcome Bonus | “Create welcome bonus 100 EUR wagering x10” |
| Cashback | “Create 10% cashback for 7 days” |
| Free Spins | “Create 20 free spins wagering x10” |
| Referral Bonus | “Create referral bonus 25 EUR” |
| Direct Bonus | “Create direct bonus for player 12345 amount 20 EUR” |
Pixi opens the bonus screen with a prefilled draft. Operators still need to add dates, images, targeting, provider/game choices, and final approval before publishing.
Daily operator workflows
Start of day
Ask “Morning brief” or “Daily agenda”. Pixi should return the first platform signals and the first action to check. The operator should then verify details in Dashboard, Financial and Reports.
Payment review
Ask “Payment health”, “Failed deposit recovery” or “Withdrawal SLA”. Pixi should help the operator focus on stuck money movement before campaign work.
Bonus creation
Ask Pixi to draft the campaign, then ask “Bonus safety check” and “Approval check”. This creates a slower but safer path to publishing.
CRM and retention
Ask “Segment idea”, “Churn rescue” or “Campaign idea”. Pixi should suggest a target group, an offer shape and a measurement window.
VIP work
Ask “VIP risk” or “VIP message”. Pixi should help identify retention risk and draft a short account-manager message.
Support work
Ask “Support reply” when a player needs a calm, non-technical response. The operator should still verify the actual player and transaction state before sending.
Risk review
Ask “Fraud scan”, “Suspicious player” or “Compliance check”. Pixi should remind the operator to check profile overlap, payment data, bonus patterns, chargebacks, KYC and responsible gaming restrictions.
Useful prompts
| Prompt | What Pixi returns |
|---|---|
| “Agent capabilities” | A short summary of what Pixi can help with. |
| “Morning brief” | Deposits, withdrawals, depositing players and first priority. |
| “What to check now” | A quick operator checklist. |
| “Risk alerts” | Key red flags to watch. |
| “Bonus ROI” | ROI formula or a simple calculation if revenue and cost are included. |
| “Segment idea” | A campaign segment suggestion. |
| “VIP message” | A short account-manager message draft. |
| “Support reply” | A short player-support response draft. |
| “Explain GGR” | A simple metric explanation. |
Safety rules
Pixi should not publish campaigns silently. It should ask for approval before any future create/update action that changes live platform data.
Before publishing a campaign, Pixi should remind the operator to check:
- Dates and timezone.
- Bonus cap and budget owner.
- Wagering and conversion rules.
- Targeting and exclusions.
- KYC, AML and responsible gaming restrictions.
- Image and player-facing text.
- Audit note.
Recommended future upgrades
| Upgrade | Value |
|---|---|
| Real agent backend | Let Pixi call a controlled backend instead of only frontend intent rules. |
| Approval workflow | Require explicit confirmation before creating campaigns. |
| Audit trail | Save who asked Pixi, what draft was created, and who approved it. |
| Live anomaly engine | Compare today vs yesterday and flag spikes or drops automatically. |
| Player segmentation API | Generate segments from real player behavior. |
| CEO brief scheduler | Send a daily summary only when intervention is needed. |
| Specialist agent queue | Route tasks to CRM, Risk, VIP, Marketing or Support workflows. |
Current limitation
Pixi is currently a guided admin assistant with selected live data reads and draft creation. It is not yet a fully autonomous agent system.