Claude for Slack: How Strategy Teams Can Turn Conversations into Decisions
Claude Tag, Anthropic's new Slack integration, launched June 23, 2026. Here is how strategy teams activate it and use it for real strategic work, from channel summarization to async deal research.
Free skills and prompts for Claude and strategy work
Templates for Claude, ChatGPT and Perplexity — from diagnostics to board-ready decks.
Claude Tag, Anthropic's new Slack integration, launched yesterday on June 23, 2026. It replaces the legacy Claude in Slack app and changes what AI assistance inside Slack actually means for professional teams. This is not a minor update. The legacy app treated every conversation as a fresh interaction. Claude Tag gives teams a persistent AI that lives inside Slack channels, remembers the channel's ongoing work over time, and can complete multi-stage tasks asynchronously without anyone staying in the thread to manage it.
Claude Tag is currently in beta as a research preview, available to Claude Team and Enterprise plan customers. The legacy Claude in Slack app will be retired on August 3, 2026. Strategy, consulting, and corporate development teams now have a narrow window to evaluate both products, understand what changes with the migration, and decide how to configure the new system before the deadline.
For teams doing deal analysis, competitive research, and board-level reporting inside Slack, the persistent context and async task execution in Claude Tag materially change what the tool can do. This article covers both products, how to activate each, and how strategy teams should use them.
What Changed: Two Versions of Claude in Slack
There are currently two versions of Claude in Slack. Understanding which one you have, and which one you should move to, matters before you configure anything.
Claude in Slack (legacy app) launched in October 2025. It is available on any paid Slack plan combined with a Claude.ai account. It lets users @mention Claude in channels and threads, message Claude directly in DMs, and access a Claude AI assistant panel from the Slack header. It summarizes threads, drafts content, and answers questions inline. Each conversation is separate from Claude.ai web history, and each conversation starts fresh. There is no memory carried between interactions. This app stops working on August 3, 2026.
Claude Tag launched June 23, 2026, as a beta research preview. It is available exclusively to Claude Team and Enterprise plan customers. It replaces the legacy app and introduces four capabilities the legacy app does not have. First, there is a shared channel identity: all members of a channel see the same @Claude, rather than each user having a separate session. Second, Claude builds persistent memory of the channel's ongoing projects over time, so context accumulates rather than resetting with each interaction. Third, Claude can execute multi-stage tasks asynchronously over hours without any user staying present to manage each step. Fourth, optional ambient mode lets Claude proactively surface relevant information from connected sources without being explicitly tagged.
If your organization is on a Claude Team or Enterprise plan, move to Claude Tag now rather than at the August 3 deadline. If you are on a Pro or Max plan with legacy Claude in Slack access, note that Claude Tag will not be available to you until Anthropic expands access beyond the current beta tier.
How to Activate the Legacy Claude in Slack
Requirements
A paid Slack plan (Pro, Business+, or Enterprise Grid). A Claude.ai account (any paid plan). Admin access to install from the Slack App Marketplace.
Admin setup steps
Open the Slack App Marketplace from your workspace.
Search for "Claude" and select the Claude by Anthropic app.
Click "Add to Slack" and follow the authorization prompts.
Approve the app for your organization. On Enterprise Grid, this requires approval from an Organization Admin.
User setup (each team member)
In Slack, go to the Apps section in the left sidebar and search for Claude.
Open the Claude app and click "Connect Account."
Select your Claude organization when prompted.
Authorize the connection. You will be redirected to Claude.ai and back to Slack.
Three ways to use Claude once connected
@Claude in any channel or thread where Claude has been added. Direct message with Claude from the Apps list. Claude AI assistant panel from the Slack header. Each conversation resets. There is no memory between sessions.
How to Activate Claude Tag
Requirements
Claude Team or Enterprise plan. Primary Owner or Owner role in the Slack workspace for admin setup.
Admin setup steps
Pair Claude Tag with the workspace.
From your organization's Claude settings console, initiate the Claude Tag pairing with your Slack workspace. This is not the same as installing from the Slack App Marketplace. Pairing is done from the Claude admin side.
Configure tool access and data source connections.
Admins connect specific data sources, repositories, and tools on a per-channel basis. Credentials can be set at three levels: org-wide (applies to all channels), workspace-wide (applies to all public channels), or per-channel (scoped to a single channel). Your M&A channel can connect to different data sources than your market research channel.
Set monthly spend limits.
Configure token limits at both the org-wide level and per-channel level. Per-channel spend caps prevent runaway usage in high-volume channels.
Test in a private channel first.
Before rolling out to operational channels, run Claude Tag in a controlled private channel to validate tool connections, ambient mode behavior, and response quality against your actual workflows.
Member access modes
Open to all members of the Slack workspace.
Open to members of the Claude organization only.
Role-based access control (available on Enterprise plans only), which restricts which users can interact with Claude Tag in specific channels.
Channel memory
Claude Tag builds and stores memory scoped to each designated channel. Private channels are excluded from cross-channel context by default. Admins can view, edit, and delete channel memory at any time from the org settings console.
Three Ways to Combine Claude and Slack
There are three distinct ways to combine Claude and Slack. Conflating them leads to wrong setup decisions.
Workflow A: Native Claude in Slack or Claude Tag (Claude lives inside Slack).
Claude operates as a participant in your Slack workspace. Team members interact with Claude without leaving Slack. With the legacy app, interactions are ephemeral and per-user. With Claude Tag, interactions are shared across the channel, Claude builds memory of the channel's work over time, and tasks can be delegated asynchronously. This is the setup most relevant for strategy teams who want Claude embedded in their operational channels, handling research, synthesis, and async deliverables. Channel interactions bill to the organization account. DM interactions bill to individual accounts.
Workflow B: Slack Connector inside Claude.ai (you are in Claude.ai, and Claude searches Slack).
This is the reverse direction. You are working in the Claude.ai web interface, and Claude has been granted access to search your Slack workspace for relevant context. Available since January 2026 to Claude Pro and Max users. Claude can search public and private channels you have access to. This is not a bot in Slack. It is Claude pulling Slack content into a Claude.ai conversation. Useful for meeting prep, project coordination research, and onboarding when you need to pull together context from multiple channels before a conversation. Set it up by connecting Slack from the integrations panel inside Claude.ai.
Workflow C: Manual copy-paste.
Copy content from Slack and paste it into Claude.ai. No setup required. No persistence. Works on any Claude plan. Right for ad hoc tasks, sensitive content you do not want flowing through an automated integration, or teams not yet on a plan that supports the above integrations. The limitation: manual effort each time and no persistent context.
Which to choose
Choose Workflow A for teams doing recurring operational work inside Slack channels. Choose Workflow B for individual analysts doing research and synthesis inside Claude.ai with Slack as one input source. Use Workflow C when setup is not feasible or appropriate.
Claude for Slack: Seven Use Cases for Strategy Teams
Strategy teams spend significant time processing conversations: reading long threads to find the decisions, synthesizing signals from multiple discussions, and turning raw dialogue into structured analysis. Claude in Slack addresses these tasks directly. The use cases below reflect how Anthropic's own finance and strategy teams have deployed this in practice. For broader Claude strategy workflows, see 21 Strategy Skills for Claude.
Channel and Thread Summarization
Before a meeting, catch up on a long project channel or a complex thread without reading every message. This is most useful when you have been away from a channel for several days, or when you need to brief someone who was not part of the conversation. With Claude Tag, the persistent channel context means Claude can surface not just recent messages but the arc of a project over weeks.
Example prompt
Extracting Decisions and Action Items
Long discussions produce decisions and commitments that are easy to lose. This prompt is most useful after a major discussion thread closes, or after a channel-based review that did not have a formal meeting structure.
Example prompt
Synthesizing Customer and Market Insights
Deal teams and strategy teams often receive customer or market signals through informal Slack channels: sales updates, customer success notes, partner feedback, and analyst commentary. Synthesizing this into a coherent picture requires reading across many messages and threads. For structured competitive analysis prompts, see Claude Prompts for Competitive Analysis.
Example prompt
Preparing Executive Briefs from Internal Discussions
Finance and strategy teams at Anthropic use Claude to turn channel conversations into weekly digests for executives. This saves time on both ends: the analyst is not writing from scratch, and the executive receives a clean summary rather than a channel link.
Example prompt
Pressure-Testing Strategic Assumptions
Recommendations that emerge from internal discussions often carry the assumptions of the team that produced them. Claude can apply structured pressure-testing before a recommendation goes up to leadership.
Example prompt
Competitive Analysis with Internal Signal
Competitive intelligence often surfaces in informal channels: a sales rep flags a pricing question, a customer success manager mentions a feature comparison, a partner notes a competitor move. Claude can synthesize these signals into structured competitive context, which strategy teams combine with external research. For issue framing prompts to pair with this workflow, see Claude Prompts for Issue Framing.
Example prompt
Turning Conversations into Structured Recommendations
Strategy teams often have detailed conversations that produce good thinking but no clean output. This prompt converts a channel discussion or thread into a structured deliverable. Anthropic's finance team uses a version of this to turn raw analyst commentary into initial drafts of monthly financial commentary, then edits from there.
Example prompt
Privacy and Permissions: What Strategy Teams Need to Know
Strategy teams handling sensitive deal information and board-level content need clear answers on data handling before deploying Claude in operational channels.
Model training
Anthropic's official Slack Marketplace listing states that Slack conversations are not used to train models by default. For Claude Team and Enterprise plans, customer inputs and outputs are not used to train models by default. This applies to Claude Tag interactions in channels.
Zero Data Retention
Enterprise customers who qualify can enable Zero Data Retention (ZDR), which means Anthropic does not retain conversation data on the backend after each interaction completes. If your organization handles regulated or highly confidential content, confirm ZDR eligibility with your Anthropic account team.
Data deletion
If a user disconnects their Claude account, conversation data is deleted from the Anthropic backend within 30 days.
Audit logging
Every Claude Tag action is logged in a centralized audit log. Each entry identifies which user initiated the request. For regulated industries or organizations with formal AI governance requirements, this log is the basis for compliance review.
Channel memory controls
Admins can view, edit, and delete Claude Tag's channel memory at any time from the org settings console. Memory is scoped strictly to designated channels. Private channels are excluded from cross-channel context by default.
Channel access scoping
Claude only accesses channels it has been explicitly granted access to. There is no ambient crawl of the full workspace. Per-channel tool connections mean each channel's data access is configured independently.
HIPAA
Claude in Slack and Claude Tag are not HIPAA-compliant as confirmed by Anthropic's Slack Marketplace listing. Organizations subject to HIPAA requirements should not route protected health information through Slack-connected Claude workflows.
Best Practices for Strategy Teams
Start with one channel, not the full workspace.
Configure Claude Tag in a single project channel before a broader rollout. This lets you validate tool connections, test ambient mode behavior, review the audit log for expected output, and train at least one admin on the memory management interface. Expanding to additional channels after a controlled pilot avoids configuration errors at scale.
Set per-channel spend limits before go-live.
Claude Tag supports token limits at both the org-wide and per-channel level. Set per-channel caps before enabling Claude Tag in high-volume operational channels. Strategy channels doing async research tasks can consume significant token budget. A cap prevents surprises on the monthly bill and creates a forcing function for prompt efficiency.
Define what each channel's Claude instance is for.
Claude Tag builds memory of each channel's ongoing work. If a channel has a mixed purpose, Claude's context will be mixed too. Where possible, keep project channels scoped to a single workstream so that the persistent memory stays coherent and useful.
Use the Slack Connector in Claude.ai for synthesis across channels.
The Slack Connector is better suited than the in-Slack bot for analysis tasks that require pulling signals from multiple channels into one view. If a strategy analyst needs to synthesize market signals from three channels before a board meeting, Claude.ai with the Slack Connector is the right tool. The in-channel Claude Tag is better for tasks that belong to one channel's workflow.
Treat channel memory as a shared artifact, not a black box.
Admins can review and edit Claude Tag's channel memory from the org settings console. Assign a channel owner who periodically reviews the stored memory for accuracy, removes outdated context, and ensures that the memory reflects the current state of the project rather than accumulated noise from closed workstreams.
Review the audit log during the first 30 days.
The centralized audit log records every Claude Tag action with the initiating user identified. During the initial deployment period, a weekly review of the log by a responsible admin will surface unexpected usage patterns, identify channels where token consumption is high, and confirm that tool connections are functioning as configured.
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
Does Claude Tag replace the legacy Claude in Slack app for all users?
Claude Tag replaces the legacy Claude in Slack app, but it is currently available only to Claude Team and Enterprise plan customers in beta. The legacy app remains active until August 3, 2026. If your organization is on a Pro or Max plan, the legacy app remains your option until Anthropic expands Claude Tag access.
Can team members in private Slack channels use Claude Tag?
Claude Tag can be added to private channels, but private channels are excluded from cross-channel context by default. Admins configure access per channel, and what Claude learns in one channel does not appear in any other channel instance.
If we use Claude in our strategy or M&A channel, will our conversations train Anthropic's models?
No. Anthropic's official policy states that Slack conversations are not used to train models by default. For Claude Team and Enterprise plans, customer inputs and outputs are excluded from model training by default. Enterprise customers can additionally request Zero Data Retention.
What is the difference between Claude Tag and installing the legacy Claude app from the Slack Marketplace?
The legacy Claude in Slack app is installed from the Slack App Marketplace, and each user connects their individual Claude account. Claude Tag is configured from the Claude admin side by pairing it with the Slack workspace. Setup requires Primary Owner or Owner role, and credentials are set at the org, workspace, or per-channel level rather than per-user.
Can Claude Tag connect to external data sources like internal databases or document repositories?
Yes. Admins can connect specific data sources, repositories, and tools on a per-channel basis as part of Claude Tag setup. Connections are channel-specific, so your deal team channel can connect to different sources than your market research channel.