Claude Tag in Slack: Claude integration as a permanent team member for Nordic companies

Anthropic launched Claude Tag on 23 June 2026. It is a new way to work with Claude, and it starts inside Slack. Claude is added as a member of the team: you give it access to selected channels and connect it to the tools and data you choose, and then anyone in the channel can tag @Claude with a task. The point is not that it is another chatbot. It is that a well thought through Claude integration now sits where the work already happens, remembers the context in the channel, and can solve tasks asynchronously over hours or days.

Anthropic's official announcement of Claude Tag →

What it means for Nordic B2B SaaS

For a Nordic B2B SaaS team, this is Claude living where your people already write to each other. No new app, no extra tab. In practice it is AI workflow automation without a new system to roll out. Find the recurring task that eats hours in a team, research, following up on accounts, tidying up notes, and hand it to @Claude in the channel where the work already happens. Access, memory and spend can be locked down per channel, and there is a log of everything Claude has done and who asked for it. That control is what lets you dare to roll out from one team to several. Measure the hours, and expand from there.

What it means for telemarketing and sales teams

Picture a shared AI sales agent in your sales channel. It remembers the context on accounts, follows up on threads that have stalled, and prepares meetings while you sell. That is AI for revenue operations in practice. Because access is set up as separate identities, your sales Claude only sees the sales tools and data, not the rest of the house. For a telemarketing or sales team that means less manual follow-up work and more time for the conversations that close. Remember that it is still a model with a human in the loop: you decide the access, the boundaries and when it is switched on.

What it means for professional services firms

For a professional services firm, the gain is the asynchronous work. You give Claude a task, research, a draft or tidying up case notes, and you carry on with your own while it solves it in the background. Because memory is locked to the channels you define, you can keep client work separate from the rest. Note two things before you switch it on: the so-called ambient behaviour, where Claude takes the initiative itself, and the fact that Claude does not report from private channels. Both belong in your internal guidelines before it reads along on real client data.

What it means for founders and scale-ups

For a founder or in a scale-up there are two things to watch. It is beta and Slack only right now, so do not build a business critical workflow on it staying unchanged. Anthropic says itself that the goal is to expand to more of the places you work. Note their own figure too: they write that 65 percent of their product teams' code today is made by their internal version of Claude Tag. That is their own figure, not independently verified, but it points to how quickly delegating to several parallel agents is becoming the norm.

The real gain is rarely the tool itself. It lies in a Claude integration that fits the workflows you already have, and that is set up right from the start. That is the kind of work I do for Nordic companies. Read more about internal Claude in your workflows, or write to me before you switch on @Claude on real data.

This work was produced in collaboration with AI. Overall: AI about 66 percent, Kim about 34 percent. Looking only at the production itself: AI about 90 percent, Kim about 10 percent. The human sets the direction, AI delivers the volume.