AI customer support software for Slack and email teams

This page is published by Weft, one of the tools compared here, and its row follows the same rules as the others. I read each vendor’s own pages in November 2026 and used only the prices and statements on them. Five tools is a shortlist, not a survey. Where a page shows no price, the table says so.

Test one: does the AI work inside a Slack Connect thread?

Slack’s help article says the feature is “Available on paid plans” and is open to All Full Members by default, so a free workspace cannot run this test. A Connect channel can host up to 250 organizations, including your own. You cannot add external people to #general or #all-companyname, and when you invite someone you choose “Can post & invite” or “Can only post”.

Fin’s Slack page answers in its FAQ: “Yes. Fin works in both Slack communities and dedicated Slack Connect channels.” It adds that in Connect channels Fin “resolves customer questions in the shared workspace between your team and the customer’s team”, and that when it cannot resolve an issue it “hands off to a human agent with full context.” Those are vendor claims, so they go into the trial.

Intercom’s native Slack article says a new conversation opens when a customer posts in a connected channel. The text I read does not say whether shared Connect channels are supported, so ask Intercom in writing.

Zendesk’s Slack integration article is written for Customer Service Suite accounts, says the integration cannot be installed on a shared Slack workspace, and does not mention Slack Connect. Help Scout’s pricing page does not mention Slack. ClearFeed’s pricing page describes its helpdesk as supporting customers via Slack Connect, Teams, Email and Chat.

None of the pages I read say how a first-response or resolution timer runs on a Connect thread. That is the open SLA question for shared channels, so put it in the trial: ask which timestamp starts the clock and whether a customer’s “thanks” reopens the thread.

Decision rule: if the vendor cannot show a live Connect thread that holds the AI answer, the human handoff and the customer’s reply together, treat its Slack Connect claim as unproven. A claim that rests only on a marketing page counts the same way.

Test script: in a test shared channel, send one question the AI should answer and one it should not. Pass only if both stay in one thread, the handoff names the person who took over and sets an assignee, and the customer’s reply lands under that same message. A second thread opening is a failure.

Test two: who does the customer see replying?

Fin’s replies come from the Fin bot. A teammate’s replies show their own name and picture. A teammate who connects their own Slack account gets replies from their own Slack identity rather than from Fin, and connecting requires the Can manage workspace data permission.

The publisher’s inbox says on its home page that replies go out under the agent’s own name and avatar, not a bot account. Zendesk and Help Scout pages I read say nothing on this, so ask.

Failure mode: the customer sees a bot where they expected a rep. The gap usually sits in attachments: Intercom’s article says non-image attachments from an unconnected teammate appear from the Fin bot.

Fix: send a PDF from a rep who has not connected Slack. If it arrives from the bot, connect that rep’s account and re-send. When a teammate takes over, say so in the thread: “I’m bringing in Dana from our team, who has your account history.” When a file does come from the bot: “The file above came from our support assistant, not a person. It’s the one you asked for.”

Test three: what the bill looks like at 300 a month

Price every option at five repliers and 300 AI-handled conversations a month, in USD list prices before tax. Vendors bill different events, so the table shows 300 billable and 180 billable, where 180 means the rest went to humans or fell outside that vendor’s rule. Totals are arithmetic on list prices, not quotes. Fin’s Intercom price is shown as “From $0.99”, so its totals are floors.

Zendesk’s page does not say which billing period the $1.50 rate applies to, and Fin’s and Help Scout’s pages do not state one for their per-outcome prices, so ask before comparing.

How to map your 300: for Zendesk and Help Scout, count only conversations the AI closed with no human touching them. For Fin, count every conversation that ends in a listed outcome: its page lists resolutions, qualifications at $9.99 each, Procedure handoffs, disqualifications and self-serve routings. A mix of 240 outcomes at $0.99 and 60 qualifications at $9.99 is $237.60 + $599.40 = $837.00 before seats. Pull the real mix from a week of your own logs.

Choosing by team size, as judgment rather than vendor guidance:

• Up to 5 repliers: seat cost is small, so the billing rule decides. Pick the vendor whose billable event matches how you would count a win, and avoid a minimum like Fin’s 50 outcomes a month if your AI volume is uncertain.
• 5 to 20: seat cost grows with headcount, and a per-resolution charge stays flat if AI volume is flat. Price both at your real volume with the seat counts you will have in a year.
• Over 20: negotiate. List prices above are a starting point, and the counting rule matters more than the rate.

Who is not built for a Slack-first team

• Zendesk is a ticketing system with a Slack integration attached. Its Slack article does not mention Slack Connect. Unless a trial proves otherwise, it is the wrong starting point for Connect-heavy work.
• Help Scout is not Slack-first. Its pricing page does not mention Slack and names Salesforce, HubSpot, Aircall, Jira and Linear as integrations.
• Fin with Intercom starts from the helpdesk, with Slack as a channel into it. By default each Slack workspace connects to only one Intercom workspace conversationally, and Workflows need the Advanced or Expert plan.
• ClearFeed names Slack Connect in its helpdesk description, but its pricing page shows no per-agent prices. Ask which product covers your Connect channels.
• The publisher’s inbox has no AI agent today; its Customer Agent is in development. Its home page says replies go out under the replier’s name and avatar, and that email sends from your own support address on Starter. Its pricing page defines a seat as anyone who replies to customers and offers 14 days of Growth with no card to start. I have not shown a Connect test for it on this page, so run the same test script on it and see how Connect messages are handled.

Failure modes and fixes

• The AI answers wrongly in a shared thread. Keep it in draft mode for the first two weeks and review 20 sampled threads a week. If more than one in 20 needs correction, do not let it reply directly yet.
• The handoff loses context. Run one escalation in the trial. The thread should stay the same, the last three customer messages should be visible, and an assignee should be set.
• The bill counts things you did not count. Export one week of billed items and compare them with your own list. Send any gap to the vendor with the thread links.
• Email replies come from the wrong place. Send a test email from an outside address to your support address. Check the AI reply lands in the same conversation. Email behavior for Zendesk and Help Scout is unverified here, so test it.

Setup and governance

• Knowledge. Limit the AI to articles a named owner reviewed in the last 90 days. If an answer needs a price, a refund or a contract term, the AI hands off.
• Approval. One named person signs off each reply template before go-live, and the first 20 AI replies sit in a review queue.
• Data. I did not verify vendors’ answers on this, so ask in writing: “Where are conversations from shared channels stored? Which people at our vendor can read them? Are they used to train models, and can we opt out?” Treat a missing written answer as a no.
• Trial length. Run 14 days on at least 20 real threads, and fail the tool if any check above fails.