A teammate in the channel.

Everyone has their own AI tab. Your team has a teammate.

The cost of an assistant that lives in a private tab is invisible until you count it: every person briefs it separately, every answer is written for an audience of one, and nothing anyone learns is available to anyone else. Work that belongs to a team ends up rebuilt, quietly, several times over.

Putting 1Presence in the room inverts that. It reads what the channel is about, does the work where everyone can watch, and leaves the answer where the conversation already is. The next person picks up from what it just said instead of starting again.

Both are called Slack and they do genuinely different jobs, so it is worth being exact about which one you want.

Most teams end up with both: the connector so each person's own 1Presence can read their workspaces, and the team agent so the company has a presence where the work is actually discussed.

• Tag it, and it gets to work in the open. It acknowledges in seconds, then edits that same message into a running checklist as it goes — so the channel can see what it is doing rather than watching a silence. The answer lands in the thread when it is done.
• The room is the context. Each channel has its own memory. It knows what this channel is about without anyone re-explaining, and a second person can follow up on the first person's request without briefing it from scratch.
• A different channel is a different memory. What it learns in one room is not carried into another, and none of it touches anyone's personal 1Presence. Rooms, with their own keys.
• Each channel can have its own specialist. Assign an agent per channel and a bare tag runs that one — the researcher in the research channel, the support drafter where customer threads live. Name a different agent inline when you want someone else on it.
• A direct message is still the company's Presence. Message it privately and you get the org's agent, reaching the org's knowledge on the org's account — a private channel of the company, not a personal session. That conversation gets its own memory too.

Invite it to a channel the way you would any Slack app, then tag it with what you want — in plain words, the way you would ask a colleague. A bare tag runs the agent assigned to that channel. Adding an agent's name after the tag runs that one instead.

One practical detail worth knowing before you type: Slack decides the exact handle when the app is installed, and it can differ between workspaces — if something in your workspace already took the obvious name, Slack hands out a variation. So 1Presence reads the real handle back from Slack at install and shows it to you in the admin panel, next to the invite instruction and the channel list. Copy it from there rather than guessing, and if your workspace ended up with a look-alike, the panel says so plainly and names the one that can actually hear you.

An admin maps each person's Slack user to their 1Presence membership once. After that the agent knows who is asking, and everything that follows from identity applies: it addresses them by name, it stays inside the teams that person belongs to, and their usage is attributed to them rather than to an anonymous room.

Colleagues you have not mapped yet can still use it — they are simply not recognised individually, and their work is attributed to the organisation rather than to them. Mapping is worth doing for the regulars and skippable for everyone else.

People from outside your workspace cannot. Guests and outside collaborators in a shared channel are turned away with a short message, because the team agent spends the organisation's credit and reaches the organisation's knowledge — that is for the team, not for whoever happens to be in the room.

Two of them sit on the bot's own tile in your organisation's admin panel, under Connectors: the channel assignments and the activity list. The other two live where they belong rather than duplicated here — an agent's access is granted on that agent, and the balance is your organisation's ordinary billing.

Worth stating precisely, because it is the thing teams are right to ask about. Every message it sends is a reply to someone. It has no standing watch on your channels, sends no unprompted pings, and posts nothing on a schedule.

It replies in two situations. The obvious one is when you tag it. The other is a short courtesy: for a little while after it has answered — in the thread it replied in, or to the same person who just asked it something in that channel — you can carry on without tagging it again, the way you would with a colleague who is clearly still listening. That window is measured in minutes and then closes, and it applies in public channels; in a private channel, tag it each time.

Everything else your team says is discarded the moment it arrives — not stored, not read by an agent, not acted on. Slack delivers channel activity to any app that has been invited into a channel; the difference is what the app does with it, and outside those two windows the answer here is nothing at all.