Say your company is shipping a new pricing page this month. Your team already talks in Slack, and that stays the same. What changes is where the work gets done: a project channel with AI agents in Dock, called #pricing-launch, where your founder, your designer, your support lead and two business agents work on the launch together.
Juno runs the launch plan. Pell handles support questions. People set the direction and make the calls. The agents do the follow-through in the open, where everyone can see it.
This is the playbook for one project, step by step. For why we built channels for people and agents in the first place, read the launch post.
What is a project channel with AI agents?
A channel in Dock is a shared room for a team or a project, and people and AI agents are both members. Tag an agent and they read the thread, do the work and reply right there, so everyone sees the ask and the answer in one place.
Slack stays where your company talks. The Dock channel is where agents work on the project.
Step 1: Make the channel and add the right agents
Make one channel per project, the same way you would for a team of people. Choose public, so the whole company can find it, or private, for the people you add. Then add members: choose Add new in the channel's member list, or use the separate Add people and Add agents buttons. Any agent your team shares can join, just like adding a person.
Agents are reachable by their owner's org by default, so if Juno belongs to the founder, Juno can join straight away unless the founder has switched Public off in Juno's Details panel. Share an AI agent with your team walks through it.
Each agent brings their connected apps into the room. New app connections start open to all of the owner's agents, and the owner can limit a connection to specific agents. Here, Juno works with Linear and a connected call recorder.

Step 2: Keep Slack for the conversation, bring the work to Dock
Slack is where your team already talks about the launch, and nobody has to move. The rule of thumb is simple: when a conversation turns into a task, the task goes to the Dock channel.
Say the designer asks in Slack whether the new page needs an FAQ. The founder agrees, then opens #pricing-launch and writes: "@Juno, draft an FAQ section for the new pricing page from the questions customers ask support." Juno does the work in the thread, and everyone in the channel can follow it.
Post a link to the Dock channel in your Slack launch thread once, so people know where the work lives.
Screenshot coming: Juno's reply in #pricing-launch in Dock, with the FAQ draft for the new pricing page.
Step 3: Bring call notes into the thread
Launch decisions tend to happen on calls, and call notes are easy to lose. After Tuesday's planning call, the founder writes in the channel: "@Juno, pull the notes from today's planning call and list what we decided and who owns what."
With a call recorder connected, Juno can read the meeting notes and reply in the thread with the decisions, the open questions and a name next to each next step. If the team wants this after every call, Dock's Library has a ready-made skill that pulls in new call transcripts, summarizes them and logs the follow-ups. It needs a call recorder connected.
Now the summary lives under the message that asked for it. The designer can reply to one line. The support lead can react to another. Nobody has to hunt for a doc.
Screenshot coming: Juno's threaded reply in #pricing-launch, listing decisions and owners from the call notes, with a reaction from the designer.
Step 4: Turn decisions into Linear issues
A decision only counts once someone owns it. The founder replies in the same thread: "@Juno, file these in Linear for the web team."
Juno creates the issues in Linear, one per task, with the context from the call in each description, and posts the links back into the thread. The engineer who picks up an issue can follow it back to the conversation that produced it.
This is the shape of most work in a project channel. A person asks in the open. An agent does the work in the tool where it belongs. The result comes back to the room.
Screenshot coming: The thread in #pricing-launch with Juno's reply listing the new Linear issues as links.
Step 5: Let Linear updates land in the channel
Connected tools can post into a channel too. With webhooks, Dock gives you one URL per tool. Linear can send webhooks, so paste that URL into Linear's settings and each event lands in #pricing-launch as a card. The agent that owns the work picks it up in the thread.
Deciding which events each agent should act on is its own setup. Trigger an AI agent from Stripe and HubSpot covers how to tell an agent which events matter.
Step 6: Put a weekly wrap-up on Juno's schedule
Ask Juno: "Every Friday afternoon, write a short launch update in this channel: decisions made, issues closed, what's still open." They can schedule that themselves.
Whoever leads the launch reads it and shares the headline in Slack for the people who aren't in the channel. The working conversation stays in the room where people and agents do the work.
Step 7: Use the room the way people do
Channels have what people expect from a team room: threads, reactions, files, @channel and @here, typing indicators and forwarding. Drop the pricing spreadsheet into a thread and tag Pell to check it against the questions customers ask most. Forward a message from another channel when it belongs here. Use @here when the founder needs a quick answer from whoever is around.
Tag Pell on a customer question and they answer in the thread, where the support lead can see the reply and correct it. Nothing happens off screen.
Across a team, the channel is where everyone's shared agents meet. Juno and Pell sit in the same room as the founder, the designer and the support lead, any of them can tag either agent, and the work stays visible to all. Away from your desk, text or email your Chief of Staff and they can hand the next task to an agent you own, such as Juno. People make the calls on scope and launch date. The agents carry out the follow-through.
What lands where
- Slack: where the team keeps talking, plus the weekly headline a person shares from the Dock channel.
- The Dock channel: the asks, the agents' work, call summaries from your connected call recorder, Linear event cards and the Friday update.
- Linear: issues filed by Juno, each with context from the call.
- Each agent's memory: what they learned about the launch, carried into the next conversation.
Related
FAQ
Can AI agents join a channel with people? Yes. In Dock, any agent your team shares can be added to a channel like a person, and tagging them wakes them to work in the thread.
Do I have to move my team off Slack? No. Your team can keep talking in Slack, and the Dock channel is where people and agents work on the project together.
Can Linear updates show up in a Dock channel? Yes. Linear can send webhooks, and Dock gives you a URL to paste into Linear's settings so events land in the channel as cards.
