Scenario 7: Bringing an employee up to speed in a Teams or Slack channel

Who and in what situation

Hakan returns after taking a few days off while working on an agency’s client project. Decisions, open tasks and links have accumulated in the channel.

How it is done today

He reads the channel from beginning to end, copies important messages into a document and asks his teammates about his tasks.

How to do it with AI

1. In a Teams chat, he selects Open Copilot at the top right and types “What did I miss? Separate decisions and action items.” [32]
2. In a Teams channel, he selects More actions > Summarize thread or Summarize thread at the end of the thread; he takes into account the minimum requirement of 1000 characters for a thread summary. [32]
3. In Slack, he opens the channel or DM and selects Summarize channel or Summarize conversation from the three-dot menu. Unread messages, the last seven days or a custom date range can be used. [33]
4. In Slack, he opens Recap from the sidebar and reviews the source details. [33]
5. He goes to the source message to verify that the task was actually assigned to him.

Example prompt

Summarize the conversation within {date range} under the headings decisions, changed information, tasks assigned to me, owners, deadlines and unclear points. Show the source message for each item; if there is no source, do not include it.

Evidence and real-world example

No company case study was found. The official Teams and Slack guides document the channel, thread, DM and Recap workflows. [32] [33]

Points to consider

Teams Copilot looks back over 30 days by default; it cannot summarize images, Loop components or shared files. [32] Slack only uses accessible content; conversation summaries are temporary, while Recap data is retained for 90 days. [34] Recap requires a Business+ or Enterprise+ plan. [33]

Sources for this scenario

32. Teams sohbet ve kanallarda Copilot (support.microsoft.com)
33. Slack AI özellikleri rehberi (slack.com)
34. Slack AI güvenliği (slack.com)