Players were asking for help in five different Discord channels, staff were answering the same questions twice, and nobody could tell which issues were still open. That was the support situation at BeeSim when I took it on. I fixed it by building BeeSim Support, a portal that connects Discord identities to a web dashboard so every ticket lives in one place no matter where it starts.
Linking Discord to the web
The first piece was account linking. Players connect their Discord identity to their web profile, so every ticket arrives carrying a verified username and server history. Staff never have to ask "what is your Discord" again, and impersonation stops being a problem because identity is confirmed on both sides before a ticket can even be created. That single decision removed an entire category of confusion.
One ticket, two interfaces
The second piece was syncing. A ticket created on the web is mirrored into the right staff Discord channels by bots, and replies flow both ways — a moderator answering from Discord and one answering from the dashboard see the same thread, the same history, and the same status. Players stay inside the community they already live in, while staff get a calm, organized queue instead of five noisy channels.
Security had to come first
A support system holds sensitive conversations, so the admin portal sits behind rotating secured passwords rather than static credentials. Logins are validated on every attempt, and sensitive actions ask for re-authentication before anything changes. If a password ever leaks, its useful lifetime is short by design. Security is not a feature I bolted on later — it shaped the architecture from the first sketch.
Built for a crowd
BeeSim has a large player base and a growing staff team, so the system needed structure. Ticket categories, priority levels, and assignment rules keep things organized during peak hours, and automated status updates tell players when their issue is being worked on, resolved, or escalated. Nobody is left wondering whether anyone saw their message.
What I would do differently
If I rebuilt it today, I would add an audit log on every ticket, SLA timers per priority level, and saved replies for the ten questions that make up half of all tickets. The core idea would stay exactly the same though: meet users where they already are, and give staff one calm screen. You can read the full project breakdown on the BeeSim Support page.