Slack allows teams to organize discussions in threads so that individual topics do not overload the main channel. Slack also supports huddles for quick conversations, including a dedicated thread for notes. That is why this page covers two situations: closing a text discussion and documenting the results of a short working conversation.
In practice, a thread is rarely finished when people simply stop typing. It is finished when a reader who joins later can understand what was decided, who does what next, and which questions are still open. Without a closing message, the discussion keeps living in participants' heads — and the channel slowly fills with repeated questions and duplicated work.
When a thread fades out without a resolution, a short closing message separates the agreed decision, the owner, and the open questions.
After a quick voice conversation, the outcome is written into the huddle's notes thread so absent teammates can find it later.
The reason the discussion started
Participants' proposals
Maya, 10:02 — Should we move the client demo to Friday? A few people mentioned conflicts.
Jordan, 10:04 — Friday works for me.
Priya, 10:07 — Or we could keep Thursday and just shorten it.
Sam, 10:15 — Either way. Let's also review the new pricing page before then.
Maya, 10:18 — Sounds good.
The thread ends here. Nobody knows whether the demo moved, who updates the invite, or what happens to the pricing review.
The agreed decision in one sentence
A named owner and the next action
Open questions with a deadline
Where the final summary lives
"Summary: the client demo moves to Friday, 15:00. Owner: Maya updates the calendar invite and confirms with the client by end of day. Open question: whether the pricing page review joins this demo or stays separate — Sam to confirm by Thursday noon. This summary is pinned in the thread."