Quickstart

Prerequisites

• You have Manage Server permission in Discord (or equivalent) for the server you’re connecting.
• You know where you want tickets to live (private channels per ticket or private threads).
• You’ve identified at least one staff role to act as agents (e.g. @Support).

Step 1: Create a workspace

1. Open the Stavent dashboard and create a new workspace (example: Acme Support).
2. Add your Discord server under Settings → Connections.
3. Pick your ticket mode: Private channels (recommended for larger teams) or Private threads (recommended for lightweight setups).

Step 2: Invite the bot

Invite Stavent with the bot and applications.commands scopes. Use the recommended permission set so the bot can create channels/threads, post messages, and update ticket metadata.

Scopes:
- bot
- applications.commands

Optional:
- webhook.incoming (if you want Discord->Stavent webhook shortcuts)

Step 3: Create a ticket form

Forms are how you capture structured context before an agent ever opens the conversation. Stavent supports dropdowns, short text, long text, and file attachments.

1. Go to Tickets → Forms and click Create form.
2. Add fields like Order ID, Issue type, and Impact.
3. Publish the form to a Discord channel as a button panel (example: #support).

Step 4: Route to a team

Routing rules decide who sees what. A simple starting point is to route by issue type.

Step 5: Test the flow

1. Submit the form from a non-staff test account.
2. Verify the ticket creates in the right place, with the right privacy (only requester + agents).
3. Reply as an agent and close the ticket. Confirm a transcript is generated and stored per your retention settings.

Pro tip: open two browser windows and a Discord client so you can watch the ticket lifecycle in real time.

Next steps

• Add automation rules to triage and tag tickets.
• Configure audit logs for compliance and incident review.
• Generate API tokens and integrate with your tools via webhooks.