Guide · Capture and extraction
Discord ticket bot: capture drafts from a server
A Discord ticket bot turns server conversations into reviewed work items. Relay is a first-class Discord app that captures a mention or a reaction, drafts a ticket with the source line attached, and posts an embed for review. Nothing reaches a tracker until a person approves the draft.
What does a Discord ticket bot do?
The bot reads the messages you point it at and extracts candidate tickets from them. Each draft carries the evidence line, a type, a priority, a suggested owner and a destination. The review surface is a Discord embed with buttons and modals rather than a separate dashboard, so the team decides in the channel where the work was discussed. Relay produces drafts; the approval decision stays with a person.
How do you capture a ticket in Discord?
- Mention the bot.
@Relaycaptures the recent message window. - React to a message. A ticket reaction captures that single message.
- Log inline. A
/relaysubcommand captures text you supply. - Review the embed. The draft appears with its evidence and actions in the channel.
All three capture paths follow the same pipeline, so the destination tracker does not depend on how the note arrived.
What can a reviewer do?
Embeds expose Approve, Edit, Reject, Delegate, Change owner and Merge actions, with modals for the fields that need correcting. Rejections record a reason as feedback. Reminders respect working hours, and a reviewer can snooze them while away. Low-risk drafts can be batched under policy, while anything risky gets individual attention. The tracker link is posted back to the thread after approval.
Which commands are available?
The slash commands cover status, queue, ownership, explanations, memory and connections. They are the quickest way to inspect what the bot has captured without leaving the server.
| Command | What it shows |
|---|---|
/relay status | Workload, queue and pushed count |
/relay who | Capacity and time away |
/relay why | Why an owner was suggested |
/relay decisions | Recent decisions and their sources |
/relay commitments | Open commitments, with overdue flagged |
What does setup need?
An admin links Discord identities to Relay members, then configures a tracker and a review policy before inviting the bot. Setup details and required scopes are in the Discord guide in the repository. Simulated payload tests run without credentials; a real workspace needs its own tokens. Live smoke tests with real credentials are documented but were not part of the release checks.
Next step
Compare the Slack flow if your team uses both apps, then self-host Relay and try the bot in a scratch server channel.