doing ยท High priority
VoidBot Support Desk
VoidBot now provides a private support desk. Members open a structured Discord form with request type, priority, subject and detail fields; configurable routing assigns the right private category and support role. Every ticket has one self-updating dashboard with claim, release, transfer, workflow, priority, close and permission-safe reopen controls. Staff can keep private notes, retain private close transcripts under an opt-in retention policy, and monitor first-response or inactivity reminders. Members can leave a one-time satisfaction rating after resolution. The native Go/PostgreSQL panel adds live queue health, waiting-state totals, response-time and rating analytics, routing, reminder and retention controls, while the bot and panel use PostgreSQL for operational ticket state. Full live lifecycle and recovery verification is still in progress. Restart reconciliation repairs stale controls and recreates a deleted dashboard without duplicating healthy messages. Ticket creation now validates the current Discord category and support roles before creating a channel or sending pings, rejects deleted roles and @everyone support access, and bounds lookups to ten seconds. The deployed guard passed Go and PostgreSQL release checks; a read-only Void Hub audit found no unexpected readers or blocked staff across four ticket destinations. A real new-ticket creation test remains outstanding.