Private support channels
A member can use /desk-open to create a ticket with access for the requester and the configured support role. Desk applies explicit private channel permissions; Discord administrators can still access the channel.
Give help requests a private home. Desk opens a support channel for the member, your selected staff role and the bot, then closes access without deleting the conversation history.
For gaming communities, creators, membership groups, and teams that need organized help without exposing a member’s request to ordinary server members.
A dedicated conversation makes the request easier to follow and keeps useful context available after it is closed.
These are the features you can configure and use in the current release. Installation and the required Discord access are still needed.
A member can use /desk-open to create a ticket with access for the requester and the configured support role. Desk applies explicit private channel permissions; Discord administrators can still access the channel.
Desk checks for an existing open ticket rather than creating repeated channels for the same requester. This keeps the first support workflow manageable for staff.
Use /desk-close to make the requester’s closed ticket read-only and retain its messages in Discord. Closing is not a destructive delete or an exported transcript.
Desk provides one open ticket per member, private support channels and non-destructive closure. It does not provide ticket departments, custom intake forms or searchable transcript exports.
Here is how the current feature fits into a real community workflow.
Read the Desk guideThey open a ticket with /desk-open in your server.
Desk creates a private conversation for the requester and the selected support role.
After helping, staff close the ticket; the conversation remains in Discord and the requester becomes read-only.
Good tools should explain what they need, what they store, and what they leave under your control.
Desk needs channel access, message-history access, Manage Channels, and Manage Roles for channel permission overwrites. Manage Roles is used to control ticket access; it does not authorize Desk to give members new roles.
Desk stores ticket channel, participant, and state references. It does not copy message transcripts in the current release; closed-ticket metadata is cleaned after 90 days, while the retained Discord channel is not automatically deleted by that cleanup.
Each app has its own Discord installation consent and server-specific settings. Available features stay free. Installing an app does not authorize every module; enable only the features you want and save deliberately.
Explore trust & safetyInstall Desk and review the permissions required for private ticket channels.
Choose the ticket category and a suitable support staff role in its workspace.
Enable and save Desk, then explain the open and close commands to your members and staff.
The important details, without hidden assumptions about what is ready.
No. The requester becomes read-only, and the messages remain in the Discord channel. A separate deletion workflow is not part of this release.
Yes. Discord Administrator access bypasses ordinary channel restrictions. Desk cannot make a ticket invisible to server administrators.
No. Current messages stay in Discord. Transcript copying, export and search are unavailable.
Choose only the apps your community needs. Related apps have separate setup and permissions; an automatic connection between them is not enabled by installing both.
Choose the features your community needs, follow the setup guide and save your server’s settings.
