@Claude Is Now on Your Team: How Claude Tag Changes the Way Work Gets Done in Slack
How to create separate Claude identities for different teams (sales vs. engineering)
What matters today
How to create separate Claude identities for different teams (sales vs. engineering)
Article roadmap
What you will learn
-
What Claude Tag does and how it differs from Claude Code or Cowork
-
The 4-step setup process for Claude Enterprise and Team accounts
-
How to create separate Claude identities for different teams (sales vs. engineering)
-
Three specific workflows that save 30 or more minutes per week
-
How Anthropic uses it internally and what that tells you about deployment
On June 23, Anthropic shipped Claude Tag: a product that puts Claude inside your Slack workspace as a team member. Not a chatbot you ping in isolation. Not a sidebar tool you switch to. An actual @Claude that anyone on your team can tag in any channel, hand a task, and walk away from while Claude works through it.
The business case is immediate. Today, most AI productivity gains are individual. One person learns a prompt, saves 20 minutes, and the benefit stays with them. Claude Tag is different because the model operates at the team level. One tag. Everyone in the channel can see what Claude is doing, pick up the thread, and redirect it. The context builds across conversations, not within a single chat window.
Anthropic says 65% of their own product team's code is now written by their internal version of Claude Tag. That number is worth pausing on. This is not a beta experiment. They use it on production work. And now it's available to Enterprise and Team customers in beta, today.
This is a PromptHacker Article
The guide includes the full breakdown, setup steps, and team workflow templates.
What Claude Tag Actually Does
Claude Tag starts on Slack because Slack is where most collaborative work already happens. An admin pairs Claude to the workspace, grants it access to specific channels and tools (documents, codebases, databases), sets a monthly spend limit, and Claude is live. From that point on, any team member types @Claude followed by a task and Claude goes to work in a thread.
Three capabilities distinguish it from a chatbot integration:
Multiplayer by design. One @Claude per channel. Anyone can see the work in progress, add context, or redirect it. If a teammate tagged Claude to draft a competitive summary and you have a correction, tag Claude in the same thread and it incorporates it. This is closer to managing a junior analyst than using an AI tool.
Free subscriber access
Keep reading with your free PromptHacker subscription.
Enter the email on your PromptHacker subscription. If access is available, a secure link will arrive in that inbox.
New to PromptHacker? Join the free weekly briefing first.
Three deep dives. Four useful moves. One email worth opening.
PromptHacker turns the AI firehose into practical next steps for work, health, family, and everything time keeps trying to steal.