Dashboard
Logs
--
0 errors
0 warnings
Tickets
--
0 pending
Alerts
--
0 monitors
Flagged Players
--
Public Replies
--
skill / apperfun
History
Loading...
Loading the latest summary...
to
Loading logs...
Loading logs...
Queued Tickets
| Ticket ID | Task | Status | Created At | Claimed By | Actions |
|---|---|---|---|---|---|
| Loading... | |||||
Pending Tickets
| Ticket ID | Subject | Pending Duration | Received At | Actions |
|---|---|---|---|---|
| Loading... | ||||
Players Awaiting Payment
| Ticket | Amount | Player | Added | Last Check | Actions | |
|---|---|---|---|---|---|---|
| Loading... | ||||||
Alert Monitors
| Name | Type | Count | Threshold | Window | Cooldown | Status |
|---|---|---|---|---|---|---|
| Loading... | ||||||
Recent Tickets
Loading...
Enter a ticket ID to investigate
Flagged Players
Loading...
New message
Sent to Phlipper with every reply for the games you tick, from the next ticket on. Use it for what the team knows today and Phlipper can't — an incident, a delay, a known bug. Set an expiry, or delete it when it stops being true.
(also covers games added later)
Messages
Loading...
⚠ Danger zone — this controls what real players receive
Each game family is either replying to players directly, replying only to a
named pilot, or off — writing every answer as an internal note for a
human agent instead. Changes take effect on the next ticket, with no deploy, and are reversible
in seconds. A wrong answer on a family that is switched on reaches the player; on a family that is
off it reaches nobody but the agent who owns the ticket.
Loading...
Knowledge Documents
Support reference files, stored in the bucket beside the playbooks. Uploading
replaces a document of the same name; the previous copy is not kept.
| Document | Type | Size | Updated | Actions |
|---|---|---|---|---|
| Loading... | ||||
Ask Phlipper anything — ticket lookups, player info, FAQ, playbooks, recent logs. Read-only: no ticket actions.
Tickets Scan
Click Scan to fetch all open tickets waiting for 2nd level support.
No scan yet.
FAQs
Loading...
Playbooks
Loading...
One or two sentences describing what the player says when this playbook should handle the ticket. This is what the classifier reads — it decides which tickets reach this playbook.
actions the agent can perform — click Insert to reference one
Game Knowledge
What the player's words mean, and the facts the Help Center does not state.
One body per game group — unlike a playbook, this is injected as a system
turn on every reply for that group's games, so an edit here
changes every subsequent ticket.
API Docs
Feature Knowledge
How a game feature works — album, BlingCup, the daily quest, the wallet. A playbook
sends the agent here by naming the feature, e.g. "read the 'album' feature
knowledge first". The agent reads these through the
agent_read_feature_knowledge action.
Loading...
The first line is the summary the agent reads when picking a feature, so make it one plain sentence. Everything below it is what the agent is served once it picks this feature.