Messaging · agents in the loop

One inbox. Agents and humans in the same thread.

Cowork is the messaging layer over DCS OS. WhatsApp, Slack, email, in-app DMs — all collapse into one threaded inbox. Agents reply alongside humans, with every message ed25519-signed so you have a verifiable record of who said what.

Try Cowork → Connected channels

Unified inbox

One thread, six channels.

Cowork ingests messages from where your customers actually are. No app to install. No new account to remember.

📱

WhatsApp Business

Official WhatsApp Business API — green tick verified. Two-way messaging, templates, broadcasts.

💬

Slack

Slack-native — Cowork appears as a bot in your channels. Threading preserved both ways.

✉️

Email

Inbound + outbound. Reply-tracking via plus-addressing. SPF/DKIM/DMARC ready.

🌐

Web chat widget

Embed a chat bubble on your DCS-built site. Conversations land in the same inbox.

📞

Voice (Twilio)

Inbound calls transcribed in real time. Voicemails summarized. Voice agents answer simple queries.

📨

SMS

For markets where SMS is the dominant channel — same threading, same receipts.

Agents in channel

Agents talk like teammates.

Drop any of 641 specialist agents into a channel by typing @intake or @booking or @support. They reply inline, hand off to humans when stuck, and every message is signed.

🎯

Intent routing

Inbound message → @intake classifies → routes to the right agent or human. Misroutes are signed too (audit-able).

🤝

Agent → human handoff

When an agent isn't sure, it tags an on-call human. Conversation history + summary attached. No lost context.

📋

Memory across threads

Agents read DCS Memory — they remember Maria's last order, allergy notes, preferred table. With explicit consent, signed.

Receipts

Every message signed. Every conversation audit-able.

Selling into a regulated market (banking, healthcare, govt)? Hand customers a CSV export of every message — independently verifiable. Compliance-grade by default.

📜

Per-message receipt

Each message — human or agent — gets an ed25519-signed receipt with content hash, sender SBT, prev_receipt_cid.

🔗

Conversation chain

Receipts hash-chain. The whole thread is one verifiable transcript. Tamper anywhere = chain breaks visibly.

📤

Customer export

One click: download your full message history as a signed bundle. Compliance + DPDP/GDPR-friendly.

Pricing

By active conversation, not by seat.

Starter

$0 · 100 conversations/mo

2 channels, 1 agent, basic templates.

Pro

$49/mo · 5,000 conversations

All channels, unlimited agents, voice, custom domains, audit export.

Sovereign

Talk · self-hosted

For regulated industries. Cowork inside your perimeter, your keys, your retention policy.

FAQ

Common questions.

Is this a Slack/Teams replacement?

No — Cowork sits *on top of* whatever you use. If your team lives in Slack, Cowork appears as a bot. If they live in WhatsApp, Cowork forwards there. We don't ask you to migrate.

How do agents know what to say?

Each agent is configured in Agent Studio with its tools + memory + tone. The Intake agent classifies + routes; specialist agents handle their domain. You can override any reply before it sends with a "human review" workflow.

What about hallucination?

Cowork agents are constrained to your DCS Memory + connected APIs. They can't make up reservations, prices, or facts — they query the source of truth and report back. If they don't know, they ask. Every "I don't know" is also a signed receipt.

Privacy of customer messages?

End-to-end signed but not end-to-end encrypted (Cowork servers see plaintext to route + reply). On Sovereign tier, deploy inside your VPC so no message ever leaves your perimeter. We never train on your customer messages.

WhatsApp green tick?

Yes — Cowork onboards you to the WhatsApp Business API (official Meta channel). Green-tick verification + display name + business profile setup all guided.