TeamDay in Slack: Your AI Employees Now Live Where Your Team Works

Your team already talks in Slack. Your standups happen there. Your incidents happen there. Your half-written decisions sit in threads you’ll never return to.

And yet, to talk to your AI agents, you’ve been switching tabs, pasting context, and losing the continuity that makes teamwork actually work.

That changes today. TeamDay now runs as a native Slack bot. Mention @TeamDay in any channel, or DM the bot directly, and your AI employee replies in a thread — with access to every tool, every skill, and every integration they already have.

What just shipped

Three things, in order of how much they’ll change your day:

1. @mention your agents from any channel. Invite the TeamDay bot into a channel, mention it, and any agent you’ve wired up can reply inside the thread. The bot adds a 👀 reaction while it’s working, so you always know it’s on it.

2. DM your agents privately. Some questions don’t belong in a channel. Open a DM with the bot, type normally — same agent, same tools, no audience.

3. Slack as a tool for every agent. If you also want your agents to act on Slack content — summarise threads, post updates, search history — you can now add Slack as an MCP in the Space settings. Both capabilities work independently. Turn on whichever ones match how you want to work.

Why this is different from a generic Slack MCP

There’s already a decent ecosystem of Slack MCP servers — including the one we wrote a guide about. Those let an AI tool running somewhere else reach into Slack.

TeamDay in Slack runs in the other direction:

Generic Slack MCP:   [Your AI tool] --talks-to--> [Slack]
TeamDay in Slack:    [You, in Slack] --talks-to--> [Your AI employees]

Both are useful. Most teams end up with both. But the second one is what changes the texture of a working day — because it moves the interface to the software you already have open at 9:14 AM.

How it works under the hood

Three design decisions that matter if you’re evaluating this.

One thread, one memory

Every Slack thread maps to a single agent session. The first mention creates a fresh context; every reply inside that thread resumes the same Claude SDK session. Two separate threads in the same channel run in parallel with independent memory. This mirrors how your team already thinks about Slack — threads are units of conversation, not channels.

Per-org, per-space isolation

Each TeamDay organisation creates their own Slack App and stores their own tokens per-Space. There’s no shared bot, no shared state, no cross-tenant surface. Even inside one org, you can wire different Spaces to different workspaces — one Space for your internal team, another for a client workspace, a third for a community you moderate.

Socket Mode, not webhooks

Setup is about ten minutes and needs no public URL. Slack opens an outbound WebSocket to your TeamDay App; we route events into your agent runtime, stream the reply back, and post in-thread. No ngrok, no HMAC verification, no receiving infrastructure to maintain.

Five patterns teams are already using

Standup summariser. Drop the bot into #standup. Every morning at 10am a scheduled agent reads the overnight messages, posts a synthesis in #exec, and flags blockers directly at the person who mentioned one.

Incident pair programmer. During an incident, mention the bot in #incidents and ask it to pull logs, check Sentry, and suggest hypotheses. Every reply lives in the same thread, so when the postmortem happens, the full AI context is already threaded.

Decision documenter. When a decision crystallises in a thread, mention the bot: “capture this decision with the rationale above and file it under docs/decisions/.” The agent writes, commits, and replies with the link.

Sales research on demand. A salesperson drops a prospect URL into a DM with the bot: “pull everything you can find on this company and their last two funding rounds.” Thirty seconds later, a research brief.

Cross-team translator. Engineering and marketing speak different languages. Paste the engineering PRD into the bot, ask for a marketing brief — it rewrites in your team’s tone because your team’s tone lives in the agent’s system prompt.

None of these are custom-coded integrations. They’re the default behaviour once you mention an agent in a channel.

What this replaces

Honestly? Mostly it replaces a browser tab.

But more interestingly, it replaces the latency between “I want to talk to the agent” and “I’m talking to the agent.” Switching tabs, waiting for the app to load, scrolling to find the right conversation, pasting context — that’s the friction tax you’ve been paying. A Slack mention is zero-friction.

And for teams where several people want to see the same agent exchange, threading it in Slack gives you the audit trail for free. No more “can you share what the AI said?” Everyone who can read the channel can read the thread.

Setting it up

Ten minutes, one Slack App, three tokens. The Slack Integration guide walks through every step — creating the app, enabling Socket Mode, adding bot scopes, and linking it to your Space.

The short version:

Create a Slack App → Enable Socket Mode → copy the xapp- token
Add bot scopes (app_mentions:read, chat:write, reactions:write, im:history)
Install to workspace → copy the xoxb- token + signing secret
Paste all three into TeamDay’s Slack integration
Invite the bot to a channel and mention it

That’s the whole loop.

What’s next

This is the first version. Three things on the immediate roadmap:

Slash commands. /teamday start a new project called "Q3 OKRs" — creates the Space, configures the agent, posts the link in-thread.

Slack AI assistant panel. Native support for Slack’s new AI assistant sidebar, so your agent shows up next to Slack’s own AI rather than as just a chat bot.

Workflow triggers. Trigger a TeamDay mission from a Slack workflow — “when a new message appears in #sales-leads, send it to the Lead Qualifier agent and reply with the verdict.”

If one of these would change your day, let us know which one and how — that’s how we pick what to build first.

Try it

If you’re already on TeamDay, the integration is live today — follow the setup guide.

If you’re not yet on TeamDay, start here. The Slack integration is included in every plan, including the free tier.

Your AI employees now work where your team works. Go mention one.