Setting Up Claude Tag in Slack: A Practical Guide for Business Teams

Claude Tag is Anthropic’s Slack integration that lets any team member tag @Claude inside a thread to delegate research, summaries, drafts, documentation, follow-ups, and operations work. Setup requires a Claude Team or Enterprise plan, Slack admin permissions, and a clear list of tools Claude should be allowed to touch. This guide walks through the full setup, from install to cost control, with practical guardrails at every step.

What Does Claude Tag Actually Do?

Claude Tag connects Claude to a Slack workspace. Once paired, any team member can mention @Claude in a channel or thread. Claude works in an ephemeral cloud sandbox hosted by Anthropic, one sandbox per Slack thread, separate from the chat itself. Inside that sandbox it can read channel history, search Slack, run web searches, execute code in a sandboxed environment, and call any tools the admin has connected, including Google Drive, Gmail, Google Calendar, Notion, Confluence, GitHub, GitLab, BigQuery, Snowflake, Linear, Asana, Jira, HubSpot, Salesforce, Datadog, and Sentry. Custom tools and custom MCP servers can also be added through “Connect another tool.”

As Claude works, it posts a progress checklist in the thread so the team can see what it is doing. Anyone in the channel can steer it mid-task by replying in the same thread. When the task is finished, Claude posts the result back into the thread where it started. In plain terms, Claude Tag turns Claude from a chat assistant into a practical cloud-based AI teammate, but it still needs clear instructions and human review on the output.

What Do You Need Before You Start?

Before touching any settings, line up the following:

• A Claude Team or Claude Enterprise account. Claude Tag is not available on the Free, Pro, or Max individual plans.
• Slack workspace admin permissions, or a Slack admin who is willing to run a single setup command for you.
• Permission to install apps from the Slack Marketplace.
• Access to the Claude Tag admin settings at claude.ai/admin-settings/claude-tag as a Claude organization Owner.
• A dedicated test channel that is not used for real client or production work.
• A clear list of which tools Claude should be allowed to use. Less is safer at the start.
• Funded usage credits for the Claude organization. On Team plans, the organization must fund usage credits before Claude Tag will run.
• Internal rules for what Claude should and should not be allowed to access, especially around client data and sensitive systems.

How Do You Set Up Claude Tag Step by Step?

Step 1: Install Claude in Slack

Go to claude.com/claude-for-slack and click “Add to Slack.” This opens the Slack Marketplace and installs the Claude app into the chosen workspace. Most Slack workspaces require a workspace admin to approve new apps, so have an admin on hand before you start. Once the app is approved, it will appear in the Slack sidebar for the workspace.

Step 2: Connect Your Claude Account and Tools

Open the Claude app inside Slack to confirm the install, then open the Claude Tag settings in the browser at claude.ai/admin-settings/claude-tag. The setup wizard will ask you to choose an access bundle, which is a named set of tool credentials Claude is allowed to use. Connect only the tools Claude actually needs for the first round of testing. A warning worth repeating: do not hand Claude access to sensitive production systems, financial data, or private client information during initial testing. Every connected tool is a potential surface for accidental exposure.

Step 3: Pair Claude Tag with Slack

A Slack workspace admin posts @Claude connect as a new top-level message in the channel you want to use. Claude replies with a pairing code that is single-use and expires in 15 minutes. Copy it immediately, then go to claude.ai/admin-settings/claude-tag, click Set up, and paste the code into the wizard. Choose the channel scope: either “Whole workspace” or “Specific channels.” Add the access bundle, fund usage credits, set a spend limit, and launch the connection. The strong recommendation here is to choose Specific channels and start with one test channel, not the whole workspace. A test scope is far easier to roll back than a workspace-wide one if something goes wrong.

Step 4: Lower Costs by Setting the Default Model

Under the Customize section at claude.ai/admin-settings/claude-tag, admins can set a default model per scope. Available models depend on how the organization is configured, typically Opus and Sonnet variants. Switching the default to Sonnet gives a better balance of quality and cost for everyday business work such as summaries, drafts, research, and internal documentation. Opus costs meaningfully more per token and should be reserved for high-stakes or genuinely complex tasks. Users can still switch models for a single thread just by asking, for example @Claude use Sonnet for this, and the reply footer shows which model actually answered. The default sets the baseline; the per-thread override gives flexibility.

Step 5: Run a Test in a Dedicated Channel

Open the dedicated test channel and tag Claude with a simple, real task. A good first prompt: “@Claude please summarize this thread, identify the open questions, and create a short action list for the team.” Confirm that Claude responds, that it used the right context, that it touched only the tools you expected, and that the output is usable. Have a human review the result before expanding access to more channels or more tools.

What Should You Review After the First Run?

After the first few real tasks, open the Claude Tag admin pages and audit three things:

• Token spend per channel. The usage page at claude.ai/admin-settings/usage/claude-tag breaks down spend by channel and resets each billing period.
• Connected tools actually used. If a tool was connected but never used, disconnect it. Fewer connections means less risk and a tighter access bundle.
• Memory Claude has saved. Claude Tag keeps persistent, channel-scoped memory. Memory from public channels is shared across the workspace; memory from private channels stays in that channel. Anyone in the channel can ask @Claude what do you remember about this channel? and can correct or remove entries by talking to Claude. Organization Owners can edit or delete a scope’s memory in admin settings, and Admins can view it.

