AI_IMAGE: A dark moody screenshot-style composition showing a Discord application window on a monitor with a deep navy theme, displaying a support channel with a bot message containing an embedded card with electric blue accent stripe showing a ticket number and priority badge, a list of recent support messages with timestamps in the sidebar, the monitor sitting on a dark desk with subtle blue ambient backlighting | photorealistic | landscape

2024

Discord Support Bot

Tech Stack

Node.js, Discord.js, SQLite, REST API, PM2

Project URL

https://dnaie.com/projects/discord-bot


A custom Node.js Discord bot that acts as the front line for incoming tech-support requests — triaging tickets by priority, routing them to the right queue, and logging every conversation to a persistent database for follow-up.

Background

Discord became the natural intake point for support requests — clients were already there, and the barrier to sending a message is lower than filling out a web form. But unstructured DMs and channel messages created chaos: requests got buried, priority was unclear, and nothing was tracked.

The bot introduced structure without adding friction. A client types a command, answers three quick prompts, and a structured ticket is created, acknowledged, and queued — all within the Discord interface they already know.


Feature Set

  • Slash command intake flow collecting device type, issue description, and urgency level
  • Automatic priority assignment based on keyword analysis and urgency selection
  • Embedded ticket cards posted to a dedicated triage channel with color-coded priority badges
  • SQLite backend storing full conversation threads linked to each ticket ID
  • REST API endpoint mirroring ticket data to the SimplyServices Platform admin for unified tracking
  • PM2 process management for zero-downtime restarts and crash recovery

Tickets Processed

Over three hundred support tickets triaged in the first four months of deployment, with an average first-response time under two hours.

Resolution Rate

Ninety-two percent of tickets resolved within the Discord thread itself — no email chains, no phone tag, no context lost between platforms.

Lessons Learned

The biggest surprise was adoption speed. Clients who had ignored the web-based contact form started filing structured tickets within days of the bot going live. Meeting people where they already are turns out to be the single most effective support optimization — more impactful than any backend improvement.

The best support system is the one your clients actually use. Discord was already open on their screens.