Appearance
AI Agents
Pixup AI Agents are operator assistants inside the admin panel. They are designed to answer short business questions, guide operators to the right workflow, draft campaigns, and highlight the checks that should happen before action is taken.
The first agent available in the admin panel is Pixi AI Admin Operator.
Chapter map
This section explains the agent system from three angles:
| Chapter | What it explains | Read it when |
|---|---|---|
| AI Agents overview | The overall agent model, roles, and operating principle. | You want to understand what Pixi and the specialist agents are meant to become. |
| Pixi AI Admin Operator | The admin widget, current commands, bonus drafts, prompts, and safety rules. | You are using Pixi inside the admin panel. |
| Admin and player context | How admin actions connect to player experience. | You want operator-friendly context instead of technical details. |
| Operator playbook | Practical workflows for daily checks, campaigns, risk, payments, VIPs, and escalation. | You want examples of how an operator should work with Pixi. |
| Agent glossary | Short definitions for the words used in the agent docs. | A term like “GGR”, “SLA”, “guardrail”, or “handoff” is unclear. |
Current agent model
Pixi acts as the central operator layer. It does not replace human approval. It helps the team move faster by turning common questions into short answers, shortcuts, draft campaigns, and operational checklists.
| Agent | Purpose |
|---|---|
| CEO Agent | Daily executive briefing, revenue signals, risks, opportunities, suggested actions. |
| CRM / Bonus Agent | Bonus campaign ideas, player segments, offer drafts, expected ROI checks. |
| VIP Agent | High-value player monitoring, VIP churn signals, reward suggestions, message drafts. |
| Fraud & Risk Agent | Bonus abuse, AML, multi-account, chargeback and suspicious pattern checks. |
| Marketing Agent | Campaign ideas, CPA checks, content prompts and acquisition quality. |
| Support Agent | Payment complaints, verification delays, player replies and escalation wording. |
What “central operator layer” means
Pixi is the first assistant the operator talks to. It should understand the question, decide whether it is a navigation request, a live data request, a bonus draft, or a specialist-agent topic, and return the next useful step.
In the future, Pixi can become the central brain that reads reports, pulls data from platform systems, assigns work to specialist agents, and reports to the CEO only when a human decision is required.
Operating principle
Pixi should keep answers short. For most admin use cases it should answer with one clear sentence, a compact example, or one next action.
When Pixi prepares an action, the expected flow is:
- Draft the item.
- Show what will change.
- Ask for approval.
- Create or update only after confirmation.
- Leave an audit note.
How specialist agents should be used
Specialist agents are not separate UI widgets yet. Today they are a mental model inside Pixi’s answers. For example, when an operator asks about churn, Pixi can answer as the CRM / Bonus Agent. When the question is about suspicious player behavior, Pixi can answer as the Fraud & Risk Agent.
The important idea is routing: the operator should not need to remember every admin page or every checklist. Pixi should identify the work type and point to the right workflow.
What is verified
The current admin widget can route users, answer predefined operator questions, check selected live deposit and withdrawal counts, show dashboard snapshots, and draft bonus forms for supported bonus types.
Fully autonomous creation is not enabled yet.