To catch up on a long Teams chat, open the chat, select Open Copilot in the upper-right corner and send a prompt such as "Summarize what I've missed". Then ask Copilot to draft your reply, copy it into the compose box and edit it. It reads only the chat you opened, and needs a Microsoft 365 Copilot licence.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThe saving is real on threads of 50 messages or more and negligible on three-line exchanges. The risk is also real: a summary can flatten a disagreement or miss a decision buried in a late message. This tutorial gives prompts for each job, shows one long thread handled start to finish, and lists what Copilot cannot see.
What do you need before Copilot appears in a Teams chat?
Microsoft's rollout notice says Copilot Chat in Teams chats, channels, calling and meetings is for users with a Microsoft 365 Copilot licence, on Teams for Windows, Mac and the web, and an administrator must also allow it.
Microsoft's support page for chats and channels does not state a licence itself, so the message centre notice (MC1156360, updated 11 September 2026) is the clearest statement. It says users open Copilot from the icon at the top right of the conversation window. If you cannot see the icon, check three things in order.
- Your administrator has assigned you a Microsoft 365 Copilot licence, and a day or so has passed since they did.
- The Microsoft 365 Copilot app is allowed in Teams app permission and setup policies, since the notice says administrators should check these.
- You are in the desktop or web version of Teams rather than an old client.
If your business has chosen to switch Copilot off for some roles, the admin steps are in our tutorial on turning Copilot off in Teams for some staff.
How do you catch up on a long Teams chat step by step?
Go to Chat, pick the conversation, select Open Copilot at the top right, choose or type a prompt and select Send. Copilot answers in a pane beside the chat.
- Select Chat on the left side of Teams, then pick the one-to-one or group chat.
- Select Open Copilot in the upper-right corner of the chat.
- Under the compose box, choose a suggested prompt or select Show more for others.
- Type your own prompt if you prefer, then select Send.
- Use Sources at the end of the answer to jump to the message a point came from.
Microsoft's suggested prompts include "Summarize what I've missed", a last-month recap prompt, "What did [a member of the chat] say?" and "What links were shared?". Selecting a source scrolls the chat to that exact message, which is the fastest way to verify a claim.
Add a time frame to get a sharper answer
Microsoft says naming a period, like "December 2023" or "last month", makes Copilot consider only messages sent in that period, and the response states the time range it used. Use this every time you return from leave: "Summarise this chat since Monday 10th". If the time frame is larger than Copilot can handle, select Generate next response to read on.
Which prompts work best for catching up?
Ask for a short structure, not a retelling. Decisions, open questions, anything addressed to you and anything that changed is a better request than "summarise".
| You want to know | Prompt to copy |
|---|---|
| The gist | "Summarise what I've missed since [date] in five bullets. Put anything addressed to me first." |
| Decisions | "List every decision made in this chat since [date] with the person who made it and the message it came from." |
| Open questions | "List questions asked in this chat that nobody has answered." |
| What changed | "What changed from the original plan discussed on [date]?" |
| A person's position | "What did [first name] say about the delivery date? Quote the messages." |
| Links and files named | "What links were shared, and what was each one for?" |
| Disagreements | "Where did people disagree? Give each position without taking a side." |
The last prompt guards against the most common failure of summaries, which is to present a contested point as settled.
A worked example: a kitchen fitter returns to a three-day chat
Take an illustrative kitchen fitter who spends three days away. A group chat with the electrician, the plumber, the worktop supplier and the office has grown to about 140 messages about a site delay. He has 15 minutes before a client call.
He opens the chat, selects Open Copilot and sends:
Summarise what I've missed since Monday morning. Give me:
1. The current state of the job in three bullets.
2. Decisions made and who made them.
3. Anything waiting on me.
4. Anything that changes the client's handover date.
Illustrative output, trimmed: three state bullets (first fix done, plumbing delayed a day by a missing part, worktop template booked); two decisions (the plumber moves to Thursday, the office rebooks the template); one item waiting on him (approve a replacement tap model); and a note that the handover date may slip by one day. He selects Sources on the last point and Teams jumps to the electrician's message that said "if the template is Friday we're tight for second fix".
That message was a conditional, not a statement of delay. Copilot had summarised it as "may slip by one day", which is fair, but he would have told the client "slipping" if he had not read the source. He tells the client "possible one-day slip, depends on the template", and then asks Copilot for a draft reply to the group (below). Total time: about six minutes for what would have been twenty of scrolling.
How do you ask Copilot about an earlier decision?
Name the topic and the period, ask for the exact messages, and open the sources. Microsoft's example prompt asks for the main points from last month, and the Sources list lets you confirm each point against the original message.
Find where we agreed the price for the worktop upgrade. Show the message
dates, who agreed, and the figure each time it changed.
Illustrative output: three messages, with figures of $1,840, $1,950 and $1,900, and the last one marked as agreed. The risk is that Copilot picks the wrong message when several talk about price. Open each source, check the figure and the date, and, if the decision matters, copy the original message into your job record, not Copilot's paraphrase.
Remember the window. Microsoft says the default history is 30 days. A decision made six weeks ago needs a prompt that names the period, and you should still verify that it was reached. For anything older, search the chat yourself.
How do you draft a reply with Copilot in Teams?
Ask Copilot in the side pane to draft the reply from the thread, select Copy, paste into the compose box and edit. You can then use Rewrite with Copilot in the compose box to adjust length and tone.
Microsoft's chat page describes the Copy button for pasting an answer into the chat, a channel conversation or anywhere else. It does not give a drafting prompt, so use one like this.
Draft a reply from me to the group. Confirm the plumber's Thursday slot,
say I approve the replacement tap model, ask the electrician whether
second fix is still possible if the template is Friday, and keep it under
80 words. Friendly and direct.
Illustrative output: a 70-word message covering the four points. What you would fix: it will often add a thank-you sentence and a softening phrase you would never write, so cut both. Check the tap model's name against the thread and make sure the question to the electrician is a question, not a statement.
Tune the draft in the compose box
Once pasted, select the text and use Rewrite with Copilot under the compose box, then choose Rewrite or Adjust. Microsoft lists the Adjust options as Make it concise or longer, and Make it sound casual, professional, confident or enthusiastic. Select Replace when you like a version, then Send. You can adjust only part of a message by selecting that part first.
How do you summarise a long channel thread?
In a channel, select More actions on the post and choose Summarize thread, or open the thread and select Summarize thread at the bottom. Microsoft says the thread needs at least 1000 characters before a summary is available.
Channel replies are often long product or quote discussions where the answer is in the third message and the changes in the thirtieth. The thread summary appears in a box you can scroll. For a deeper question, open the thread and select Open Copilot in the upper right, then use the prompts under the compose box, choosing More prompts for suggestions.
For a quick scan of several channel threads in the morning, the thread summary is faster; for a question about one decision, use the pane and the Sources list.
Which Teams Copilot feature suits which job?
Four Copilot features touch Teams messages and each fits a different job. The chat pane answers questions about one conversation, thread summaries digest a channel post, the meeting chat uses a transcript, and the compose box rewrites your own words.
| Feature | Where | Best for | Limit from Microsoft's page |
|---|---|---|---|
| Copilot pane in a chat | Open Copilot, upper right of a one-to-one or group chat | Catch-up, decisions, a person's position, links | 30-day default history; no images, Loop components or files |
| Thread summary | More actions, then Summarize thread, on a channel post | Digesting a long channel reply chain | Needs at least 1000 characters of text |
| Meeting chat | Open Copilot in the meeting's chat | Asking about what was said | Uses the transcript if transcribed, otherwise the chat |
| Rewrite with Copilot | Under the compose box | Making your own draft shorter, clearer or warmer | Works on your text, not on the thread |
Most owners start with the first and the last. The pane gets you up to speed, and the compose-box tool tidies the reply you write.
How should you word replies for the situations that come up most?
Give Copilot the decision you have already made and the tone you want, and ask it to write only the message. It is better at wording than at deciding.
Draft a reply to [first name] that says no to the extra visit this week
but offers next Tuesday. Polite, two sentences, no apology.
Draft a message asking everyone in this chat to confirm by 4pm whether
they can start at 7:30 on Monday. Mention that the delivery arrives at 7:00.
Draft a short message that summarises where we have got to for someone
who has just joined this chat, and ends by asking them for the one thing
we still need from them.
The third is handy when a new person is added to a long group, because you can send the recap yourself instead of leaving them to scroll. Check names, numbers and dates in each draft before sending, since Copilot is paraphrasing a thread it read quickly.
Another example: a nursery manager and a staff group chat
Take an illustrative nursery manager returning on Monday to a staff group chat of 90 messages about covering a sickness absence. She asks Copilot "What cover has been agreed for this week, who is covering which session, and what is still unresolved?" The answer gives three confirmed sessions and one gap on Thursday afternoon. She selects Sources on the gap, finds that one member offered to cover but was never confirmed, and drafts a reply: "[first name], can you confirm Thursday afternoon? Please reply by noon." The chat contains no children's names by house rule, so the summary she can paste into her own notes carries nothing sensitive.
Another example: a craft brewery supplier's customer channel
A craft brewery supplier has a shared channel with a pub group customer. A thread of 25 replies discusses a delivery shortfall. The account manager selects Summarize thread, reads the thread summary, and then opens Copilot to ask "Which of the customer's requests have we not yet answered?" Three are listed. He answers all three in one message, drafted with Copilot, and posts it in the thread. The customer sees one organised reply instead of three sporadic ones.
How do you check a summary before acting on it?
Open Sources for each point that drives an action, check dates and numbers against the message, and look for conditions and doubts that the summary may have dropped. A two-minute check is enough for most threads.
- Pick the two or three points that would make you do something: spend money, change a date, tell a client.
- Select Sources for each and read the original message, not just the highlighted phrase.
- Look one message before and after for qualifiers like "if", "unless" and "provisionally".
- Check any number against the file or quote it refers to; Copilot cannot read attachments in the chat.
- If the answer surprises you, ask a second question from a different angle and see whether the two agree.
What can Copilot not see in a Teams chat?
Microsoft's page says Copilot cannot summarise images, Loop components or files shared in the chat thread, and uses a 30-day history by default. It reads the thread it is opened in, not your other chats.
That produces three blind spots worth planning for.
- Attachments carry decisions. A photo of a damaged unit or a marked-up drawing may hold the real instruction. Copilot's summary will not include them, so scan the files list yourself.
- Loop components. A task list pasted as a Loop component is invisible to the summary. If the group tracks work there, read it separately.
- Other conversations. A decision made on a call or in another chat will not be in the summary. If the group refers to "what we agreed on Tuesday", find out where that was.
When the chat is a meeting chat, Microsoft says Copilot uses the transcript if the meeting was transcribed, and the chat conversation if not. Our tutorial on Copilot in Teams meetings: recaps, actions and privacy settings covers what that depends on.
Is it safe to use Copilot on a chat with customers or staff?
Microsoft says thread summaries use the same data handling, privacy and compliance standards as Copilot in Teams, and Copilot answers from the thread you open. Confidentiality still depends on your own rules about what goes in a chat in the first place.
Practical rules for a small business:
- Keep children's names, medical details and similar personal information out of group chats at a childcare nursery, because a summary inherits whatever the chat contains.
- Do not paste a Copilot summary of an internal argument into a customer-facing channel.
- Ask your administrator how Copilot interactions are stored and who can search them, since your retention settings decide that.
- Treat a summary as a working note, not a record. If it matters later, keep the original messages.
If the spreadsheet step is the slow part when you log decisions from chat, try The Complete Excel Course with AI Integration on Coding Liquids.
A morning routine that fits ten minutes
Run the same four prompts on your busiest chats each morning, in the same order, and do the rest by exception. A routine beats improvising because you notice when something is missing.
- Open the busiest chat and send "Anything addressed to me since yesterday 5pm?"
- Send "List decisions made since yesterday 5pm and any open questions."
- Reply to the items waiting on you using the draft-reply prompt.
- For channels, use Summarize thread on any post with a pile of replies.
- Write one line in your job notes for any decision that changes cost, date or scope.
Before and after: a chat reply
Before: "ok will sort that and let you know on the other thing too thanks". After using the draft prompt and a short edit: "Thursday works for the plumber. I approve the replacement tap, model as listed above. [first name], can second fix still happen if the template is Friday? Please reply by 3pm so I can tell the client." The second message names the decisions and asks a question with a deadline, which is what stops a long chat from growing further.
What mistakes do people make with Copilot in chat?
The biggest are trusting a paraphrase over the source, asking vague questions and forgetting the window. All three have one-step fixes.
A mistake that slips through: the stale answer
Imagine a specialist food importer asks "What did we agree with the producer about the pallet count?" in a chat that has run for two months. Copilot answers from the last 30 days and quotes "6 pallets". The agreement of 8 pallets was made 40 days ago, and 6 was a later revision that was never confirmed. Nothing in the answer is false; it is just limited by the window. The fix is a prompt with an explicit period ("since 1 October") and a habit of opening Sources before quoting a number to a supplier.
A second common mistake is asking for the whole story when you need one answer. "Summarise this chat" returns a generic recap, while "What does the electrician need from me?" returns something you can act on.
What if Copilot gives a thin or wrong answer?
Narrow the question, name the period and the person, and ask for the messages themselves. Thin answers usually mean the prompt was broad or the evidence sits outside the window.
- Answer too generic: replace "summarise" with a specific question, such as "What does [first name] still need from me?"
- Answer misses something you remember: add the period ("since 1 October") and ask "Was there anything about [topic] before that?" to test the 30-day default.
- Answer cuts off: select Generate next response to read the rest.
- Answer contradicts the chat: open Sources, correct Copilot in your next message, and trust the messages over the summary.
- No Copilot icon at all: go back to the licence and policy checks at the top, since that is where the cause almost always sits.
When a thread matters commercially, such as a price or a date promised to a client, treat the original message as the record and the summary as a pointer to it.
How much time does this really save?
Illustrative sums help you decide whether it is worth the seat. If a manager reads 60 messages a day across chats and Copilot cuts the reading by a third on the heaviest days, that might save 10 to 15 minutes. Over 220 working days, ten minutes a day is about 37 hours. Whether that justifies a licence depends on your price and on whether people actually use the feature, so measure for a fortnight before rolling out wider, as our tutorial on rolling out Microsoft 365 Copilot to a small team suggests.
If you want help fitting chat catch-up into how your team works, I offer one-to-one AI consultations for small businesses.
A short etiquette guide for teams using Copilot on chats
Agree three habits so that Copilot makes chats better rather than longer. Write decisions as decisions, put one topic in one thread, and name the person a question is for. A model that summarises well rewards chats that were written clearly.
- Start a decision line with "Decision:" so a prompt for decisions finds it.
- Put the person's name at the start of any question: "[first name], can you confirm..."
- When a thread has run past 50 messages, post a one-line recap yourself so the summary has an anchor.
- Move a long debate to a call and post the outcome back, so the chat holds the result.
Our tutorial on triaging email with Copilot in Outlook covers the same approach for the inbox, so the two habits reinforce each other.
Copilot in Teams chat: what people ask next
How far back does Copilot read in a Teams chat?
Microsoft says Copilot references the message thread it is opened in, with a 30-day history as the default unless you name another time frame. Ask for a month or a date range in the prompt. If the range is above the limit, select Generate next response to see the rest.
Can Copilot summarise files and images shared in the chat?
Not in this feature. Microsoft's page says Copilot cannot summarise images, Loop components or files shared in the chat thread. Open those yourself, or ask Copilot in the Microsoft 365 app to summarise the file separately, then paste the result back into your question.
Does Copilot send the reply for me?
No. Copilot answers in its own pane, and Microsoft's page tells you to select Copy to paste its answer into the chat. You read it, edit it and press Send yourself, so the message goes out in your name only after you have approved it.
Can other people see that I asked Copilot about a chat?
Microsoft's page describes the answers as appearing in your own Copilot pane and does not say other chat members see your prompts. Do not rely on that for sensitive matters. Ask your administrator how Copilot interactions are stored and who can search them in your organisation.
What is the quickest way to summarise a channel conversation?
Select More actions on the channel post, then Summarize thread. Microsoft says a thread needs at least 1000 characters of text before a thread summary can be generated, so very short threads will not produce one. Alternatively open the thread and select Summarize thread at its bottom.
Further reads
- Teams Premium vs Copilot: Which Is Cheaper for AI Meeting Recaps? — Compare ways to get meeting recaps.
- Should You Keep Microsoft 365 Copilot Licences at Renewal? — Audit whether each Copilot seat is used.
- Who in Your Team Actually Needs a Paid AI Licence? — Decide who really needs the paid seat.
- How to Use Copilot in OneNote to Summarise Meeting Notes — Turn meeting notes into actions.
- How to Use Copilot in Planner to Turn Meeting Notes Into a Plan — Turn what you caught up on into a plan.
Browse all AI-for-business tutorials
Sources: Microsoft Support page How to use Microsoft Copilot in Teams chats and channels; Microsoft Support page Rewrite and adjust your messages with Copilot in Microsoft Teams; Microsoft 365 message centre notice MC1156360 (all read 22 November 2026).
