Ticketing — support workflow builder

What it is
Full-featured ticketing: staff-facing panels that open ticket channels, support claims, transcripts, per-ticket participants and more. Panels and ticket metadata are persisted so they survive restarts.

Where to find it
Setup → Ticketing in the Features section.

Key UI elements

• Panel + Routing: panel title, description, destination channel/category (where new tickets are created), a mention role, and button label/emoji.

• Panel controls: preview of live tickets, a list of panels on the right (Live / Draft), and buttons to Copy / Create as Draft / Push Panel (push = publish to Discord).

• SLA / Auto-close / Transcripts: set auto-close windows and whether to log transcripts to your log channel or DM staff.

• Live tickets: view currently open tickets, claim/close from the dashboard view.

Important slash commands

• /ticket setup — initialise roles, category and open button. (Options: panel-title, button-emoji, mention-role, etc.)

• /ticket category — set the ticket category (channel) for new tickets.

• /ticket close, /ticket add, /ticket remove, /ticket rename, /ticket claim, /ticket unclaim, /ticket transcript, /ticket list, /ticket settings — day-to-day ticket operations.

• Panel management: /ticket ticketpanel create, /ticket ticketpanel addbutton, /ticket ticketpanel delete, /ticket ticketpanel list — for posting and editing panel messages.

Persistence note
Ticket channels, roles and panel metadata are stored under data/ticket*.json so panels survive bot restarts. This is useful during large launches: you can safely push/populate panels and rely on persisted metadata.

How to use it (quick flow)

1. Build a panel in the dashboard: give it a clear title, a short description telling members what to include, and choose the destination category/channel.

2. Configure button label/emoji and a mention role (optional). Enable Auto-assign on open or Claim on first reply as needed.

3. Preview the panel, then Create as Draft (if you want review) or Push Panel to publish the message to Discord. Staff can also create/manage panels directly via /ticket ticketpanel commands.

4. After panels are live, use the Live tickets view to monitor open tickets and the ticket list command to find active tickets.

Tips

• Use the mention role sparingly — pinging a large role for every ticket can cause notification fatigue.

• Enable transcripts for support processes that require record keeping; transcripts are generated with /ticket transcript.

• Use drafts and copy/paste options to duplicate panels for different support channels.

Reaction Roles — role palette builder

What it is
A visual builder to create select-menu or reaction-based panels that let members self-assign roles. Panels can be previewed, edited, and pushed to Discord. The dashboard mirrors the /reactionroles flows so staff can stage changes first.

Where to find it
Setup → Reaction Roles.

Key UI elements

• Build a panel: panel title, description, channel destination, and role options (each option: role, label, description, emoji).

• Panel preview: how the panel will render in Discord (use this to sanity-check layout and wording).

• Push to Discord / Copy command: publish the panel message or copy the command you can paste into Discord.

• Existing panels: pull a panel by message ID to edit or re-post; sync with Discord if you have pre-existing panels.

Important slash commands

• /reactionroles — post a new reaction-role panel (title and options are provided). Note: role IDs are persisted in data/reactionRoles.json.

• /reactionroles-view — fetch an existing panel by message ID for editing or removal.

How to use it

1. Create a role palette with clear labels and concise helpers (e.g., “Matchmaking pings — queue nights & scrims”).

2. Use the Panel preview to check ordering and emoji.

3. Push to Discord from the dashboard or run /reactionroles from Discord (the dashboard can generate the command for you).

4. To manage live panels, paste the message ID into the “Existing panels” area and sync/edit as needed.

Tips

• Allow members to pick multiple roles if the categories are non-exclusive (the system supports multi-select).

• Keep role descriptions short; they appear in the preview and help members identify the right choice.

Moderation — quick actions, automod & raidshield

What it is
Centralised control for manual moderation (ban/kick/mute/warn/clear/etc.), the auto-moderation rule matrix, raidshield/auto-shield posture, logs, and a digest. Quick actions in the dashboard map directly to /moderation commands so staff can stage actions without opening Discord.

