Ticket Tool NextThe complete capability list
Every capability below is also a row in the table further down, and every row is checked against the code before this page ships. Where something is not built yet, it says so.
A member presses one button and lands in a private channel, with the people who can help already in it.
Panels
A panel is a ticket type, independently configured: its own message, button, form, category and team. One posted message can carry up to 25 of them.
Questions before the channel opens
Up to five questions, and dropdown questions rather than only text boxes. Five is Discord's modal limit, not ours.
A channel, or a thread
Channel tickets move between an open and a closed category. Thread tickets do not consume Discord's 500-channel ceiling, and carry a staff-only side thread.
Who can see a ticket is a grid of allow, inherit and deny, which is why this bot never asks for Administrator.
- Nine permission editors. Around twenty-two permissions each, set separately while a ticket is open and while it is closed. Inherit leaves a role exactly as the server has it.
- Claiming. Ten behaviours to choose between: hide the ticket from other staff, rename it, move it, overwrite access, restrict who may reply. Premium
- Scheduled support hours. Per day, per hour, aware of your timezone, with roles that bypass it. Outside them the panel says so instead of opening a ticket nobody is reading. Premium
Ten triggers and five actions, each with a delay measured from seconds to a month.
Automation rules
Seven triggers fire the moment they happen; the interval watcher fires on presence or absence over a window from five minutes to thirty days, and can keep checking after it fires. A rule can be stopped so a human can take the conversation over.
Custom commands
The question you answer twice a day becomes a command you type once. Named capture groups from a regular expression are usable as variables in the reply.
Every word the bot says
Thirteen separately editable message types, around fifty variables and eleven chainable modifiers, previewed exactly as Discord will render them.
The conversation leaves as one HTML file, and the numbers behind it stay honest.
- Transcripts. Up to a thousand messages as one HTML file, on close, on delete, or both. Who may open one is gated on the roles you nominate.
- A searchable audit log. Who changed what, and exactly which values moved. Event logging has a toggle per event rather than one switch for all of them.
- Statistics. Volume per panel and claims per staff member. Deleting a ticket's channel leaves the record behind on purpose, so last month's numbers cannot be rewritten.
The part that is not a like-for-like copy, including the one thing that is built and still not for sale.
An MCP server for AI assistants
Connect Claude Code, Cursor or VS Code with an access token, and the assistant can list your tickets, read one or its transcript, reply and close. Every call is checked against Discord, and never more than a minute old.
A real, ordered queue
Priority sets a ticket's actual place in the line rather than colouring a label, and a first-response target is attached to it.
Tickets from your own website
A form on your site opens a real ticket, synced both ways with the Discord channel, so a member who never joins the server still gets an answer.
AI answering in the ticket
Tell it about your business, upload your documents and list your web pages. When a ticket
opens, Connections AI greets the member, asks what they need, and answers each message from
what you gave it, naming its source. It says so when it does not know, and a
Talk to a person button hands the ticket to your team at any time.
/ask answers the same way outside a ticket.
Queue boost
Built, and deliberately not for sale. Where a member's payment would go is still being settled, so the ladder can be configured and nothing can be bought.
Every capability, with the Premium line drawn where it really falls. Nothing is ticked here that the code cannot be shown to do.
| Capability | Free | Premium | Notes |
|---|---|---|---|
| Ticket lifecycle | |||
| Unlimited panels and ticket categories | ✓ | ✓ | A panel is a ticket type, independently configured |
| Creation by button, dropdown, command or schedule | ✓ | ✓ | Command creation can target a user and take a reason |
| Ticket forms, up to 5 questions | ✓ | ✓ | Discord's modal limit, not ours |
| Dropdown questions, not just text boxes | ✓ | ✓ | Discord bans dropdowns inside a form, so we ask them just before it |
| Channel-mode tickets | ✓ | ✓ | Moved between open and closed categories |
| Thread-mode tickets | — | ✓ | Does not consume the 500-channel ceiling |
| Staff-only side thread | — | ✓ | Excluded from the transcript |
| Naming patterns and zero-padding, 0–20 digits | ✓ | ✓ | Separate patterns for open and closed |
| Per-user and server-wide limits, open and closed | ✓ | ✓ | 0–500 each, with bypass roles |
| Escalation between panels | ✓ | ✓ | Adopts the target panel's category and team |
| Channel recycling | ✓ | ✓ | Parks, wipes and reuses deleted channels |
| Auto-close with a warning first | ✓ | ✓ | A quiet ticket is warned, and any reply cancels the close |
| Messages | |||
| 13 separately editable message types | ✓ | ✓ | Each a full embed builder with 25 fields |
| Full embed customisation, no character caps | ✓ | ✓ | On every plan, up to Discord's own limits. The incumbent caps free servers |
| ~50 variables, 11 chainable modifiers | ✓ | ✓ | Server, owner, author, reasons, timing, form answers, regex captures |
| Live preview of what Discord will render | ✓ | ✓ | Including images, fields and footers |
| Direct messages on ticket events | — | ✓ | Says so in the ticket when a DM bounces |
| Staff | |||
| Claiming, with 10 behaviour options | — | ✓ | Hide, rename, move, overwrite, restrict |
| Support, additional, admin and blacklist roles | ✓ | ✓ | Blacklist carries its own refusal message |
| 9 permission overwrite editors, ~22 permissions each | ✓ | ✓ | Allow, deny or inherit per permission |
| Automatic role changes on state change | — | ✓ | Opened, closed, claimed, unclaimed |
| Scheduled support hours | — | ✓ | Per day, per hour, timezone aware, with bypass roles |
| Automation | |||
| 10 triggers including the interval watcher | — | ✓ | Fire on presence or absence, 5 minutes to 30 days, once or until stopped |
| 5 actions, each with its own delay | — | ✓ | 0 seconds to 30 days |
| Custom commands: strict, wildcard and regex | ✓ | ✓ | Named capture groups usable as variables |
| Up to 5 arguments with a configurable separator | ✓ | ✓ | Post in channel, DM the invoker, or DM the owner |
| Records | |||
| HTML transcripts, up to 1,000 messages | Manual | Automatic | On close, on delete, or both |
| Transcripts that keep the files | — | ✓ | Copies uploaded files while the Discord links still work; needs object storage |
| Event logging with per-event toggles | ✓ | ✓ | Created, opened, closed, deleted, renamed, claimed, transcript |
| Statistics history | 7 days | Full | Volume per panel, claims per staff member |
| Searchable audit log with structured diffs | ✓ | ✓ | Who changed what, and exactly which values moved |
| Config backup, restore and transfer key | ✓ | ✓ | Tickets deliberately excluded |
| Integrations | |||
| Outbound webhooks with your own auth header | ✓ | ✓ | Per-event toggles |
| Bloxlink (Roblox identity) | — | ✓ | Your key, your quota |
| Allow-list of other bots | ✓ | ✓ | Off by default, which is what stops two bots looping |
| True white labelling - your own application | — | White label tier | Your bot, your badge, your rate limit, your domain, set up with you |
| Staff tooling | |||
| Add and remove people from a ticket | ✓ | ✓ | /add and /remove, by individual grant |
| Private staff notes on a ticket | ✓ | ✓ | /note and /notes. The member who opened it never sees them |
| Rename, transfer, staff thread, close request | ✓ | ✓ | Plus /open, /delete and /transcript |
| Right-click a message or a member to open a ticket | ✓ | ✓ | Discord context-menu actions |
| Priority, four levels | ✓ | ✓ | Sets the ticket's real place in the queue |
| Saved panel templates and a starter catalogue | ✓ | ✓ | 1 template free, 25 on Premium; share by code |
| Temporary dashboard access | ✓ | ✓ | An expiring link, owner-level, one at a time |
| Per-panel log channel overrides | ✓ | ✓ | One panel's logs can go somewhere else |
| One-command setup | ✓ | ✓ | /quicksetup makes a category and a working panel |
| Safety and abuse | |||
| Ticket creation cooldown and rename limits | ✓ | ✓ | On from the start: 10 seconds between tickets, 2 renames in 10 minutes; bypass roles honoured |
| Raid lockout | ✓ | ✓ | Freezes new tickets past a rate you set |
| Minimum account age | ✓ | ✓ | Turns away accounts made minutes ago |
| Role-gated transcript viewing | ✓ | ✓ | Staff, the owner, and roles you nominate |
| Feedback and intake | |||
| Ticket ratings, 1 to 5 stars | — | ✓ | Three modes, a rating log, per-staff averages |
| Applications with a review queue | ✓ | ✓ | Staff recruitment and signups, decided in the dashboard |
| 33-language interface | ✓ | ✓ | One language per server. Fifteen cover every message the bot sends; the rest cover the basics and show English where a line is not yet translated |
| Identity | |||
| Steam account linking | ✓ | ✓ | OpenID 2.0, verified against Steam, not merely claimed |
| Roblox and Twitch linking | ✓ | ✓ | First-party OAuth. No third-party bot, no API key of yours |
| Require a linked account on a panel | — | ✓ | The panel refuses until they link |
| Linked profile in the ticket header | — | ✓ | Staff see who they are talking to |
| Beyond the incumbent | |||
| Queue boost | — | Not yet | Built, not for sale until where a member's payment goes is settled |
| A real, ordered ticket queue | ✓ | ✓ | With first-response targets. The incumbent has none |
| Ticketing from your own website | — | Add-on, $5 | Bought separately, on any plan. Synced both ways with the Discord channel |
| AI answers from your own business, documents and web pages | — | Add-on, $5 | Bought separately, on any plan. Written by Connections AI, naming its source, or saying it does not know |
| AI answering in the ticket, message by message | — | Add-on, $5 | The same add-on. Steps aside the moment your team replies or the member asks for a person |
| An MCP server for AI assistants | ✓ | ✓ | Access tokens from the dashboard, checked against Discord and never more than a minute old. The incumbent has none |
| A public API with an OpenAPI description | ✓ | ✓ | Generated from the route table, at /api/openapi.json. The incumbent publishes neither |
Free and Premium marks follow the shape of the market's established pricing so a comparison is like for like.
Two honest caveats. Queue boost is built and not yet for sale: where a member's payment goes is still being settled, so the ladder can be configured and nothing can be bought. And the interface ships in 33 languages: fifteen cover every message the bot sends, the other eighteen cover the basics and show English where a line is not yet translated.
Put it on a server you own
Nothing is written to a server until you add the bot, and the invite lists every permission with a reason before you approve it.