Private threads
DefaultA private thread opens right under your panel channel - no category to set up and no channel-list clutter, even with hundreds of tickets. Invisible to everyone but the opener and your staff.
Cleanest for busy servers
AntiLink TicketsPlus & Premium
Support that starts
in private.
Publish one clean panel and give every member a private line to your team - as a private thread or a private channel, your call. Your staff run the whole thing with /ticket, and AntiLink keeps it locked down from open to close.
No privileged Server Members Intent required.
# help-desk
How can we help-
Open a private ticket and tell our team what you need.
#ticket-184private
Thanks for contacting the team. Please describe what you need help with.
/ticket claim/ticket add/ticket close
Threads or channels
Your desk, your way.
Pick per panel. Same private, staff-gated ticket either way - only the shape changes.
Private channels
ClassicA private text channel per ticket, filed under a category you choose. More visible and permanent, organized exactly how your team expects a support desk to look.
Familiar and organized
Command it
Run every ticket with /ticket.
Configure panels in the dashboard, then let staff operate right inside the ticket. Seven subcommands, all staff-gated.
/ticket close
Close the ticket, with an optional reason for the log. The opener or staff.
/ticket add
Pull another member into the ticket.
/ticket remove
Remove someone from the ticket - never the opener.
/ticket rename
Rename the ticket on the fly.
/ticket claim
Take ownership of the conversation.
/ticket unclaim
Hand it back to the team.
/ticket transcript
Save the styled HTML transcript to the log channel on demand.
/ticket blacklist add
Block a user or role from opening tickets.
/ticket blacklist remove
Unblock a user or role.
/ticket blacklist list
See everyone currently blocked.
Configure in the dashboard, operate with /ticket.
A short path from question to answer
A member opens a ticket
One click on the panel opens their private ticket - a thread or a channel, whichever you chose. Duplicate clicks return them to the one they already have.
Your team takes ownership
Configured staff roles see the ticket, claim or unclaim it, and add or remove members with a slash command.
The opener or staff closes it
Close from the button or /ticket close. AntiLink saves a styled HTML transcript, plus a shareable online copy, to your log channel first, then clears the ticket away.
Every conversation, saved
Transcripts you can read and share.
Close a ticket and AntiLink captures it as a clean, styled web page - then hosts a shareable copy and lists it in your dashboard. Never a plain text file again.
Styled HTML, not a text dump
Every closed ticket becomes a self-contained web page - avatars, colored names, UTC timestamps, code blocks, and real @mentions and #channels resolved to names. It lands in your log channel as a .html file you can open in any browser.
A shareable online copy
Paid tickets also get an unguessable link to a hosted copy, kept 7 days on Plus and 30 days on Premium, then cleared automatically. Send a teammate the link instead of making them dig through the log channel.
Browse them in the dashboard
A Ticket transcripts page in your account: pick a server and see every hosted transcript, newest first, each one a click from opening. No hunting through Discord.
AntiLink ticket transcript
Acme Support #ticket-184
6 messages · generated 2026-07-23 00:13 UTC
Nova23:46 UTC
Thanks for reaching out! @Support is on it.
timeout23:47 UTC
Perfect, thank you! Details are in #billing.
Generated by AntiLink · a labelled record, not a live copy
Privacy and guardrails
Private by construction, not by convention.
Tickets hold the conversations members expect your team to protect. AntiLink builds that protection into the ticket itself - and into every command that touches it.
Private from the first second
Threads are private by construction; channels deny @everyone in the creation request itself. Either way there is no public window - only the opener, configured staff, and the serving bot get in.
No message database
AntiLink stores ticket state and IDs, never the conversation. Paid transcripts are generated on close or on demand as a styled HTML page and sent straight to your log channel.
Staff-gated commands
Every /ticket action re-checks who is asking. Only the opener can close their own ticket; add, remove, rename, claim, and transcript are staff-only, always.
Blacklist the flooders
Block a user or a whole role from opening tickets with /ticket blacklist (or the dashboard). Blocked members are turned away before a ticket is ever created - so no one can spam your desk.
Live permission checks
Every publish and open re-checks the current plan, the message binding, the staff roles, and the exact channel or thread permissions the bot needs.
Included with AntiLink Plus and Premium.
AntiLink Plus
5 panels
- Private threads or channels, your choice per panel
- The full /ticket command suite
- Up to 10 staff roles and 250 open tickets server-wide
- Custom panel colors, styled HTML transcripts, and shareable online copies
AntiLink Premium
10 panels
- Everything in Plus, with double the panel limit
- The same staff roles, colors and transcripts
- Hosted transcripts kept 30 days instead of 7
AntiLink Tickets
Give every question a private place to land.
Upgrade to Plus or Premium, pick threads or channels, choose your staff roles, and publish your private support desk.