Work through communications
Route team chat, card discussion, email, Slack, and configured SMS into accountable work without losing context.
Log in or sign up to make these docs interactive
Choose your team, project, or agent to turn guidance into links to the exact place in your workspace.
Use communication channels to meet people where requests arrive, then anchor meaningful work to the appropriate card and project record.
Quick steps
- Choose team chat for general coordination and card activity for a specific, accountable outcome.
- Open the selected agent's Communications and create its email account when it should own inbound and outbound mail.
- For Slack or configured SMS, open Channels, choose Add Channel, and complete the destination-specific setup.
- Send a harmless test message and verify it appears under the intended agent's communications or channel conversation.
- Turn actionable requests into cards with an owner and finish line, then keep decisions and returned artifacts in the card work stream.
- Test ambiguous, unauthorized, and out-of-scope messages and confirm the agent asks, refuses, or escalates instead of guessing.
1. Choose the right conversation surface
Use team chat for general orientation and coordination. Use card
activity to brief, start, steer, and review a specific outcome. Card activity
is where an @mention starts an assigned agent's work and where the resulting
work stream remains visible.
When a chat becomes actionable, create or identify the card rather than leaving ownership and the finish line implicit.
2. Configure an external channel
Open the selected agent's Communications page and create its Email Account when the agent should receive and send mail. Use that address for conversations that should be owned by this agent, then verify a harmless inbound message appears under its communications.
For Slack or text messaging, open the selected agent's Channels page and choose Add Channel. Select Slack and complete the workspace/channel setup, or select SMS only when text messaging has been configured for the deployment. In Slack, mention the agent or use its supported direct-message flow to start a conversation; do not assume every message in a connected workspace is routed to it.
Verify channel identity, team scope, and who can trigger or receive agent work. Use a harmless test conversation before relying on the channel for sensitive or time-critical requests.
3. Turn the request into a bounded outcome
Open the resulting item under Communications to confirm the sender and thread. When a message asks for work, capture its purpose, source, constraints, owner, and definition of done on a card. Link or quote only the context needed to perform and review the task. Preserve the original sender and conversation reference where follow-up may be necessary.
Assign the right agent, then mention it on the card to begin. Do not assume a message arriving in a connected inbox grants the sender authority to choose any agent or external action.
4. Keep decisions with the work
Reply through the channel when that serves the conversation, but record durable decisions, artifacts, and review on the card. If an agent drafts a message, inspect the actual recipient, content, and attachments before a guarded send action is approved.
Use the work stream to follow tool activity and cost. Stop or redirect work if the channel thread and card outcome have diverged.
5. Handle ambiguity safely
Ask for clarification when the sender, destination, or intended consequence is unclear. Avoid turning vague inbound text into a broad autonomous assignment. For recurring well-understood requests, encode the routing and method in a maintained automation or skill.
What good looks like
People can begin in a familiar channel, but the team can still find the owner, instructions, agent work, result, and decision in Delegate. No consequential action depends on reconstructing a private inbox or direct message.