Claude for Slack: Claude Tag Setup, Plans & Access

Quick Answer: Which Claude and Slack Setup Should You Use?

If your organization already holds a Claude Team or Enterprise seat, use Claude Tag. It is the only option here with memory scoped to a channel and the ability to run a multi-step task without anyone staying in the thread to manage it. Everyone else needs a different answer, because Claude Tag simply is not available to them yet.

Claude Tag, Anthropic's persistent AI teammate for Slack, is built for teams already on a Claude Team or Enterprise plan that want an assistant living inside a deal or research channel. Teams on Claude Pro or Max should use Claude.ai's Slack Connector instead, since Claude Tag is not open to them during this beta. Teams with no Claude subscription at all can start with Slack's own built-in thread summaries, which ship free on every paid Slack plan. And for a single one-off summary, manual copy-paste into Claude.ai still works on any plan and needs no setup at all.

How We Compared the Four Setups

None of this is abstract. Asana's Anatomy of Work Index, a survey of more than 13,000 knowledge workers, found that knowledge workers lose almost two-thirds of their time to work about work, including chasing status updates and hunting for information across tools. That is exactly the layer these four setups compete to automate, so we compared them on what actually decides which one a team can use, not on a feature checklist.

What we ignored: general chat quality and model benchmarks, since three of the four options run on the same underlying Claude models where a model even applies, and interface polish, since neither changes which option a given team is actually allowed to use.

Key Takeaways

• Plan eligibility decides your shortlist before features do. Claude Tag needs Claude Team or Enterprise. Claude.ai's Slack Connector works on Pro or Max. Slack's own recaps need only a paid Slack plan.
• Setup ownership differs sharply. Claude Tag is paired by a Slack Owner from the Claude admin console; the Slack Connector is a five-minute, individual opt-in; Slack's AI features are already on if your plan includes them.
• Memory is the real dividing line. Only Claude Tag keeps context scoped to a channel between sessions. Every other option, including Slack's own AI, resets with each request.
• Governance has to be checked, not assumed. Audit logging, per-channel access scoping, and Zero Data Retention eligibility exist on Claude Tag today; confirm each one before routing deal or board content through it.
• Cost controls should be set before rollout. Claude Tag supports org-wide and per-channel token caps. Set them in the pilot channel, not after the first surprising invoice.

Claude Tag vs the Alternatives, Compared

Four real ways to combine Claude and Slack exist today, scored on the decision rules above. The legacy Claude in Slack app is not one of them: it retired on August 3, 2026.

Claude Tag: Who Is It Built For?

This decision is more common than it was a year ago. Anthropic overtook OpenAI in business adoption for the first time in May 2026, 34.4 percent of firms versus 32.3 percent, according to Ramp's AI Index, which tracks spend across more than 50,000 businesses. Claude Tag is for a strategy, deal, or corp-dev team already on a Claude Team or Enterprise plan that wants an assistant living inside one operational channel rather than a fresh chat window each time. It puts one shared @Claude in the channel that every member can see and steer, builds memory of that channel's ongoing work over time, and can run a multi-stage task over hours without anyone staying present to manage each step. An optional ambient mode lets it proactively surface relevant updates without being tagged. "Claude Tag is built to be interactive and multiplayer," said Cat Wu, Anthropic's head of product for Claude Code and Cowork, when it launched. "When Claude Tag works in a channel, everyone can see it, and everyone can jump in, engage, and steer it in the right direction." Anthropic disclosed in the same launch announcement that 65 percent of its own product team's code is now created by an internal version of the tool, the clearest signal it has given that Claude Tag is meant to run unattended on real work, not just answer questions.

Setup is admin-side. An Owner or Primary Owner pairs Claude Tag with the Slack workspace from the Claude settings console, connects the data sources and tools each channel should reach, sets token spend limits at the org and per-channel level, and pilots it in one private channel before a wider rollout. Strategy teams use it most often for channel and thread summarization, extracting decisions and action items from a closed-out discussion, turning a week of chat into an executive brief, and pressure-testing a recommendation before it goes to leadership. For issue framing prompts that pair well with that last use, see how to build an issue tree, and for turning informal competitive signal into a structured slide, see how to build a competitive landscape slide.

The trade-off: Claude Tag is still a beta research preview, restricted to Team and Enterprise plans, and per-channel setup takes real admin time. Ambient mode surfacing unprompted information inside a live deal channel also needs a deliberate policy decision before anyone turns it on, not a default left alone.

Claude.ai's Slack Connector: Who Is It Built For?

This one runs in the opposite direction from Claude Tag. You stay in the Claude.ai web interface, and Claude has been granted permission to search your Slack workspace for relevant context. It is not a bot that posts into Slack; it is Claude pulling Slack content into a Claude.ai conversation, and it can read any public or private channel you personally already have access to. It is the better fit for an individual analyst who needs to pull signals from three or four channels into one view before a meeting, a board update, or an onboarding brief, rather than a channel-wide teammate.

