B2B customer support software: a shortlist for shared Slack channels

One test splits this market: can a person in another company’s Slack workspace, in a channel you don’t own, reach a working intake and get a reply back without a seat in your help desk? Everything else, price and reporting included, comes after it.

This page is published by one of the vendors in the table. That vendor’s claims get the same checks as everyone else’s, and where I only have its own product description, the page says so. Prices are USD list prices from each vendor’s own pricing page, as of 2026-11-11.

Start with the Slack Connect test

Slack’s help guide says both organizations need a paid Slack plan to share channels. It also says you can start a DM on any plan, so a free-plan customer can reach you by DM but not in a shared channel. Check the customer’s plan before you promise them a channel.

The shortlist rule:

• If most of your customers are in Slack, drop any tool without a documented Slack Connect path first.
• Only then compare account structure, SLA basis and price across what remains.

Don’t rank a cheap tool above a native one. A tool that reaches Slack customers only through a shared email alias is a second inbox with a Slack sticker on it.

The test that settles it is a recording. Ask the vendor for a screen recording of a person from an outside company posting in a Slack Connect channel you don’t own, with the ticket appearing in the vendor’s queue and no seat for that person in the tool. A written yes without a recording doesn’t count.

Where each tool lands on the rule

• Zendesk: passes, with limits. Its Slack article documents Slack Connect channels. Support Team is a listed plan, so the integration doesn’t require a Suite tier. The article doesn’t mention an extra charge for the integration; confirm that in the quote.
• Intercom: not shortlisted yet. The Channeled article I read doesn’t mention Slack Connect, and the app is a paid add-on whose price the article doesn’t state. It stays out until a recording shows a shared channel working.
• The publisher’s tool: documented by the publisher only. Its product facts say every customer message in a shared channel becomes a thread in one queue, and replies post back under the replying person’s own name. I haven’t seen a third-party recording, so it gets the same recording test as the others.

Result as of 2026-11-11: one tool passes on public documentation, one passes on its maker’s description, and Intercom is held out. If your list is longer, run the same recording test on each name, starting with the ones whose docs never say “shared channel” or “Slack Connect”.

What the documented tools allow in shared channels

Zendesk’s Slack article says people on both sides of a Slack Connect channel can create tickets with the @zendesk mention. The limits matter for an operations lead. External users don’t get the Assignee field on the new-ticket form, they can’t use the global shortcut command, and the integration “only allows tickets to be assigned to a group.” An outside customer can open a ticket but can’t name an individual owner, so route by group. It also says that if an unrecognized user creates a ticket in Slack, “a new Zendesk Support end user is created”. Each new contact becomes a new end user, so check how that user is tied to the customer’s company before you report by account.

Intercom’s Channeled app runs in one of two modes, and the mode decides how many requests reach your queue:

• Automated. Per the article, each customer message in a connected channel creates a conversation. Every message is a request, including thank-yous.
• Manual. An emoji reaction, an @mention or a keyword starts a conversation, and the article says some Slack threads then never become conversations.

Decision rule: if most messages in your channels are requests, pick automated. If customers chat in the same threads, pick manual and agree on the one reaction your team uses. Failure mode: in manual mode a request nobody reacted to never enters the queue, and the queue looks quiet while customers wait. Fix: once a week, count Slack threads that have no conversation and compare that with your queue.

Multi-contact accounts and the SLA clock

A B2B customer is an account with several contacts, often spread across channels. Three checks decide whether a tool fits.

• Grouping. Does a message from any contact land under the same account record? The publisher’s product facts say a customer belongs to an account. The Zendesk Slack article I read doesn’t mention organizations, so ask Zendesk how a Slack contact is linked to one. If each contact becomes a separate customer, every account-level report is wrong from the first week.
• SLA basis. Zendesk’s SLA article says policies set “response, update, and resolution targets for tickets”, so the basis is per ticket, which in practice means per request. It lists SLA support under Suite Growth, Professional, Enterprise and Enterprise Plus, and under Support Professional and Enterprise. Support Team and Suite Team aren’t listed. The publisher’s SLA and escalation features are marked as planned, not live, so don’t buy it for contractual timers today. Worked example: an account with three contacts posts four separate requests within one hour. Under a per-request one-hour first-response target that is four clocks. Under a per-account target it would be one. Pick the basis before you quote “one hour” to a customer, and write it into the contract.
• Start and stop. Confirm the timer starts at the customer’s first Slack message in a new request, not when someone on your team notices it. The SLA first response time guide covers the start and stop rules.

AI agents add a fourth check. If an agent replies in the channel, decide whether its replies count as a first response, and report human and AI first responses separately. Then ask each vendor in writing whether an AI agent that replies counts as a seat.

Failure mode: the vendor says it supports SLAs, but the timer only runs on tickets created by hand, not on Slack threads. Fix: ask for a demo where a message is posted in a Slack Connect thread and the timer starts from that message.

Per-seat list prices at 5, 15 and 40 agents

The table uses annual billing, monthly USD, before tax and before any add-on. The publisher’s pricing page doesn’t show monthly-billed Starter or Growth prices, so there is no monthly column.

Intercom has no row because I did not verify a price for it. I did not verify the Zendesk Suite Growth price, the cheapest Suite tier whose docs list SLAs, so ask for it.

Worked example at 15 agents, same vendor. Zendesk Suite Team is 15 × $55 = $825 a month, and Suite Professional is 15 × $115 = $1,725 a month, so the step up costs $900 a month. The publisher’s Starter to Growth step at 15 seats adds $750 a month. Compare steps inside one vendor, not across vendors, because the tiers hold different features. Before you move up, name the feature you need and confirm it is on the vendor’s page the day you sign.

Worked example on seat units. A team of 40 where 12 people reply to customers pays for 12 seats on a per-replier tier: 12 × $89 = $1,068 a month, not 40 × $89 = $3,560. Zendesk’s page prices per agent, so confirm in writing who counts as an agent.

Questions to send before you sign

Send these in writing. Vague answers are the signal.

• “Show us a screen recording of a person outside our workspace creating a ticket from a Slack Connect channel we don’t own, with no seat in your tool.”
• “Can someone outside our workspace set the assignee? If not, which fields can they set?”
• “Is the SLA timer per request, per contact or per account, and does it start from a message in a Slack Connect thread?”
• “Does an AI agent that replies in the channel count as a seat, and do its replies count as a first response?”
• “Does any Slack feature carry a separate charge, and what is the annual price?”

Failure modes and fixes

• The demo works, the customer channel doesn’t. Many demos run in a channel the vendor’s team owns. Fix: run one test in a channel the customer created, with a contact on a paid Slack plan, before the trial ends.
• Replies come from a generic bot name. Customers can’t tell who is answering, and escalations stall. Fix: ask which identity posts the reply, and read one reply the way the customer sees it.
• The seat count is headcount, not reply seats. At 12 repliers out of 40 people, the quote differs by $2,492 a month at $89 a seat. Fix: count reply seats for the quote, and recount every 90 days.
• A cap, add-on or plan gate appears after onboarding. Fix: write the seat cap, the channel limit, the add-on price, the plan that includes SLAs and the SLA basis into the order form, not just the pricing page.