Where Did My Channel Reply Go? Mentions, Planner and Sub-threads

In an Insulin channel, the mentions in your message decide who answers it. An @agent-name mention reaches that agent, @All reaches every specialist agent but not the coordinator, a message that mentions nobody in an organization channel goes to Planner, and a message that mentions only people gets no agent reply. The answer itself is delivered into a sub-thread, which you open from the reply badge on the message.

---

You ask your team’s channel a question, and nothing appears under it. Before you conclude that the agents ignored you, check two things: whom your message was addressed to, and where a channel puts an agent’s answer. Both follow documented rules.

Start with three documented outcomes. The message was routed to Planner or to specialist agents, and which ones depends on your mentions. It mentioned only people, so it was treated as a conversation between people and no agent replied. Or the answer was placed in a sub-thread you haven’t opened. When none of the three fits, check the documented conditions that do leave you without an answer.

This post covers who answers and where the answer lands. For what a channel is, its roles and knowledge bases, and why only Planner delegates, see how channels work. Approvals have a post of their own: where the approval gate is armed.

Who answers a message in a channel?

The mentions in your message decide. In an organization channel, specialist agents answer the @mentions they receive, and a message that mentions nobody goes to Planner. Type @ and the autocomplete shows the agents and people in the channel. Each agent carries a role label, such as “researcher” or “reviewer”, so everyone can see which agent serves which purpose.

You write	Who picks it up in an organization channel	What comes back
@agent-name	That agent	Its answer to your message
Two or more @agent-name mentions	Each agent you mention	An answer from each agent to its mention
@All	Every specialist agent in the channel, but not Planner	The specialists’ answers; Planner is not triggered
No mention at all	Planner	Planner plans the work, assigns each part to the member agent best suited to it, and posts a combined summary once they have replied
Only people’s names	No agent	No agent reply: the message is treated as human conversation

Use @All for each specialist’s own answer, and no mention for one plan with a combined summary. The documentation keeps every routing rule for channel agents in one section.

When you mention nobody, Planner answers

Planner is the coordinator of an organization channel: an organization-owned agent that belongs to the channel rather than to any one member. The documentation puts its rule plainly: “A message addressed to nobody is always picked up.” Three details decide what you write next:

• Planner answers without a model of your own. It draws on your organization’s model configuration, so an organization channel answers even when the person writing has no model provider of their own.
• Planner has no integrations, so it names an agent that can do the job. When a request needs email, calendar, files or another third-party system, Planner declines and names the member agent that can do it. @mention that agent next.
• Only Planner delegates. In an organization channel, a specialist’s attempt to pass work to another specialist simply doesn’t happen. To involve several agents, mention each of them, or mention nobody and let Planner assign the parts.

In a personal channel, Insulin coordinates

A personal channel has no Planner; the built-in Insulin agent coordinates instead. It can invoke specialist agents on your behalf, so you can ask a broad question and let Insulin route the work, and specialists there can also hand off to each other. @All does not trigger Insulin either. Insulin, for its part, is not available in an organization channel: it runs with your own connected accounts, which should not be used to answer in a room your teammates read.

Why did no agent reply to my message?

Because a message that @mentions only people, and no agent, is treated as human conversation, and no agent replies, Planner included. The rule that sends an unaddressed message to Planner applies to a message that mentions nobody at all, not to one that mentions people. To bring an agent in, send the request again with the agent’s @mention, or with no mentions so Planner takes it. A personal channel never reaches this case: it holds only you and your own agents.

Where does a channel reply appear?

In a sub-thread, not in the main thread. In a channel, an agent’s reply is delivered into a sub-thread, and the parent message grows a 1 reply or N replies badge that you click to read it. A sub-thread is a nested discussion tied to a specific message. In a solo chat you can start one yourself; in a channel, the badge is the only way in.

Way in	Solo chat	Channel
Hover a message, then click Reply in thread	Starts a new sub-thread, or reopens the existing one	Not offered
Click the 1 reply or N replies badge on a message	Yes	Yes: the only way in

Three things make a delivered reply easy to miss:

• The panel doesn’t open for you. Sending a message in a channel no longer pops the side panel open by itself, which used to interrupt whatever you were reading. Open it yourself while a reply is still being written, and it streams live from that point.
• A sub-thread keeps no unread count. Organization channels carry an unread count in the sidebar, but sub-threads don’t accumulate one, so the badge on the message is the signal to look for.
• An @agent mention opens a different conversation. Clicking an @agent mention in a message switches you to that agent’s solo chat, a separate conversation from the channel. The reply to your channel message stays in the channel’s sub-thread, so go back and open the badge.

The Agents documentation shows how sub-threads work in a solo chat and in a channel, side by side.

What else can stop a channel reply?

Three documented conditions to check: an agent the channel needs cannot get a model, the agent you want isn’t a member, or your connection drops while an agent is still writing in an organization channel. Unlike the three outcomes above, each leaves you without the answer you asked for.

One agent without a model stops the whole turn

In a channel, if any agent the channel needs cannot get a model, the whole turn stops, and none of the channel’s other agents answer it. There is no friendly reply in a channel, not even from the Insulin assistant. Instead, an error card shows the cause, prefixed with that agent’s name and a colon.

