Roadmap

Run whitelist, faction or staff applications as a guided flow — review the answers, approve or deny in one tap, and the bot hands out the role automatically on approval.

Label tickets and filter the queue by tag on the dashboard, so a big backlog stays navigable and the right tickets surface first.

Every update is health-checked the moment it goes live — if something breaks, the bot rolls back to the last known-good version automatically. A bad release can’t take your tickets down.

Drop in pre-built ticket panels — refunds, reports, partnership requests, content takedowns. Edit the copy, post the panel, done.

Member writes in their language, staff reads and replies in theirs — translated inline inside the channel, both sides none the wiser.

An alternative to one-channel-per-ticket: each ticket as a forum post, with native Discord tags and an archive that doesn’t clutter your channel list.

The bot already follows your server’s language. Next: each member picks their own — one international community, no language-split servers.

A standby instance with database replication that takes over if the primary goes down — real redundancy for communities that can’t afford a support outage. Heavy infra, so it lands once the paid base justifies it.

Drafts a response your staff can ship in two clicks, right in the channel. Your tone, your knowledge base — not generic AI noise. Opt-in, ticket content stays in your scope.

Suggest the right help article before a ticket is even opened. The questions that answer themselves never reach the queue.

A live "average response time" embed for your community to display. Trust earned in numbers.

Volume over time, median first-response and resolution times, busiest hours, load per staff member — on the web dashboard.

Forward open / claim / close events to Slack, Linear or any webhook. Useful for ops teams, but it pulls the workflow out of Discord — so it stays a "maybe" rather than a focus.

Run DiscordNext as your own product — your brand on the admin surface, your subdomain, our infra underneath. Agency-focused and web-heavy, hence parked here.

A step-by-step wizard walks you from zero to live tickets — and a re-openable checklist tracks what is left. A teaching bar shows the Roles → Team → Category → Panel pipeline at every step, so the order finally makes sense the first time.

Greet every new ticket with a branded card — your banner image, the category, status and priority, and an SLA checkmark that ticks the moment staff respond. Edit it live from the dashboard, no re-posting required.

Claim, close and transfer messages are yours to shape — the wording, the icon and the colour, per server. The bot speaks in your voice instead of a generic default.

Per-member and per-team support metrics — tickets handled, response and resolution times, support-voice time and CSAT — rendered with real Discord avatars. See who is carrying the queue at a glance.

Give each panel an internal name to keep your setup readable, and pause a panel to unpost it from Discord without deleting its configuration — flip it back live whenever you are ready.

Every language gets its own indexable address under a /de/ /fr/ … prefix, with correct hreflang tags and a dynamic sitemap. Search engines serve the right language to the right visitor instead of one generic page.

The full dashboard and every bot message ship in 28 languages — from English, German, Spanish and French to Chinese (Simplified & Traditional), Japanese, Korean, Hindi, Thai, Vietnamese, Indonesian, and most of Europe. Each one complete and hand-reviewed, not crowdsourced.

Images shared in a ticket are copied to our own storage on close and rendered in the dashboard view and the HTML export — they stay visible long after Discord’s own attachment links expire.

Teams ranked above a category on the escalation ladder automatically get view access to its tickets — a senior tier oversees what lower tiers handle, without becoming the first responder.

Per-category opt-in: the bot mentions the category’s team roles the moment a ticket opens — in the staff thread on thread-only servers, otherwise in the ticket channel.

The bot joins your support voice channel and plays your uploaded MP3s — once or on loop, with business-hours/custom time windows, per-greeting volume and an optional staff ping.

/warn, /timeout, /kick, /ban (permanent or temporary with auto-unban) and /unban — every action recorded in a case history with executor and reason, DM to the member, and an optional mod-log channel.

View, search, ban and unban from the dashboard, /bans and /baninfo in Discord, plus a who-banned-whom history that outlives Discord’s 45-day audit log.

Pull tickets, stats, transcripts and bans over a documented v1 REST API with per-server keys — for your own tooling and integrations.

Every feature area — greetings, reaction roles, canned responses, moderation, voice, API — is a module you switch on per server. Off means off: nav, commands and endpoints included.

Expert servers keep closed-ticket transcripts forever instead of the 365-day cap — re-downloadable from the dashboard any time.

Pause a whole category or a single reason ("applications are closed, back July 1st") with a custom notice — without deleting the setup.

Build self-service role pickers without touching bot commands. Pair an emoji with a role, post the message, done.

Export any ticket as a self-contained HTML file — avatars, markdown and timestamps preserved, optionally including the internal staff chat.

Set priority, transfer a category, add or remove members — all through clean Discord modals instead of cluttering the channel with commands.

Per-tier response deadlines with a live countdown, colour-coded risk and an alert before a ticket breaches. Staff see what needs attention first.

Auto-posted messages for joins, leaves and server boosts — your branding, your copy, no extra bot in the member list.

Build a snippet library in the dashboard; staff drops one into any ticket with /reply <key>. Autocomplete picks the right answer in two keystrokes.

When a ticket closes, the opener taps one of three buttons right in the close DM. Score saves to the ticket and shows up on the dashboard — no survey link required.

Paying subscribers get their Discord roles assigned the moment payment clears. No support tickets to claim tier benefits — they just show up.

Closing locks the channel with a 🔒 prefix and keeps a Reopen button available for 24 hours before auto-deletion — misclicks and second thoughts are recoverable.

Multi-step questions per category — dropdowns and text — asked before a human is paged. Staff open the ticket to a clean, pre-filled summary instead of "hi" and silence.

Set your team’s hours. Off-hours tickets get an honest "we’re back at 9:00" reply and the SLA clock freezes, so you’re not judged on time you were asleep.

After a configurable quiet stretch the bot asks once "still need help?" — only when staff answered last. No response → the ticket closes itself a day later.

Order your teams from front-line to most-senior. An unanswered ticket climbs the ladder automatically; non-support teams stay off-ladder as standalone working groups.

Breached tickets escalate on a schedule — bumping priority or climbing the team ladder — until they’re handled. The resolution clock pauses while you’re waiting on the member.

New tickets can auto-assign to the eligible staff member with the fewest open tickets, so the workload spreads evenly.

Bar specific members from opening tickets, and set a minimum gap between opens to shut down spam — dashboard or /blacklist.