A full helpdesk right inside your Discord.
Multi-type panels with buttons or dropdown, channel-per-ticket with auto-overflow categories, internal notes, modular pre-open fields, SLA timers, auto-close, and auto-blacklist.
What Tickets can do
Up to 25 buttons or one dropdown per panel — each entry opens a different ticket type. Embed editor with images, colors, footer.
Each ticket gets its own channel under the chosen category. At 50 channels the bot auto-spawns an overflow category. Up to 500 open tickets per server.
Per type: short text, long text, select, multi-select, number — asked as a modal before opening and posted as an embed inside the ticket.
Staff-only threads with their own visibility, stored separately in the transcript and clearly labelled in the web view.
Configurable first-response and resolution SLAs per type with mod-log escalation. Auto-close on inactivity with a grace period and a re-open button.
Coloured tags, four priority tiers, claim/unclaim by button — all visible in one embed and audited in mod-log.
Heuristics block spam openers (X tickets in Y minutes without substance). Blacklist with expiry and hit counter, manually overridable by staff.
Closing posts a link (mod-log + optional DM). The web page renders avatars, embeds, replies, attachments and username colors — like the Discord client. JSON export button on the page.
Three token scopes (staff, opener, public) with 90-day expiry. Staff tokens are server-shareable, opener tokens are personal, public tokens are issued manually.
Optional 1–5 star rating on close — directly in the archive embed; results aggregated in the analytics tab.
Per type: volume, first-response median, resolution time, claim rate, CSAT average, heatmap (weekday × hour). Export endpoint for third-party analysis.
Per server: message storage and transcript generation can be turned off. Defaults are both on but can be fully disabled for GDPR-strict communities.
In detail
Channel-per-ticket runtime
When a user clicks a panel button, the bot creates a new channel under the selected category and sets permissions: opener + staff roles see, everyone else doesn't. Pre-open fields are posted as an embed and pinned in the ticket header. On close the channel is archived (read-only for opener), then deleted after the grace period — the web transcript link stays valid for 90 days.
Discord-1:1 web transcript
Instead of an HTML file in the DM you get a link to the web viewer. There we render the conversation like the Discord client: avatars from cache, username colors from top roles, embeds with color bar + fields grid, reply arrows with truncated quote, attachments as images/videos/file cards, markdown (bold/italic/code/strike), custom emojis as inline images. JSON export for your own analysis.
Custom-bot compatible
If your server has a custom bot configured, all ticket channels, embeds, mod-log posts and opener DMs are sent through its token — your branding, your rate-limit slot.
GDPR-compliant storage
Per server you can turn message storage off — the bot then only tracks activity timestamps for SLA but doesn't persist content. With storage on, all content is wiped through the platform's auth hook (GDPR Art. 17) when the opener requests data deletion.
Frequently asked questions about Tickets
How many tickets can a server have open at the same time?
Up to 500 open tickets per Discord. Discord holds 50 channels per category — the bot auto-spawns overflow categories when needed. Per user + type the count is also configurable (default: 1 open per type).
How do transcripts work?
Every message in an open ticket (if storage is on) is stored in the database with avatar, username, role color, embeds, replies and attachments. On close the bot mints a 90-day token, posts a link in the mod-log and optionally in the opener DM. The link opens a Discord-styled web view with JSON export.
Can tickets be closed without a reason?
Yes. The close modal accepts 0–500 chars. If empty, everything works as usual — the reason is just null in the audit log.
What happens if someone deletes their account?
The auth hook places a tombstone marker on the user record. Tickets remain readable for server-owner accountability; the username is anonymized to '[deleted]'.
Does this work with custom bot?
Yes. Once you've registered your own bot via token for your server, it takes over all ticket operations — channel creation, embeds, mod-log posts, DMs.
Can I disable transcripts entirely?
Yes. Under Tickets → Settings you can turn both message storage and transcript generation off per server. Tickets still work but nothing is persisted or sent out as a web link.
Does this cost anything?
No. Completely free — all features, no limits, no premium tier.
More modules
Ready for TeraOne?
Two clicks to set up. No onboarding, no credit card.