The name before the colon tells you whose model access to fix, and the cause after it tells you what to fix:

• The card says your organization has disabled Fours’ hosted models. The agent has nothing to run on until a provider it can draw on is connected or Fours-hosted models are allowed. Organization agents draw on the providers the organization has connected, and Planner on the organization’s model configuration, so the fix belongs to an organization ADMIN: connect a provider that the organization’s AI Model Policy allows, under Settings → Organization → Integrations, or allow Fours-hosted models in that policy. In a personal channel, your own agents draw on the providers you connect under Settings → Integrations.
• The card says Fours’ hosted models could not be reached. The card itself puts that on Fours’ side: retry in a moment.

The Agents documentation walks through how a turn resolves to a model, one organization setting at a time.

The agent you want isn’t a member

In a channel, the agents that can respond are the ones added as members, and the @ autocomplete shows the channel’s agents and people. If the agent you want isn’t there, add it from the Members panel, the members icon in the channel header, which takes the EDITOR role or higher on the channel. An organization channel takes only organization agents, and a personal channel only your own user-level agents.

On an organization channel, your role on the agent matters as well. An agent shared with the whole organization can be added by anyone who can use it; any other organization agent, only by its owner or someone who holds ADMIN on it. The Members panel lists every organization agent either way, so adding one you may not add fails with Failed to add agent.

Your connection dropped in an organization channel

In an organization channel, a dropped connection stops your turn immediately. A one-on-one chat or a personal channel is more forgiving: if you reload the page or lose your connection while an agent is still writing, Insulin waits 30 seconds after it notices you have gone, and the reply carries on if the conversation is open again. An organization channel doesn’t wait for a dropped connection, so if yours dropped mid-reply, send the request again.

What should you check when nothing comes back?

Start with where the answer would be, then check what you wrote, then what could have stopped it.

What you see	What happened	What to do
A 1 reply or N replies badge on the message, but nothing in the main thread	The reply was delivered into a sub-thread, and the panel no longer opens by itself	Click the badge
You clicked an @agent mention, and the reply isn’t in the chat that opened	Clicking an @agent mention switches you to that agent’s solo chat	Go back to the channel and open the badge
No reply and no error, and your message mentions only people	It was treated as human conversation, so no agent replies	Send it again with the agent’s @mention, or with no mentions so Planner takes it
You used @All and got no combined summary	@All addresses the specialists and doesn’t trigger Planner	Mention nobody when you want Planner to plan the work and post a combined summary
Planner declined and named another agent	The request needs email, calendar, files or another third-party system, and Planner has no integrations	@mention the agent it named
An error card that starts with an agent’s name and a colon	That agent couldn’t get a model, so the whole turn stopped and no other agent answered	Fix that agent’s model access, then send the request again
The agent isn’t in the @ autocomplete, or adding it fails with Failed to add agent.	It isn’t a member, and on an organization channel, adding it depends on your role on the agent	Add it from Members; if that fails, ask its owner, or someone with ADMIN on it, to add it
Your connection dropped while an agent was writing	An organization channel stops your turn immediately	Send the request again

Frequently asked questions

Why didn’t any agent reply to my channel message?

If the message mentioned only people, it was treated as human conversation. If an agent answered, look for the 1 reply or N replies badge that opens its sub-thread. If there is no badge, check for a model error, channel membership, or a dropped connection.

Where do agent replies appear in an Insulin channel?

In a sub-thread. The parent message grows a 1 reply or N replies badge, and clicking it is the only way in: Reply in thread isn’t offered in a channel. Sending a message no longer opens the side panel by itself, so open it yourself.

Who answers a channel message that mentions nobody?

In an organization channel, Planner: it plans the work, assigns each part to the member agent best suited to it, and posts a combined summary once they have replied. It draws on the organization’s model configuration, so the writer needs no model provider of their own.

Does @All include Planner?

No. @All addresses every specialist agent in the channel but doesn’t trigger the coordinator: Planner in an organization channel, Insulin in a personal one. Use @All for each specialist’s own answer; mention nobody for Planner’s plan and combined summary.

Why did an error naming one agent stop the whole channel turn?

In a channel, if any agent the channel needs cannot get a model, the whole turn stops. The error card shows the cause, prefixed with that agent’s name and a colon, and none of the other agents answer. Fix that agent’s model access and send again.

Why can’t I add an agent to an organization channel?

Only organization agents can join, and your role on the agent matters: one shared with the whole organization can be added by anyone who can use it, any other only by its owner or someone with ADMIN on it. Otherwise you’ll see “Failed to add agent.”

Takeaways

• Choose mentions deliberately. @agent-name for one agent, @All for every specialist, no mention for Planner, and people’s names alone for no agent at all.
• Open the badge. A channel reply is delivered into a sub-thread.
• Read the name on an error card. It names the agent whose model access stopped the turn.
• Check membership before you mention. Only member agents can respond.

A channel works best when everyone in it knows whom they are asking and where the answer will land. To see what the agents in it can be built to do, start with AI agents for business workflows.