Guide · Capture and extraction
Slack ticket bot: capture decisions in chat
A Slack ticket bot turns messages into reviewed tickets without anyone opening the tracker. Relay is a first-class Slack app: mention it in a thread, react to a message, post in a watched channel or use a slash command. Each draft carries its source quote and waits for approval before it is pushed.
What does a Slack ticket bot do?
The bot captures a message window and extracts candidate tickets from it. Each draft shows the type, priority, risk, confidence, suggested owner, due date and the evidence line that produced it. Review cards post back into the same thread, so the conversation that created the work stays next to the decision about it. Relay handles the transcription and routing; the approval remains a person's call.
How do you capture a ticket in Slack?
- Mention the bot.
@Relayin a thread captures the recent messages. - React. A
:ticket:reaction captures one message. - Watch a channel. Messages in a configured channel are captured for review.
- Log inline.
/relay logcreates a draft from text you type.
All four paths produce the same kind of draft: a ticket with a quote and a review card in the thread.
What can a reviewer do in Slack?
Review cards support approve, edit, reject, delegate, change owner and merge. Editing opens a modal for the title, description, type, priority, owner and labels. Rejecting asks for a reason, which is stored as learning feedback. Reviewer DMs respect working hours and out-of-office status, and the Home tab plus digests keep the team in sync. Batch approval handles low-risk drafts; risky ones are reviewed individually.
Slack or Discord?
Relay ships both as first-class apps with the same capture and review model. The difference is the interface each platform offers, not the ticket pipeline behind it. If your team lives in Slack, start there; the Discord guide covers the equivalent flows for server-based teams.
| Action | Slack | Discord |
|---|---|---|
| Mention capture | @Relay in a thread | @Relay mention |
| Reaction capture | :ticket: | Ticket reaction |
| Review surface | Cards with actions | Embeds with buttons and modals |
| Commands | /relay log and more | /relay subcommands |
What does setup need?
An admin links chat accounts once per person with /relay connect, configures the default tracker and review policy, then invites the bot to the notes channel. Chat tests run on simulated payloads without credentials; a separate recordable flow needs your own workspace tokens. Live chat smoke tests with real credentials are documented but were not run in the release checks.
Next step
Read the meeting-notes guide for the source side of the flow, or self-host Relay and try the bot against a scratch channel.