Claude Tag: Your New AI Employee in Slack

Claude Tag is the newest feature released by Anthropic, and the simplest way to describe it: Claude living inside your Slack. In this walkthrough I break down the two very different modes it runs in, the settings you need to know about, the best real-world use cases I have found so far, and what the pricing situation looks like while the feature is fresh.

What you need

• A Slack workspace you can connect Claude to.
• Accounts for the tools you want Claude to use: its own Gmail, Google Drive, or Notion accounts for channel work, or your own connections for DMs.
• If you are on Teams billing, note that you get two thousand dollars of usage credit to experiment with.

1. What is Claude Tag (0:00)

When you connect Claude to your Slack workspace, you open up two different worlds of possibilities, and keeping them straight is the key to the whole feature. World one lives in channels. World two lives in your DMs. Here is the memory trick I use: its own employee in a channel, your own information in the DMs.

2. Claude as an AI employee in channels (0:20)

Inside a channel, Claude behaves like its own AI employee. You can give it access to its own Gmail account, its own Google Drive account, its own Notion account, so it really has its own identity and personality. In channels it behaves more like an agent, similar to Claude Code and Claude Cowork, and less like an assistant.

3. Roles and permissions per channel (0:38)

You can give Claude multiple roles according to the Slack channel it sits in. Want a legal role inside the legal channel? You can absolutely do that. And you can set permissions on what it has access to, channel by channel, plus give it different accounts and different tools depending on where it is deployed.

4. The guest setting you need to know (1:03)

One setting to be aware of before you rely on it: if you have guests inside a channel, Claude is not going to respond to them by default. That is a setting you have to change yourself. If your client-facing channels include external guests, flip this first or the whole use case falls flat.

5. DMs: Claude uses your own connections (1:22)

Direct messages are the second mode. When you DM Claude in Slack, it uses your own connections, so it behaves just like Claude Cowork inside the desktop application. You prompt it like you normally would and ask questions about your own information.

6. Proactive and scheduled tasks (1:56)

Claude in Slack can also behave proactively. You can give it scheduled tasks: ask it to run a task every single Monday, every Tuesday, whatever rhythm you need. Your Slack becomes a place where work happens on a schedule, not just where you ask questions.

7. Use cases: account manager and sales (2:11)

These use cases come from a roundup I found on X. I have not had time to set all of them up myself yet, but they are fantastic ideas for what Claude Tag can do. The first family exploits the fact that Claude Tag remembers everything inside a single Slack channel:

• Client account manager: put Claude inside the channel of each of your clients, and your clients can ask it questions whenever they have one.
• Sales handoffs: it closes the gap between setters and closers. If someone forgets to log information into the CRM, Claude can retrieve it from the channel conversation.
• Channel memory: it keeps track of all the information across every conversation in a channel.

8. Community listening and content pipeline (3:04)

The second family is community listening. Being able to read everything said inside an entire channel is extremely useful for reporting, and it can feed a content pipeline. Think of it as a hybrid of OpenClaw, Hermes, and Claude Code: it really behaves like its own instance.

9. Bridging email and project tools (3:30)

A lot of information lives in Slack simply because Slack is where we communicate. Claude Tag can close the gap between communication in emails and your project management tools such as Trello or Notion: ask it to check everything said in the channel every single day and send it off where it belongs.

10. Fixing bugs from Slack (3:47)

For developers, being able to fix bugs directly from Slack is another genuinely useful one. The report arrives in the channel; the fix starts in the same place.

11. Multiplayer prompting (3:57)

Claude Tag behaves as a multiplayer application. With multiple people inside a single channel, you can all prompt Claude together. If someone kicks off a task and missed a piece of information, a second person can jump in and correct it while Claude is working. That is something a solo desktop chat simply cannot do.

12. Pricing and the two thousand dollar credit (4:26)

Claude Tag is being built as a separate application right now. If you are on Teams billing, you get two thousand dollars of usage. Fair warning: over time this will probably be quite expensive. But right now is a fantastic moment to try it out and see whether this type of tool is something your organization can use.

Pitfalls and tips

• Guests are muted by default. Touch that setting yourself before promising clients a channel assistant.
• Keep the two modes straight: channels use Claude's own accounts, DMs use yours. Deciding which mode fits a task is most of the design work.
• Scope permissions per channel from day one, especially for anything like a legal or client channel.
• Watch your usage. The credit is generous, but the long-term cost deserves attention before you roll it out widely.

Where to go next

The scheduled-task pattern here mirrors the desktop version: see Automate Your Work with Claude (Scheduled Tasks). And for agents that go gather intelligence instead of waiting to be asked, read Scrape Every Social Platform at Once with AI.