---
id: "action-deploy-in-slack"
type: "action-item"
source_timestamps: ["00:02:51", "00:03:00"]
tags: ["deployment", "user-adoption"]
related: ["claim-agents-must-live-in-workflow", "entity-slack"]
speakers: ["Nate B. Jones"]
action: "Deploy the agent directly into the Slack channel or system where the work already happens."
outcome: "Higher organic adoption rates and elimination of context-switching friction."
sources: ["s06-openai-free-employee"]
sourceVaultSlug: "s06-openai-free-employee"
originDay: 6
---
# Deploy Agents in Existing Work Surfaces

## Action

**Deploy the agent directly into the [[entity-slack-d6|Slack]] channel or system where the work already happens.**

## Expected Outcome

Higher organic adoption rates and elimination of context-switching friction.

## Detail

Do not force your team to open a new tab or log into the ChatGPT interface to use the new agent. Configure the [[concept-workspace-agents|Workspace Agent]] to operate directly within:

- Communication channels ([[entity-slack-d6|Slack]])
- Document repositories (SharePoint, Google Drive)
- Wherever the team already spends their day

**If the agent is adjacent to the work rather than in it, adoption will fail.**

See [[claim-agents-must-live-in-workflow]] for the underlying claim and supporting validation (70%+ of internal AI tools go unused when not native to existing surfaces).