---
id: "claim-agents-must-live-in-workflow"
type: "claim"
source_timestamps: ["00:02:51", "00:03:00"]
tags: ["adoption", "ux-design"]
related: ["action-deploy-in-slack", "entity-slack"]
confidence: "high"
testable: true
speakers: ["Nate B. Jones"]
sources: ["s06-openai-free-employee"]
sourceVaultSlug: "s06-openai-free-employee"
originDay: 6
---
# Agents Must Live in the Workflow to Succeed

## Claim

Internal AI tools fail for a very boring reason: **people simply forget to open them.** Agents must be deployed directly into the surfaces where work is already occurring.

**Confidence:** High. **Testable:** Yes.

## The Logic

If an agent requires a user to navigate to a separate tab or application (like the standalone ChatGPT interface) to execute a workflow, it becomes an **optional, adjacent task** rather than an integrated part of the job. Optional tools are forgotten tools.

## The Prescription

Deploy agents directly into the surfaces where work happens:

- [[entity-slack-d6|Slack]] channels (primary example) — the agent monitors a channel for inbound requests, processes them, and posts the brief back into the same channel
- SharePoint document repositories
- Email inboxes
- CRM systems

By eliminating context switching, the AI becomes **an unavoidable, helpful participant** in the existing workflow. See [[action-deploy-in-slack]] for the operational step.

## Enrichment Validation

Strongly supported. Studies cited in enrichment indicate **70%+ of internal AI tools go unused** when not native to the user's existing tools (Slack, CRM, email). Context-switching is the dominant predictor of abandonment.