Community in Discord. Team in Slack.
Bring Discord tickets into Slack
Your community lives in Discord. Your team works in Slack. That split is fine until support starts flowing - and then someone is babysitting a Discord tab all day, or worse, missing messages in it. Routing Discord tickets into Slack lets members ask for help where they already hang out, while your team answers from the workspace where it actually gets work done.
Why this pairing
Why teams send Discord to Slack
Discord is unbeatable for community; Slack is where internal work happens. Bridging them means you don't have to ask your team to live in Discord all day, or ask your community to file a ticket somewhere cold. Each side stays in the tool it prefers.
- Members open a ticket with /ticket - no account, no portal, no leaving the server they're in.
- Your team answers in Slack, the tool it already has open, instead of monitoring a Discord channel.
- Each Discord ticket becomes its own Slack conversation, so handoffs and assignments stay clean.
- Two communities, one workflow: support from Discord lands beside everything else your team handles in Slack.
How it works
One thread, both ends
A member runs the /ticket command inside your server. A private thread opens for them, and everything they type from that point on flows straight to your team.
InboxBarn routes that conversation into Slack as a channel per conversation in the workspace your team already lives in. Your team reads it and answers it right there, in the tool they already have open - no portal to log into, no queue to refresh.
The reply always goes back on the channel the customer used.
Setup
Set it up in three steps
- 1
Install the bot and turn on /ticket
Add the InboxBarn bot to your server (it needs the Manage Roles permission), and members can open a ticket with one slash command - no leaving Discord, no signup.
- 2
Connect your Slack workspace
Authorize the workspace and choose where routed conversations should appear. Your team replies in the channel; the customer never sees Slack.
- 3
Pick a category and go live
Map the source to a routing category (general, billing, VIP, sales) and point your destination at it. Send a test message - it should appear on the other side in seconds, and your reply should land right back where it started.
77 of the Fortune 100
use Slack. Slack is already open on the screens of the people who answer your customers - routing to it just meets them there.
Source: Slack, 2024
Questions
Frequently asked
Do members need Slack?
No. Members stay in Discord the whole time. Slack is only where your team answers - the reply appears back in the member's Discord ticket thread.
How do members start a ticket?
They run the /ticket slash command in your server. A private thread opens, and everything they type flows to Slack.
Where do my Slack replies show up?
In the member's private Discord ticket, always. However your agent typed it, the answer is delivered back on Discord, so the member sees one continuous conversation.
Can I route some tickets to different Slack channels?
Yes. Tickets are categorized, and each Slack channel subscribes to the categories you choose, so VIP or billing can have a dedicated channel.
Keep reading
Other ways to route
Connect Discord to Slack today.
Every channel is included on every plan - no per-channel taxes. Wire up the bridge in a few minutes and answer your customers from the tool your team already lives in.