Skip to main content

Player Support

Player Support is a core feature. It keeps one ticket history while the project chooses how tickets are processed:

  • Internal support - the team replies in the administration panel;
  • Omnidesk - tickets are delivered to an external help desk while players keep using the same cabinet interface.

Changing the processing mode does not create a second ticket list or change the player workflow.

Project selection​

Support is configured independently for every project. Select a project first, then work with its queue, staff, rules, and integrations. Data from different projects is never combined.

The entry point lists only projects available to the administrator

Project overview​

Queue health, workload, and recent tickets for the selected project

Included sections​

SectionPurpose
OverviewKey metrics and direct access to the queue
TicketsSearch, filters, assignment, priority, and bulk actions
CategoriesLocalized ticket topics, order, and external mappings
StatisticsWorkload, response time, and ticket distribution
MacrosLocalized reusable replies
ModerationTemporary and permanent write restrictions
IntegrationsOmnidesk connection and custom-field mappings
SettingsAvailability, content rules, cooldowns, and staff identity
AttachmentsFile limits, storage, access, and delivery verification
Player cabinetTicket creation, conversation, response feedback, and special states
Filters, selected tickets, and available actions in one work-focused table

Ticket states​

  • New - the ticket has been created and has not been processed yet.
  • Waiting for staff - the project team must reply next.
  • Waiting for player - the team replied and is waiting for more information.
  • Cancelled - the ticket was cancelled and is no longer in the active queue.
  • Closed - work is complete and the conversation cannot continue.

External delivery state is displayed separately and never replaces the ticket workflow state.

Players see their own tickets, current state, and unread replies

Launch sequence​

  1. Open support settings and define availability, content rules, and limits.
  2. Select Internal processing or configure the Omnidesk integration.
  3. Create and order the ticket categories.
  4. Configure attachment storage.
  5. Grant team permissions and prepare reply macros.
  6. Create a real test ticket from the player cabinet, reply to it, and verify an attachment.
  7. Enable the player-facing section only after the complete check passes.
info

Disabled Player Support is removed from the player menu; new tickets are unavailable.