Two doors into the same room — and why they need different routing.
Slack DMs vs. shared channels.
8 min read · CHANNELS
Slack support arrives through two doors that look identical from your side of the inbox and could not be more different from the customer's. The first is the DM: one person, one question, low ceremony. The second is the shared channel: your team and a client's team in one room, where every message has an audience.
Teams that treat the two the same get both wrong — they bring DM-speed informality into channels their biggest client's CTO is reading, or they wrap a thirty-second DM answer in account-management ceremony. The fix is to route them differently from the moment they arrive.
01
Two doors, two social contracts
A DM is private by construction. The asker expects speed and informality; nobody else will ever read the exchange. Volume is high, stakes per message are low, and the questions repeat — password resets, plan questions, the same three configuration confusions. It's the channel where good macros earn their keep.
A shared channel is a stage. It usually exists because money does — an enterprise deal, an agency relationship, a pilot with someone's procurement department watching. Volume is low, stakes are high, and silence is conspicuous: an unanswered DM disappoints one person, while an unanswered shared channel disappoints an audience, on the record.
An unanswered DM disappoints a person. An unanswered shared channel disappoints an audience.
The confusion is understandable, because both doors open into the same workspace and arrive wearing the same notification. Slack itself doesn't distinguish on your behalf — a message is a message. The distinction has to live in your routing layer, which is the real subject of this guide.
02
Route the DMs like volume
Connect Slack as a source and let DM conversations default to the general category — or billing, if you run a dedicated billing workspace door. General flows to wherever your support rotation actually looks, and the dashboard catches everything as always.
Because DM questions repeat, this is macro territory: saved replies classified by category surface on these threads automatically, and a one-line answer can go out in seconds without sounding canned. Assignment matters less here — most DM threads are born and resolved inside one shift — but anything that survives the day should get an owner at the next weekly triage pass.
One clarification that saves a lot of head-scratching: Slack can sit on both sides of your help desk. As a source, it's where these customers write in; as a destination, it's where your team can answer everything else too — support email flowing into Slack channels right alongside the DMs. The two roles never collide, because the reply invariant anchors each conversation to the customer's own door.
03
Route the shared channels like accounts
Shared channels deserve the VIP category, applied as a standing decision rather than a per-message judgment. Conversations from those channels then flow to a destination your senior people genuinely watch — the founders' channel, the account team's room, a dedicated space in your own workspace, or wherever your escalation path actually lives.
Two disciplines keep the stage calm. First, every VIP conversation gets an assignee immediately — on a stage, "someone will pick this up" reads as nobody owning it. Second, response tone is written knowing the audience: more "here's what we're doing and when you'll hear back," less "hey! taking a look." Same warmth, more spine.
Shared channels are also where assignment earns its keep across weeks rather than hours. The account's conversations should keep landing with the same person where possible — continuity is half of what the customer is paying for in that tier — and when the owner is out, the handoff is a reassignment with the whole thread attached, not a briefing document.
Tone deserves a standing decision too, rather than per-message improvisation. Write your VIP macros in the voice you want on the record — measured, specific, dated commitments — and let the category surface them only where that register belongs. The same library that keeps DM answers quick keeps shared-channel answers careful.
04
Setting up both, cleanly
- 1
Connect Slack as a source
Customer messages — DM or shared channel — become threads in your inbox, each one its own conversation with its own history.
- 2
Split the categories at the door
DM traffic defaults to general; shared-channel traffic gets VIP. This single distinction is most of the value, and it's two sentences of configuration.
- 3
Subscribe destinations to match the stakes
General reaches the support rotation; VIP reaches the people accountable for the accounts. The dashboard receives both, so neither lane can silently drop.
- 4
Reply from wherever you work
The reply invariant holds on both lanes: the customer's answer lands back in their Slack — the DM or the shared channel they wrote in — no matter where your teammate typed it.
Resist the urge to add a third lane. Teams discover the DM/shared-channel split and immediately want gold, silver, and bronze versions of it — but every lane you add is a routing decision someone has to make per conversation, forever. Two lanes match the two real social contracts; if a third genuinely emerges, the billing and sales categories are sitting there waiting. Four words have been enough for every Slack setup we've seen.
The quiet payoff arrives later, when a DM asker turns out to work at a shared-channel account, or a pilot graduates and brings a procurement audience with it. Flip the conversation's category and the routing follows — no migration, no new tool, no per-channel pricing surprise. Two doors, one room, and your team standing in the right place for whoever walks through.
Run support as one thread.
Everything in these guides assumes a help desk that never fractures a conversation. InboxBarn is that help desk — every channel on every plan, free for up to five teammates, and replies always land back where the customer started.