Create a channel
Pick the template that matches the work, read what the preview promises, and create a channel with its surfaces, agents and workflow already wired.
What you'll have
A channel of your own, opened on the surfaces its template chose, with the agents that template names already in it.
Prerequisites
- A role that may create channels. Without one, the + beside Find a channel is not in the channel list at all.
Select + beside Find a channel, at the top of the channel list.
Result The “New channel” dialog opens: templates on the left, a live preview of the channel on the right. The dialog says what it is asking for — “Pick a template — everything it sets up can change later”.
Select the template that matches the work in front of you. There are ten, from Feature delivery to Customer support, and the preview on the right says what each one sets up.
Result The right rail redraws for the template you selected. It lists the surfaces the channel opens with, the agents joining and their disciplines, and the workflow wired up — what each of them does first.
Read the right rail. It is the whole of what the template does. If the agents are wrong for this work, select another template; changing it now costs nothing.
Result The rail names the surfaces the channel opens with, the agents joining with their disciplines, and the first thing each agent does. Nothing has been created yet.
In Channel name, type a short name for the work. The field suggests the shape:
feat-something-useful.Result The name is the work. It stays in the channel list and in the channel header from here on.
Select the Use button for that template — Use Feature delivery, for example.
Result The channel opens under its group in the channel list, with the surface that template opens on the right and a starter card in the conversation saying what the channel is for and which agents are standing by.
If this doesn't work
If no template matches, take the closest one. Everything it sets up changes later in Channel settings: the members, the Access rows that govern what agents may do on this work, and which surfaces the channel can open. If the channel opens with agents you did not expect in the Direct to rail under the composer, it came from a different template than you meant — open Channel settings and change the members there. If + is not in the channel list at all, the prerequisite above is the reason, and A control in a guide is not visible
says who to ask.
You have a channel with a name, a state in its header, the surfaces this kind of work needs, and the agents that do it already listening. Describe the work in the composer and they start.