Chat and Slack
Chat or Slack?
Slack is where your company talks all day. Chat is where a team works one question through with Zero and its agents, and records what it decided.
#claims-ops
Thread · 47 replies · 3 days ago
Should we raise the auto-approval threshold to $250?
I think Dana said yes on the call? Can someone confirm.
Bumping this. Did we land anywhere?
Room · Claims spike, week 39
- Brief: threshold held at zeroDecided
- Sidebar: should answers cite a source?Open
- Decision recorded by DanaLedger
- Check the reopen rateOct 24
The room hears back when the decision comes due
Where the two part ways.
- 1
A room has a brief at the top
Zero keeps a short brief of what's decided, what's open and who needs to act. Anyone can rewrite it, and the room shows when a person did.
- 2
Hard questions go into a sidebar
A few people, or Zero and your agents, work one question through while the room keeps going. Zero drafts the outcome, and a person settles it.
- 3
Decisions leave the conversation
A settled decision goes into Ledger with what you expect to happen, and a proposed change goes into Compass. Each one links back to the room it came from.
- 4
Zero can act across your ZeroWidth work
In a room, Zero reads your maps, files, decisions and flows, and drafts edits to them. Every edit waits for a person to approve it.
- 5
Your own agents sit in the room
Flows your team publishes in Workbench join a room as members, and so can Claude Code running on a teammate's machine.
When Chat is the right choice
- A question keeps coming back because nobody wrote down the answer.
- You want Zero and your agents to work in the open, where the whole team reads them.
- You want decisions recorded with a date to check them.
- Your team already maps, builds and tests its work in ZeroWidth.
Job by job
Where talk happens
Slack: Channels, threads, DMs and huddles for the whole company.
Chat: Rooms for one piece of work, with sidebars for single questions.
Catching up
Slack: Recaps, thread summaries and a daily Today briefing.
Chat: A brief at the top of each room that Zero keeps current and people can rewrite.
Recording a decision
Slack: A message, a pinned post or a canvas someone writes.
Chat: A settled sidebar becomes a Ledger decision with a date to check it.
The assistant
Slack: Slackbot answers from Slack and the apps your admins connect.
Chat: Zero answers from your whole ZeroWidth workspace and drafts edits for approval.
Agents
Slack: Agentforce and partner agents in channels, threads and DMs.
Chat: Workbench flows and Claude Code join rooms as members.
Other tools
Slack: Thousands of apps, an MCP server and an MCP client.
Chat: Zero uses any MCP server your admin connects, and asks a person before it changes anything.
Private work
Slack: Private channels, managed by workspace admins.
Chat: Private rooms that are invisible to owners and admins too.
Talk in Slack. Settle the work in Chat.
Most teams keep Slack for everyday talk and open a room in Chat when a question needs Zero, an agent or a decision on record.
- Workbench flows your team builds can answer in Slack channels.
- Connect Slack's MCP server, and Zero can read the threads behind a question.
- Post the link to a settled decision back in Slack so the channel knows.
Questions
- Can Zero read our Slack?
- Yes, if a workspace admin connects Slack's MCP server. Zero asks a person to approve anything it would change there.
Try Chat with your domain.
Open a room for the question your Slack channel keeps asking.
No website? Describe what you do
If you'd like help with the first changes, talk to us.