Shared agent workflow
Shared Team Workflow Agent
A proof-of-work concept for teams that already live in Slack: tag @Claude, turn messy channel context into structured work, and save the receipt into the workspace your whole team can access.
1
Team channel
4
Work receipts
0
Unsafe auto-sends
Interactive proof
The demo starts in Slack, not another dashboard.
Slack group chat
#customer-ops
Maya, Omar, Justine, @Claude
Maya
in #customer-ops
Customer approved the proposal 🎉 but asked if we can send a revised timeline before Thursday.
Omar
in #customer-ops
I can own procurement follow-up, but I need the latest Drive folder and vendor checklist.
Justine
in #customer-ops
@Claude can you turn this thread into a clear action plan and save the receipt for the team?
@Claude
team member · scoped channel agent
I’ll structure the request, create a workspace receipt, and flag the decisions that still need human approval.
Shared workspace receipt
Saved where the team already works
Receipt
Customer request → action record
- Summary
- Customer request logged · owner assigned · timeline change marked Review · Drive folder linked · draft reply prepared but not sent
- Owner
- Ops lead
- Status
- Needs review
- Destination
- Notion project page + Google Drive folder
- Approval
- Drafts and outbound messages stay review-only until a person approves.
Admin chooses access
Channel setup
Claude is added to selected Slack channels only, with the workspace tools that match the task: Notion, Drive, CRM, or GitHub.
Team tags @Claude
Delegated task
The team keeps talking normally. Someone tags @Claude when the thread needs a summary, action plan, handoff, or receipt.
Notion receipt
Customer request → action record
Saved for everyone
Shared receipt
The answer is not trapped in a private AI chat. It becomes a structured record with owner, status, source, destination, and approval gate.
Main software angle
Slack + @Claude is the current best example.
Agent in the room
A team can tag @Claude inside Slack instead of copying context into a separate AI tab. The work starts where decisions already happen.
Scoped identities
Admins can separate tools, memory, and data by channel or use case, so a sales agent does not need engineering access.
Background work
Claude can take a task, work asynchronously, and come back with a receipt instead of requiring everyone to watch the process live.
Workflow architecture
Chat becomes shared operating memory.
01
Tag the agent
Someone tags @Claude in a Slack channel with a customer request, meeting note, or delivery handoff.
02
Extract the work
The agent separates facts, assumptions, missing data, owners, dates, risks, and draft replies.
03
Save the receipt
The output lands in Notion, Drive, Trello, GitHub, or your team’s chosen workspace.
04
Report back
The agent replies in chat with where it saved the work and what still needs human approval.
01
Slack channel
02
@Claude
03
Notion record
04
Drive folder
05
Human approval
06
Receipt back to chat
Notion
Project page
Decision log, owners, status, blockers
Google Drive
Company folder
Source files, drafts, receipts, exports
Slack
Thread recap
What changed, where saved, what needs approval
Safety layer
The value is access with boundaries, not a bot that sees everything.
What the team gets
- • Shared context instead of private AI chats.
- • Clear owners, statuses, and deadlines.
- • Drafts that stay draft-only until approved.
- • A workspace receipt anyone can find later.
What stays controlled
- • Channel-specific memories and tools.
- • No hidden access to private chats.
- • No auto-sending outbound messages.
- • Sensitive work stays inside company-owned systems.
Adaptation paths
If Slack + @Claude is not your team’s stack, the pattern still travels.
Telegram + Hermes
A founder-led version of the same shared-agent pattern: team chat first, Hermes receipts, approval gates, and saved project memory.
WhatsApp Business
A customer-facing version for official WhatsApp Business/API workflows: incoming inquiries, human handoff, and approved replies.
Workspace destination
Notion, Google Drive, Sheets, or your team’s existing hub can hold the receipt. The tool changes; the operating record stays the same.
GitHub / technical teams
For build teams: issue intake, context summary, implementation plan, draft PR, and human review before merge.
Email / Gmail
For inbox-led teams: summarize intake, draft responses, route owners, and keep all sends human-approved.
Automation glue
Zapier, Make, n8n, or Pipedream can connect older tools when your company already has a mixed stack.
Build-ready proof
A shared team agent should make work easier to find, not harder to trust.
The public concept stays simple: Slack + @Claude first, then adaptations for the tools your team already uses. Behind the scenes, every offer needs a feasibility check, access checklist, and human approval boundary before it becomes real company work.
Back to work