Ticket Routing

One intake form, department-owned ticket centers.

Vuplore does not collapse everything into one central queue. Intake classifies the request, creates the ticket in the responsible department, and keeps claim, chat, attachment, audit, and resolve logic consistent across departments.

Routing Matrix

Support sends work to the right owner.

TASTrust & Safety TicketsReports, appeals, moderation records, player safety, CSAM/abuse flags, custom-battle reports. PACPeople & Culture TicketsApplications, staff lifecycle, staff conduct, time corrections, Integrity Review intake. PATProduct & Technology TicketsBugs, platform incidents, bot operations, release issues, technical review. CACCommunity & Communications TicketsAnnouncements, newsletter, public media, ad placements, community requests. LACLegal & Compliance TicketsPrivacy requests, legal notices, commercial terms, data corrections, deletion reviews. FACFinance & Commercial TicketsBilling, services, vendors, sponsorships, commercial fulfillment. IASIAS TicketsRestricted escalations and security referrals only.

Claim Logic

Every department uses the same base ticket protocol.

Ticket is created inside one department, with category, readable ticket ID, creator identity, target identity, and evidence state.

Eligible staff claim the ticket. Department chief, CEO, CI, and authorized IAS oversight can see broader queues where policy allows.

Resolution actions are type-specific: approve/deny/correct flag for AI review, uphold/reduce/remove for appeals, fulfill/decline for services.

Reassignment keeps the audit trail and moves the ticket to another department, category, or type without losing chat history.