Multi-channel tasks and handoffs

Cross-channel workflows where:

• A task can start in one place and continue elsewhere without losing context.
• Notifications go to the right people on the right surface.
• Agents do not duplicate work or contradict prior messages.

CoWork OS supports many channels; the use case is about routing discipline, not novelty.

• Broad channel coverage reduces “only works in Slack” lock-in.
• Graph and memory features (where configured) reduce repeated cold starts across surfaces.
• Unified execution model means the same guardrails apply regardless of where the user spoke.

1. Pick primary vs secondary channels (where truth lives).
2. Define handoff rules: when to move threads, what summary to pass.
3. Test delivery and permissions per channel.
4. Monitor for duplicate replies or missed escalations.

• Accounts and tokens for each channel you enable.
• Naming for projects so humans and agents align on IDs.
• Privacy review if channels mix personal and work content.

1. Enable one extra channel; mirror a simple workflow.
2. Add a standard handoff template (context blob + next action).
3. Measure latency and error rate for a week.
4. Add channels only when ops load justifies it.

• “Summarize this thread for someone who only reads email.”
• “What context must transfer if we continue in channel B?”
• “List failure modes for cross-posting this update.”

• Users know which channel to use for what.
• Spoilers / privacy rules respected across surfaces.
• Fallback when a channel is down (even if fallback is “human takes over”).

• Split-brain conversations with conflicting instructions.
• Notification overload on every channel.
• Assuming parity—not every channel supports rich formatting or attachments the same way.