Desk documentation
Give members a private support channel and close tickets without deleting their history.
On this page
A ready workspace for Desk.
Sign in as the server owner or with Manage Server permission. Open Desk, choose the correct server inside the app, and check its connection. Each app needs its own Discord installation consent.
New to Guildryx? Follow Getting started first
Configure the required channels, roles, and access before enabling and saving. Saving applies to this app in the selected server.
Set the support destination
- Install Desk. In its workspace, choose Ticket category and Support staff role, then enable Desk and save.
- Allow Desk View Channel, Send Messages, Read Message History, Manage Channels, and Manage Roles in the category. Manage Roles is used for ticket permission overwrites, not for granting member roles.
- Choose an ordinary, available support role. Tickets are accessible to the requester, that role, and Desk; Discord administrators can also access them.
Open and handle a ticket
- A member who has finished screening and is not timed out uses /desk-open inside the server.
- Desk returns a link to the private ticket channel. The member explains their problem there and your support team replies.
- Each member can have one open ticket. Using the command again returns the existing ticket instead of creating another.
- The server can have up to 50 open tickets. Close finished requests to make room for new ones.
Close without losing the conversation
- Inside the open ticket channel, use /desk-close. The requester, its support team, server managers, and owner can close it.
- The requester keeps read access but cannot send new messages. The Discord channel and conversation remain; this is not a transcript export.
- Closing existing tickets remains possible while new tickets are paused. Desk still needs Manage Roles in the ticket channel.
- Closed-ticket metadata expires after 90 days. That cleanup does not delete Discord channels or their history.
Commands & controls
Use these controls for the current release inside the relevant Discord server. Discord’s command picker supplies required options; app-specific permissions still apply.
/desk-openOpen a private support ticket, or find your existing open ticket.
/desk-closeClose an authorized ticket while retaining the conversation.
What this app needs and keeps
Discord access
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.
Stored information
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.
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.
Troubleshooting
Desk cannot create a ticket
Check the saved category, support role, all required category permissions, and Manage Channels for Desk. Finish screening or wait for a timeout to end before opening.
A previous ticket cannot be confirmed
Ask a manager to inspect the existing Desk channel and ticket state. Repeated attempts do not safely solve an uncertain channel creation.
A ticket cannot be closed
Run /desk-close inside the recorded ticket, check you are its requester, staff member, or manager, and restore Desk’s Manage Roles access there.
Still stuck? Check Service Status, then contact private support with the app, server ID, and the error. Never send a password, bot token, or backup code.