Slack client channels move fast. The account lead misses threads, the strategist promises a deck, and the agency owes a recap by Friday. Dock sits next to Slack and Notion as the audit layer. An agent reads the channel, writes a structured recap into Dock, drafts the next deliverable, and waits for the account lead to approve before the reply goes back.
Slack and Notion stay the system of record for the raw data. Dock is the system of record for what the AGENT INTERPRETS. Each Dock row carries a pointer back to the platform record, agent identity, decision, reviewer, and timestamp. The agent re-fetches platform data via fresh API reads when it needs current state.
The Client Channel Recaps surface
| Channel | Thread ts | Client ask | Agent recap | Next action | Owner | Lead review | Notion page |
|---|---|---|---|---|---|---|---|
| #acme-growth | 1717003922 | Q3 paid roadmap | Acme wants a $40k test budget split Meta and TikTok by July 15 | Draft media plan v1 | Strategist (Priya) | Approved by Jordan 05-29 14:02 | notion.so/acme-q3-plan |
| #northwind-brand | 1717061180 | Reaction to logo v3 | CMO rejected v3, wants warmer palette, keeps wordmark | Re-brief design, send v4 by 06-04 | Designer (Tomas) | Pending Jordan review | notion.so/northwind-brand-v4 |
| #helios-launch | 1717094455 | Press timing | Helios pushed launch from 06-10 to 06-24, embargo holds | Update PR sequencing, notify three outlets | PR lead (Mei H.) | Approved by Jordan 05-30 09:18 | notion.so/helios-launch-runbook |
Each row points back to the Slack permalink and the Notion deliverable.
One worked workflow
A strategist runs an agent against #acme-growth every morning at 9. The agent reads new messages, calls the Slack API for fresh thread state, and writes a row to the Client Channel Recaps surface. If the client asked a question, the agent drafts an answer. Jordan, the account lead, opens Dock at 9:30, edits the recap to soften one line, approves, and the agent posts the reply back to Slack under the strategist's name. The Notion page updates with a link to the Dock row.
Why it matters
Agencies bill by hour and ship by deadline. Without an audit layer, agent drafts go straight from Slack to client, and the account lead finds out at the QBR. With Dock in the middle, every agent action has a named reviewer before it leaves the building. The agencies and consulting pillar covers the wider workflow set. Surfaces for research and design reuse the same review primitive. The agent identity model explains why each row names an agent. The agent collaboration primer covers how multiple agents share one surface. The identity primer is the next read if you have not modeled agents as principals.
Slack reports 77 of the Fortune 100 use the platform and 2,500 apps connect to it, which is why agencies live in client channels. Forrester's collaboration research argues that AI adoption fails when employees cannot use the tools effectively, which is the gap a review layer closes.
Try it
Pipe one client channel into Dock this week. Pick the account lead who reviews the most replies. Measure how many drafts they edit before approval.
FAQ
Does Dock replace Slack or Notion? No. Slack stays the conversation. Notion stays the deliverable. Dock holds the agent recap and the sign-off.
Who approves the agent's reply? The account lead named on the Dock row. Approval is a typed action against an authenticated identity, stamped with timestamp and reviewer.
What if the Slack thread changes after the recap? The agent re-fetches the thread on the next run and writes a new row. The old row stays as the historical interpretation.
Can multiple agents share one surface? Yes. Each row carries the agent identity that wrote it. A strategist's agent and a PR agent can both write to recaps without overwriting each other.
Sources
- Slack, About Slack, accessed May 2026.
- Forrester, Collaboration research, accessed May 2026.