Where to find it
Setup → Moderation.

Key UI elements

• Quick actions: big buttons for /moderation ban, /moderation kick, /moderation mute, /moderation warn, /moderation clear. These let staff stage commands with an audit note.

• Auto-mod matrix: configure rules (spam/links/profanity/raids/scam phrases), thresholds, automatic action and logging destinations. The dashboard shows staged vs live state so staff can preview before pushing.

• Shield mode: a single posture to harden the server during raids (often combined with short spam windows and stricter auto-mod rules).

• Escalation & logging: configure strike paths, webhook sinks for leadership, and a moderation digest schedule.

Important slash commands

• /moderation ban user:<user> reason:<reason> — ban a user. Example shown in UI.

• /moderation automod rule:<rule> action:<action> threshold:<n> duration:<duration> — configure auto-mod rules; these map to the matrix in the dashboard. Example syntax: /moderation automod rule:spam action:timeout threshold:3 duration:30m.

How to use it

1. Use Quick actions to stage a ban/mute/etc. and add an audit note; staged actions remain visible until pushed.

2. Configure your Auto-mod matrix: set rule actions (timeout, mute, warn), thresholds, and where to log. Use the preview to verify behavior.

3. Toggle Shield mode when under active attack to apply aggressive automations and deny new messages/joins as required.

4. Set a Log channel and digest time so leadership receives summaries and automated logs.

Tips

• Stage automod changes and test them on a single channel before rolling them server-wide. The staging model reduces accidental misconfiguration.

• Use strike paths (warn → timeout → ban) to create predictable escalation and a clean audit trail.

Announcement / Embeds — stage & push rich messages

What it is
Compose and stage rich announcement embeds (title, body, attachments, channel destination) and optionally stage them locally before delivering. The dashboard staging keeps embed metadata local while bot-side delivery handles uploads. This lets staff craft messages safely without immediately notifying the whole server.

How to use it

1. Build an embed in the dashboard, add attachments and choose the destination channel.

2. Preview the embed and iterate in staging. Because embed metadata is local to the dashboard, you can refine copy and assets before pushing.

3. Push the embed live when ready or schedule/automate posting if your workflow requires it.

Tips

• Use the dashboard to test different headlines and bodies with staff in a private channel before publishing to the community.

• For large announcements, test image attachments and how they render across desktop/mobile.

Workflows & best practices

• Staging-first approach: use dashboard drafts and staging for embeds, ticket panels and automod settings; preview and test in a limited channel before publishing. (The dashboard explicitly supports staging of embeds and keeps metadata local.)

• Ticketing + staffing: set mention-role and Claim on first reply appropriately so tickets are routed to the right team; ensure your ticket category has staff access to the channels.

• Moderation safety: stage automod changes and test on low-traffic channels. Enable raidshield only when you’ve validated thresholds to avoid false positives.

• Role palette hygiene: name roles clearly and limit role counts per panel to keep the UI scannable for members.

Technical & persistence notes

• Ticketing data (channels, roles, panel metadata) is persisted to data/ticket*.json so setups survive restarts.

• Reaction-role mappings are persisted to data/reactionRoles.json. This lets members keep role state even if the bot restarts.

Troubleshooting checklist

• Panel doesn’t show in Discord after push — check that the bot has permission to post in the target channel and that the channel/category is correctly selected in the panel settings. Use the ticketpanel list or /reactionroles-view with the message ID to inspect persisted panels.

• Tickets not being created — ensure a ticket category exists and is selected (set via /ticket category) and verify the bot has Manage Channels permissions for the category.

• Role pickers not working — confirm role IDs are valid and the bot can manage the role, and re-push the panel from the dashboard. Persisted role IDs live in the data/reactionRoles.json file.

• Automod false positives — decrease sensitivity, test in a staging channel, and review logs/webhooks to debug thresholds. Use /moderation automod to tweak rules.