It is available to Claude Pro and Max users, which makes it the right answer for a team that has not bought a Claude Team or Enterprise seat, or for one member of a larger team who wants Slack context without waiting on an admin rollout. Setup takes under five minutes: connect Slack from the integrations panel inside Claude.ai, and Claude can reference channel content the next time you ask. Billing runs on that individual's own Claude subscription, not an organization-wide account, which is also why it does not need the admin sign-off Claude Tag does.

The trade-off: it cannot post back into Slack, work asynchronously, or build memory of a channel over time. It is a research aid for one person's Claude.ai conversation, not a standing teammate the whole channel can steer.

Slack's Built-In AI: Who Is It Built For?

This one is for a team with no Claude subscription at all, or one that would rather keep AI entirely inside Slack's own data controls than add a second vendor. Conversation and thread summaries, plus huddle notes, ship free on every paid Slack plan and need no Anthropic account. Business+ adds channel recaps, AI search answers, file summaries, and workflow automation; Enterprise+ layers on organization-wide search. None of it requires pairing a second vendor with your workspace, connecting external tools, or training an admin on a new console, since it is already part of the Slack subscription your team is paying for.

Slack itself frames the stakes of getting AI into this layer at all. "Slack is the only layer in the AI stack where teams work together," Rob Seaman, Slack's EVP and general manager, said of bringing Claude Tag into the product, a reminder that Slack is building native AI into the same surface Claude Tag competes for. Separately, Slack's own State of Work survey of 17,000 knowledge workers, published in 2019, found that 68 percent spent at least 30 minutes a day just switching between apps, which is exactly the friction native, in-Slack AI features are built to cut without ever leaving the workspace.

The trade-off: it does not carry memory across sessions the way Claude Tag does, cannot execute a multi-step research task unattended, and does not reach outside Slack the way the Slack Connector reaches into Claude.ai. It answers questions about one request at a time.

Manual Copy-Paste: Who Is It Built For?

This one is for ad hoc work: copy content out of Slack and paste it into Claude.ai. No setup, no admin approval, and no persistence between sessions. It works on any Claude plan, including the free tier, which makes it the right call for sensitive content a team does not want flowing through an automated integration at all, or for a workspace not yet on a plan that supports the other three options. For broader Claude workflows once a team has an answer to act on, see 21 Strategy Skills for Claude.

The trade-off: manual effort every time, and nothing carries over to the next conversation. For a single thread, that cost is trivial. For a channel someone checks daily, it adds up fast enough that one of the other three options usually pays for itself.

Where Does Oria Fit In?

Every option above ends the same way: a decision or a synthesis sitting as text, in a Slack message or a Claude.ai reply. Turning that into a formatted, on-brand PowerPoint deck is a separate job, and it is the one Oria is built for. Oria is aimed at the output a tier-one consulting firm produces: board packs, steering committee decks, diligence exhibits, and dense operating-model frameworks held to an enforced corporate template. It reaches you two ways, a PowerPoint add-in running in the task pane on Windows, macOS, and PowerPoint for the web, and a connector for Claude and ChatGPT over MCP, so the slide can be built from the same chat where Claude just summarized your channel, without opening PowerPoint separately. Either way the output is native PowerPoint objects on your own template, not a static export, so a partner can still edit the deck after Oria hands it back. See how to install Oria in Claude and ChatGPT.

The trade-off: Oria only helps once the discussion is over and a decision needs to become a deck. It does not summarize threads, extract action items, or run inside Slack at all; that part of the job still belongs to whichever setup above your team is using. And within slides, Oria is built for the corporate environment and loses on highly visual work: founder fundraising decks, launch and campaign decks, and marketing one-pagers want visual impact more than defensible content, and a design-led tool such as Gamma, Canva, Pitch, or Beautiful.ai will beat it there and look better doing it.

Data Handling and Governance: What Strategy Teams Need to Know

A team routing deal information or board-level content through any of the setups above needs clear answers before it deploys them in an operational channel, not after. The answers below apply specifically to Claude Tag, since it is the option that actually stores and executes against channel content; Slack's own AI features run under Slack's data processing terms rather than Anthropic's.

Which Setup Should Your Team Use?

Route by the constraint that actually binds: your plan, what the channel needs to remember, and what happens after Claude gives you an answer. Most teams end up using two or three rows on this table at once, not one, since the plan question and the "what happens after the answer" question are answered by different tools.

For a full playbook on how consultants and strategy teams use Claude end-to-end, including how to turn channel analysis into board-ready deliverables, see The Consultant's Guide to Claude.

FAQ