Ticket Bot

The Ticket Bot lets members open a private support channel by clicking a button. Each ticket is a hidden channel only the opener and your support team can see, with built-in claim, close and transcript.

Paid plugin — included from Link. The Ticket Bot needs a Link subscription ($3.99/mo) or higher on that network; Network and Grid include it too. See pricing.

Re-invite required. Tickets create channels, so the bot needs the Manage Channels permission (and Attach Files for transcripts). If your bot was invited before this feature, re-invite it from the dashboard — the button uses the updated permissions.

Create a panel

In the Tickets tab → New panel:

• Title / description — shown on the panel embed.
• Post the panel in — the channel where the button lives.
• Button label / emoji — e.g. “Open a ticket” 🎫.
• Support roles — these roles get access to every ticket and can claim/close.
• Ticket category — new ticket channels are created under this category.
• Transcript channel — where the HTML transcript is posted on close.
• On close — see below.
• Naming — ticket-0001 or ticket-username.
• Max open tickets per user — stops one person opening dozens.
• Opening message — posted inside each new ticket ({user} mentions the opener).

The bot posts the panel automatically and the button keeps working across restarts.

Opening, claiming, closing

• A member clicks the button → the bot creates a private channel, pings the support roles, and posts Claim and Close buttons.
• Claim marks a staff member as the owner of the ticket.
• Close archives the ticket (see below) and then, depending on the panel's close mode:
  • Lock & delete button — the channel is locked (the opener loses access) and staff get View transcript and Delete buttons. The channel itself stays as the record until someone deletes it.
  • Delete immediately — the channel is deleted right away. Only what was archived beforehand survives.

Transcripts & privacy

A transcript is generated as an HTML file and posted to your transcript channel — and, if you turn it on, DM'd to the opener as well. Message content is never stored in CloudMod's database; the transcript only ever lives in the file posted to Discord. Very long tickets are capped to keep the file within Discord's upload limit.

Set a transcript channel before using "Delete immediately"

A transcript channel is optional and not set by default. Without one — and without the DM copy — nothing is archived anywhere.

With Lock & delete button that is survivable: the ticket channel stays, so the history is still there. With Delete immediately it is not: closing a ticket discards its history for good, with nothing to recover it from.

The panel editor warns you when you pick that combination. Run /ticket diagnose to check that CloudMod can actually post in the channel you picked — it needs View Channel, Send Messages, Embed Links and Attach Files there. Missing any one of them means the transcript never arrives.