Tickets from Slack. Handled in Discord.
Route Slack tickets into Discord
Maybe your internal team raises issues in Slack, but the people who resolve them - moderators, community managers, a partner team - live in Discord. Without a bridge that means copy-pasting between two chat apps and losing the thread halfway. Routing Slack tickets into Discord connects the two: a /ticket in Slack becomes a conversation in Discord, and the answer comes back to Slack on its own.
Why this pairing
Why teams send Slack to Discord
Slack and Discord are the same shape but different worlds - one internal, one community. Bridging them lets a request raised in Slack reach the people who handle it in Discord, and return cleanly, without anyone keeping two apps in sync by hand.
- Your team raises tickets in Slack with /ticket - the tool it already has open.
- Those tickets route into Discord, where your moderators or community team actually work.
- Each ticket is a separate Discord channel, so nothing gets crossed.
- Replies are delivered back to the original Slack thread automatically - no copy-paste.
How it works
One thread, both ends
Someone in a connected Slack workspace runs /ticket. InboxBarn listens over Socket Mode, captures the thread, and routes it onward without anyone touching a help-desk portal.
InboxBarn routes that conversation into a Discord server as a dedicated channel for each conversation, filed under a category you choose. 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
Connect Slack over Socket Mode
Install the InboxBarn Slack app, switch on Socket Mode, and the /ticket command is live for everyone in the workspace - no public webhook to host.
- 2
Connect the Discord destination
Authorize InboxBarn for the server your team answers from, then pick the category new conversations should land in. Per-assignee categories are supported, so each agent can have their own lane.
- 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.
200M+
monthly active users on Discord. Discord is already open on the screens of the people who answer your customers - routing to it just meets them there.
Source: Discord CEO Jason Citron, April 2024
Questions
Frequently asked
Does the Slack user need Discord?
No. They opened the ticket in Slack and get the answer in Slack. Discord is only where the resolving team works.
How does someone open a ticket?
With /ticket in Slack, over Socket Mode. The thread is captured and routed into Discord.
Where do Discord replies show up?
Back in the original Slack thread. However the answer is typed in Discord, it returns to where the ticket started.
Can I route by category?
Yes. Tickets are categorized, and each Discord destination subscribes to the categories you assign.
Keep reading
Other ways to route
Connect Slack to Discord 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.