Persistent memory is genuinely useful for repeat workflows, but it should be monitored. If multiple teams use Claude Tag, build a regular memory review into your admin routine.

How Should You Handle Safety and Permissions?

A few practical guardrails that pay off quickly:

• Start with limited channel access, not workspace-wide.
• Avoid connecting sensitive tools at first. Add them only when a real workflow demands it.
• Do not give Claude access to private client data without an approved internal policy and a human review on the output.
• Write simple internal rules for what employees can delegate, especially around outbound messages, financial data, and any action that touches customers.
• Keep a human in the loop on any output that will be sent externally or used to make decisions.
• Monitor usage and costs weekly at first, then monthly once patterns are clear.
• Document which channels Claude is allowed in, and keep that list current.

One guest-access detail that often surprises admins: in channels that include guests, Claude stays silent by default unless the admin enables “Allow Claude to respond to guests.” Plan for this if your team collaborates with external people in shared channels.

What Are the Best Use Cases for Claude Tag?

Claude Tag fits naturally into the work teams already do in Slack:

• Summarizing long Slack threads that everyone has stopped reading.
• Capturing meeting follow-ups and decisions.
• Drafting client updates from internal discussions.
• Turning conversations into task lists with owners.
• Researching internal questions by searching connected tools.
• Creating SOPs from Slack conversations.
• Producing first drafts of blog posts, emails, and reports.
• Reviewing project status across tools.
• Preparing sales or support responses from prior context.
• Organizing team knowledge scattered across channels and documents.

Example Slack Prompts That Work

Copy-paste prompts that work well in real threads:

1. @Claude summarize this thread and list the decisions made.
2. @Claude create a task list from this conversation and group it by owner.
3. @Claude turn this discussion into a client-friendly update.
4. @Claude review this idea and identify risks or missing details.
5. @Claude draft an SOP based on the process described in this thread.
6. @Claude create a blog outline from the points above.
7. @Claude compare the options discussed here and recommend the best one.
8. @Claude find the open questions we still need to answer.
9. @Claude rewrite this into a professional email.
10. @Claude create a concise executive summary of this thread.

How Do You Troubleshoot Common Claude Tag Issues?

Most Claude Tag issues fall into a small set of common causes:

• Claude does not respond. The app may not be installed or approved, the channel may not be in the chosen scope, Claude may be switched off for that scope, guests may be in the channel, or the channel may be shared across multiple Slack workspaces, which is not supported.
• Pairing code expired or already used. Codes are single-use and expire in 15 minutes. Run @Claude connect again and paste the new code quickly.
• Only admins can pair. Only Slack workspace admins can run @Claude connect. Have an admin do it.
• Usage credits not funded. On Team plans, the organization must have funded usage credits before Claude Tag will run.
• New tools not taking effect. Configuration changes only apply to new threads. An existing thread keeps the connections it started with, so test changes in a fresh thread.
• “Still waiting for available capacity.” This message is transient. Retry in the same thread and it usually resolves.
• Costs higher than expected. Check the default model and the per-channel spend page. Switching the default to Sonnet usually brings costs down.
• Claude using too many tools. Tighten the access bundle to the minimum set needed.
• Memory needs review or deletion. Channel members can correct memory by talking to Claude; organization Owners can edit or delete a scope’s memory in admin settings.

How Do You Keep Claude Tag Costs Under Control?

Model choice is the single biggest lever. Sonnet is a sensible default for everyday work and costs meaningfully less per token than Opus, while still being strong enough for summaries, drafts, research, and internal documentation. Reserve Opus for tasks that genuinely need it.

Beyond model choice, a few habits keep costs predictable:

• Monitor token spend after the first few runs at claude.ai/admin-settings/usage/claude-tag.
• Use dedicated test channels so accidental overuse does not hit a production channel.
• Expand from one channel to more channels slowly, watching the spend page as you go.
• Set a spend limit before launch, not after the first surprise. The limit resets each billing period.

Conclusion

Claude Tag makes Slack more productive by letting teams delegate work where the conversation already happens, without leaving the thread. The best setup is careful and controlled. Start with one channel, connect only the tools you need, set Sonnet as the default model, set a spend limit, and review spend, tools, and memory after testing. Once configured properly, Claude becomes a useful teammate for summaries, documentation, follow-ups, content drafts, and internal operations, with a human still firmly in the loop on the work that matters most.

FAQ

What plan is required to use Claude Tag in Slack?

Claude Tag requires a Claude Team or Claude Enterprise plan. It is not available on the Free, Pro, or Max individual plans, and the organization must have funded usage credits before Claude Tag will run on a Team plan.

How do you pair Claude Tag with a Slack channel?

A Slack workspace admin posts @Claude connect as a new top-level message in the chosen channel, copies the single-use pairing code that expires in 15 minutes, and pastes it into the setup wizard at claude.ai/admin-settings/claude-tag, then selects a channel scope, access bundle, and spend limit.

Why is Claude silent in channels with guests?

Claude stays silent by default in any channel that includes guests unless an admin explicitly enables “Allow Claude to respond to guests” in the Claude Tag settings.