{"id":1202,"date":"2026-07-08T12:32:27","date_gmt":"2026-07-08T12:32:27","guid":{"rendered":"https:\/\/feedsta.ai\/blog\/claude-tag-slack-setup-guide\/"},"modified":"2026-07-19T06:33:20","modified_gmt":"2026-07-19T06:33:20","slug":"claude-tag-slack-setup-guide","status":"publish","type":"post","link":"https:\/\/feedsta.ai\/blog\/claude-tag-slack-setup-guide\/","title":{"rendered":"How to Set Up Claude Tag in Slack and Delegate Team Tasks to AI"},"content":{"rendered":"

Claude Tag is Anthropic’s Slack integration (currently in public beta) that lets team members delegate repeatable work by mentioning @Claude<\/strong> in a channel or thread. Claude works in a cloud sandbox, posts a progress checklist, and reports the finished result back into the same thread. Setup requires a paid Claude plan, Slack admin permissions, a dedicated test channel, and a careful rollout to avoid runaway cost or data exposure.<\/p>\n

What Claude Tag Actually Does<\/h2>\n

Claude Tag is the current product from Anthropic for using Claude inside Slack. It supersedes an earlier, more limited “Claude in Slack” app. Once installed, any team member with access to a connected channel can mention @Claude<\/strong> and hand off a task.<\/p>\n

Behind the scenes, Claude works in an ephemeral cloud sandbox hosted by Anthropic, with a separate sandbox for each Slack thread. It can read the thread, run multi-step work, call any connected tools it has been granted, and post the result back into the thread. Anyone in the channel can steer it mid-task by replying in the thread.<\/p>\n

The honest framing: this turns Claude from a chat assistant into a delegated worker. It is still a language model, so it still needs clear instructions, well-scoped tasks, and a human reviewer on anything that matters.<\/p>\n

What Do You Need Before Installing Claude Tag?<\/h2>\n

Run through this checklist before installing anything. Skipping any of these items is the most common cause of a messy rollout.<\/p>\n

    \n
  • A Claude Team or Claude Enterprise account.<\/strong> Claude Tag is not available on the Free, Pro, or Max individual plans.<\/li>\n
  • Slack workspace admin permissions<\/strong> (or a direct line to whoever has them). Most workspaces require an admin to approve new apps before they can be installed.<\/li>\n
  • Permission to install Slack apps<\/strong> in the workspace, or a clear approval path.<\/li>\n
  • Access to the Claude Tag admin settings<\/strong> at claude.ai\/admin-settings\/claude-tag<\/code> as an organization Owner or Admin.<\/li>\n
  • A dedicated test channel<\/strong> where you can trial Claude without touching production conversations.<\/li>\n
  • A short list of tools Claude actually needs<\/strong>, not a wishlist. Connect tools on purpose.<\/li>\n
  • Funded usage credits<\/strong>. On Claude Team plans, the organization must fund usage credits before Claude Tag will run.<\/li>\n
  • Internal rules<\/strong> covering what Claude is and is not allowed to access, who can delegate what, and how outputs should be reviewed.<\/li>\n<\/ul>\n

    Step-by-Step Setup<\/h2>\n

    Step 1: Install Claude in Slack<\/h3>\n

    Go to claude.com\/claude-for-slack<\/code> and click the button to add Claude to Slack. This opens the Slack Marketplace listing for the official Claude app. Confirm the correct workspace before approving, and be ready for a Slack workspace admin to complete the final approval. If you are not an admin, send the request through your normal app-approval process and wait for the confirmation before continuing.<\/p>\n

    Step 2: Connect Your Claude Account and Tools<\/h3>\n

    Open the Claude app inside Slack, then in a separate browser tab open the Claude Tag settings. You will set the channel scope, attach an access bundle (a named set of tool credentials), and choose a default model. Connect only the tools Claude actually needs for the work you plan to delegate. For a first test, Slack channel history and search, web search, and sandboxed code execution are enough, and they do not require any extra credentials.<\/p>\n

    Warning:<\/strong> do not connect sensitive systems, customer databases, or private client data during initial testing. It is much easier to expand access later than to clean up after an over-permissioned rollout.<\/p>\n

    Step 3: Pair Claude Tag with Slack<\/h3>\n

    Pairing is a two-sided handshake between Slack and Claude.<\/p>\n

      \n
    1. A Slack workspace admin posts @Claude connect<\/strong> as a new top-level message in the channel you want to use.<\/li>\n
    2. Claude replies in-thread with a single-use pairing code that expires in 15 minutes.<\/li>\n
    3. A Claude organization Owner opens claude.ai\/admin-settings\/claude-tag<\/code> in the browser, clicks Set up<\/em>, and pastes the code into the wizard.<\/li>\n
    4. Choose the channel scope: Whole workspace<\/em> or Specific channels<\/em>. Strong recommendation: start with Specific channels and one test channel. You can always expand later.<\/li>\n
    5. Attach the access bundle, add usage credits, and set a spend limit before launching.<\/li>\n<\/ol>\n

      If the code expires before you finish, just post @Claude connect<\/strong> again and use the new code.<\/p>\n

      Step 4: Lower Costs by Setting the Default Model<\/h3>\n

      In the Claude Tag settings under Customize<\/em>, set the default model for the scope. Sonnet is a sensible default for everyday business work such as summaries, drafts, research, and internal documentation, and it costs meaningfully less per token than Opus. Reserve Opus for genuinely complex or high-stakes tasks.<\/p>\n

      Users can still switch models for a single thread by asking, for example “@Claude use Sonnet for this”<\/em>. The reply footer shows which model answered, so it is easy to audit.<\/p>\n

      Step 5: Run a Test in a Dedicated Channel<\/h3>\n

      Tag @Claude<\/strong> with a simple, real task and watch what happens. A good first prompt:<\/p>\n

      @Claude please summarize this thread, identify the open questions, and create a short action list for the team.<\/p><\/blockquote>\n

      Check four things before you expand access:<\/p>\n

        \n
      • Claude responded and used the right context.<\/li>\n
      • It touched only the tools you expected.<\/li>\n
      • The output is actually usable, not just plausible.<\/li>\n
      • A human reviewer can verify the result quickly.<\/li>\n<\/ul>\n

        If any of those fail, fix the access bundle, the prompt style, or the model choice in a fresh thread and try again. Remember that configuration changes only apply to new<\/em> threads, so always retest in a fresh thread rather than continuing in the same one.<\/p>\n

        What Should You Review After the First Run?<\/h2>\n

        Once you have run a handful of tasks, go back to the Claude Tag admin pages and audit three things:<\/p>\n

          \n
        • Token spend per channel<\/strong> at claude.ai\/admin-settings\/usage\/claude-tag<\/code>. The per-channel breakdown makes it obvious where usage is concentrated and where the spend limit should sit.<\/li>\n
        • Connected tools.<\/strong> If Claude never used a tool, drop it from the access bundle. A smaller bundle is safer and cheaper.<\/li>\n
        • Memory.<\/strong> 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?”<\/em> 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.<\/li>\n<\/ul>\n

          If multiple teams use Claude Tag, put a recurring memory review on the calendar. Persistent memory is genuinely useful, but it should be monitored.<\/p>\n

          Safety and Permissions<\/h2>\n

          Claude Tag can do real work, so the guardrails matter.<\/p>\n

            \n
          • Start with limited channel access and expand slowly.<\/li>\n
          • Avoid connecting sensitive tools until you trust the workflow.<\/li>\n
          • Do not give Claude access to private client data without an approved internal policy.<\/li>\n
          • Write simple internal rules for what employees can delegate (for example: no sending emails or messages without human approval).<\/li>\n
          • Keep a human review step on anything important.<\/li>\n
          • Monitor usage and costs weekly at first, then monthly.<\/li>\n
          • Document which channels Claude is allowed in, and why.<\/li>\n
          • In channels that include guests, Claude stays silent unless an admin enables Allow Claude to respond to guests<\/em>.<\/li>\n<\/ul>\n

            Best Use Cases<\/h2>\n

            Claude Tag fits work that is text-heavy, repeatable, and lives in conversation:<\/p>\n

              \n
            • Summarizing long Slack threads<\/li>\n
            • Meeting follow-ups and action items<\/li>\n
            • Drafting client updates from internal discussions<\/li>\n
            • Turning conversations into task lists<\/li>\n
            • Researching internal questions across connected tools<\/li>\n
            • Creating SOPs from Slack conversations<\/li>\n
            • First drafts of blog posts, emails, and reports<\/li>\n
            • Project status reviews<\/li>\n
            • Preparing sales or support responses<\/li>\n
            • Organizing team knowledge into something searchable<\/li>\n<\/ul>\n

              Example Slack Prompts<\/h2>\n

              Copy, paste, and adapt these to get started:<\/p>\n

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

                Troubleshooting Common Claude Tag Issues<\/h2>\n

                When something does not work, run through this list before assuming Claude is broken.<\/p>\n

                  \n
                • Claude does not respond.<\/strong> Check that the app is installed and approved, the channel is in the configured scope, Claude Tag is not switched off for that scope, and the channel is not shared across multiple Slack workspaces (which is not supported). If the channel has guests, enable Allow Claude to respond to guests<\/em>.<\/li>\n
                • Pairing code expired or already used.<\/strong> Codes are single-use and expire in 15 minutes. Post @Claude connect<\/strong> again to get a new one.<\/li>\n
                • @Claude connect did nothing.<\/strong> Only Slack workspace admins can run the connect command. Ask an admin to post it.<\/li>\n
                • Tasks fail to start.<\/strong> The organization has not funded usage credits. Add credits under the Claude Tag admin settings.<\/li>\n
                • New tool connections do not seem to work.<\/strong> Configuration changes only apply to new threads. Start a fresh thread and try again.<\/li>\n
                • "Still waiting for available capacity" message.<\/strong> This is transient. Retry in the same thread after a short wait.<\/li>\n
                • Costs higher than expected.<\/strong> Check the default model for the scope and review per-channel spend. Switching the default from Opus to Sonnet is usually the single biggest cost lever.<\/li>\n
                • Claude is using more tools than expected.<\/strong> Tighten the access bundle for that scope and remove tools that are not needed.<\/li>\n
                • Memory needs review or deletion.<\/strong> Channel members can correct or remove entries by talking to Claude. Organization Owners can edit or delete a scope’s memory in admin settings; Admins can view it.<\/li>\n<\/ul>\n

                  Cost Control<\/h2>\n

                  Two factors drive the bill: which model handles the work, and how much of it runs.<\/p>\n

                    \n
                  • Set a sensible default model.<\/strong> Sonnet is the right starting point for most business work. Opus is reserved for tasks that genuinely need it.<\/li>\n
                  • Set a spend limit before launch.<\/strong> Limits live in the Claude Tag admin settings and reset each billing period. Setting the limit first turns a surprise into a pause.<\/li>\n
                  • Use dedicated test channels.<\/strong> Testing in a private channel with a small group prevents accidental overuse from a busy workspace.<\/li>\n
                  • Expand slowly.<\/strong> Move from one channel to a small group, then to a wider rollout, checking spend and outputs at each step.<\/li>\n
                  • Monitor the usage page weekly at first.<\/strong> claude.ai\/admin-settings\/usage\/claude-tag<\/code> shows a per-channel breakdown so you can see exactly where tokens are going. Work done in channels bills to the organization’s shared usage credit balance, while direct messages with Claude bill to the sender’s own seat.<\/li>\n<\/ul>\n

                    Conclusion<\/h2>\n

                    Claude Tag makes Slack more productive by letting teams delegate work where the conversation already happens, and it does so without forcing people to learn a new tool. The best setup is careful and controlled: start with one test channel, connect only the tools you actually need, set Sonnet as the default model, set a spend limit, and review spend, tools, and memory after the first few runs.<\/p>\n

                    Once the configuration is right, Claude becomes a useful teammate for summaries, documentation, follow-ups, content, and internal operations, and your team can keep working in the place they already do.<\/p>\n

                    FAQ<\/h2>\n

                    What plan is required to use Claude Tag in Slack?<\/h3>\n

                    Claude Tag requires a paid Claude Team or Claude Enterprise plan and is not available on Free, Pro, or Max individual plans. The organization must also fund usage credits before Claude Tag will run on a Team plan.<\/p>\n

                    How do you pair Claude Tag with a Slack channel?<\/h3>\n

                    A Slack workspace admin posts @Claude connect<\/strong> in the target channel, then a Claude organization Owner pastes the returned single-use pairing code (valid for 15 minutes) into the Claude Tag setup wizard at claude.ai\/admin-settings\/claude-tag<\/code>.<\/p>\n

                    What is the single biggest way to control Claude Tag costs?<\/h3>\n

                    Set Sonnet as the default model for the scope and set a spend limit before launch. Switching the default from Opus to Sonnet is described as the single biggest cost lever, and spend limits reset each billing period so they turn a surprise into a pause.<\/p>\n