Skip to content

Keeping a record when half the decision happened in Teams chat

On this page

A client asks something by email. Your team talks it over in a Teams chat and lands on an answer. That’s a perfectly good way to decide. The only thing missing is the record: the client’s thread still holds the question, and the answer lives somewhere the client can’t see. This page covers what Teams keeps of that chat, what can still change after the fact, and how to put the decision on the record in a few minutes. The Teams behavior described here comes from Microsoft’s documentation, read on October 4, 2026.

Where the decision lives right now

Picture a Tuesday. Dana, a client, emails at 9:40 asking to push her filing to the extension deadline. Sam and Priya, the two partners, settle it in a Teams chat by 4:10. Yes to the extension, and the fee goes up $400 for the second pass.

At 4:10 the firm has decided. Dana hasn’t heard anything. Her email still sits in Sam’s mailbox, unanswered.

The decision exists in two places, and each holds half:

The client’s email threadThe Teams chat
Who can see itDana, and whoever she copiedSam and Priya
What it holdsThe questionThe answer, and how you reached it
Who keeps a copyBoth sides, in their own mailboxesYour Microsoft 365 organization
Who can edit it laterNobody, once sentEach sender, for their own messages

The fix is to carry the answer back to the thread where the question lives. Everything below is about why that’s the right home, and how to do it well.

What Teams keeps of a chat

Unless someone deletes it or a retention policy clears it, a chat from last spring is still there to scroll back through and search. That’s a good working memory. It isn’t quite the same thing as a record, for three reasons.

Senders can change their own messages. Microsoft’s support page on editing or deleting a sent message puts it plainly:

There’s no limit to how many times you can make changes to a sent message.

A sender can also delete a message from More options > Delete, and select Undo to bring it back. So the fee agreed at 4:10 can read differently next month, and the chat shows only the newer wording.

A person who leaves takes their name with them. When a departing colleague’s account is deleted, Microsoft says their name shows as Unknown User, permanently and by design. Their messages can stay in the chat. Who said “yes, go ahead” gets harder to read a year on.

Deleting a chat only clears it for one person. Microsoft’s messaging policy page describes the Delete chat option:

This will only delete the chat content for the user taking the action; other users in the chat will still be able to see all of the messages.

That’s reassuring for the other people in the chat. It also means the record depends on who’s still in it.

Turning off edits and deletes

If your firm wants chat messages to stay as they were sent, an admin can do that in the Teams admin center. Microsoft’s messaging policy page gives this exact case as its example:

For example, you want to make sure that sent messages aren’t deleted or altered. Create a new custom policy named “Retain sent messages” and turn off the following settings

The settings it lists are:

  • Owners can delete sent messages
  • Users can delete sent messages
  • Users can edit sent messages

Assign the policy to the people it should cover, and their messages stay as sent. It’s a sensible setting for a firm where chat carries client decisions. It also means a typo stays a typo, so it’s worth telling the team before it’s switched on.

What a retention policy adds, and who can read it

A retention policy is Microsoft’s tool for keeping, or deleting, Teams messages for a set period. It’s set up in Microsoft Purview, usually by whoever runs your Microsoft 365. With one in place, Microsoft says users can still edit and delete, and the original survives out of sight:

Although users no longer see their edited or deleted messages in Teams, data from these messages is stored in a secured location designed for eDiscovery searches by compliance administrators.

That’s a real safety net. It helps to know its shape before you count on it.

It’s for admins, not for the people in the chat. Microsoft’s retention page for Teams says chat data is copied to a hidden folder in each participant’s mailbox. Channel messages go to a hidden folder in the team’s group mailbox. Those folders “aren’t designed to be directly accessible to users or administrators.” They’re searched with eDiscovery tools. A partner looking for last March’s decision can’t open them from Teams.

It needs the right license. Microsoft says people covered by a Teams retention policy “must have an appropriate license, such as Office 365 E3 or Office 365 A3.” It points to its licensing guidance for other plans. Check yours there before assuming you’re covered.

It doesn’t keep everything. Microsoft lists what Teams retention leaves out:

  • code snippets
  • voice memos recorded in the Teams mobile app
  • thumbnails and announcement images
  • emoji reactions

The messaging policy page adds that read receipts and audio messages “aren’t captured in eDiscovery reporting.” A thumbs-up on “shall we go ahead?” is how plenty of small decisions get made. Retention doesn’t keep it.

It stops at your own organization. Emails and files used in Teams need retention policies of their own. And if someone from another company joins a chat from their own Microsoft 365, their copy sits in their tenant, under their rules.

What you see in Teams isn’t the answer. Microsoft is direct about this:

Messages visible in the Teams app are not an accurate reflection of whether they’re retained or permanently deleted for compliance requirements.

So a retention policy is worth having, especially if a regulator or insurer may ask for your messages one day. It answers “can we recover this?” It doesn’t give the client a copy, or put the answer next to the question.

The quick move is to copy a link to the deciding message and paste it into your notes or an email. Microsoft’s page on linking to a specific message is clear about the limit. Anyone who wasn’t in the original group chat can’t open it.

That makes a message link useful between the people who were there. It doesn’t reach the client, a new colleague, or anyone reviewing the file later.

Writing the decision back into the client’s thread

This is the record that holds. Reply to the client’s own email, in the thread where they asked, and say what was decided. It takes a few minutes, and it does several things at once:

  • The client sees the answer where they asked the question.
  • Both sides keep a copy, each in their own mailbox.
  • A sent email can’t be edited afterward.
  • Anyone who opens the thread later reads the question and the answer together.

A good confirming reply carries four things. Say what was decided, and what it means for the client. Give the date or the next step. Name who’ll do it. Then ask them to say if anything reads differently from what they expected.

For Dana, that reads like this:

Hi Dana, thanks for asking about the extension. We can file by the October deadline instead. That needs a second review pass, so the fee for this year’s return goes from $1,850 to $2,250. Priya will send the updated engagement letter by Friday. If any of that doesn’t match what you had in mind, just reply here.

The reasoning stays in Teams. The client gets the outcome, the number and the next step.

Two Microsoft features look like shortcuts here, and both send something else.

Share to Outlook sends a Teams conversation as an email. For a channel post, Microsoft says it sends “the entire conversation history.” That’s the internal back-and-forth, including the part where Priya wondered whether Dana would mind. It’s rarely what a client should read. What it sends, and when it fits, is covered in sending email from Teams.

Replying to an emailed post in a channel stays in Teams. If Dana’s email was sent into a channel, Microsoft’s channel email page says a reply there “doesn’t send an email reply to the original sender.” The reply has to come from your mailbox. How emails reach a channel in the first place is in emailing a Teams channel.

Which decisions need the email

Not every chat needs a confirming reply. “Who’s got the Henderson file?” is fine left where it is. A decision belongs in the client’s thread when it changes something the client relies on:

  • fees, scope, or what’s included
  • dates, deadlines, and who’s waiting on whom
  • an instruction from the client you’ve agreed to follow
  • advice, or a view on what the client should do
  • anything a colleague promised the client on the firm’s behalf

When the decision is purely internal, a short note in the channel is enough. Something like “Decided: Sam takes Dana’s extension, new fee confirmed, client told by email October 6.” That gives the team one line to find later.

When the thread has more than one client contact, or the question first came to someone else, clients on email, colleagues on Teams walks the full handoff. For the broader question of which surface a thread belongs on from the start, see how email and Microsoft Teams fit together.

Where Point helps between the chat and the reply

The gap in this whole story is the hours between 4:10 and the reply. The chat feels finished, so the client’s email feels handled.

Point reads your Microsoft 365 mailbox, not your Teams chats. So Dana’s email keeps its place in your feed until it’s been answered. It doesn’t drop out of sight because the team already talked. When you’re ready, Point can draft the confirming reply from Dana’s thread for you to edit. You check the figure and the date, and send it from your own address, into the thread she started. The deciding stays in Teams.

How chat and mail can share one ranked list is in chat and email in one ranked feed. The benefits page covers drafting, follow-ups and the rest, so you can weigh it as a whole.

Common questions

Can I just send the client the Teams chat?

You can, with Share to Outlook, but it sends the conversation as it happened. For a channel post, that’s the entire history. Most clients need the outcome, not the discussion. A short reply in their own thread gives them that, and it’s the copy both of you keep.

If a colleague edits a message after we agreed, is the original gone?

From the chat, yes. Teams shows the current wording. If your firm has a Teams retention policy, Microsoft says the original is kept in a secured location for eDiscovery. If you want messages to stay as sent, an admin can turn off editing and deleting in a messaging policy.

Does a thumbs-up in Teams count as agreement?

It may be how your team works, and that’s fine inside the firm. Microsoft’s retention for Teams doesn’t keep emoji reactions, though. If the client’s fees or deadlines turned on that thumbs-up, write the decision into the client’s thread.

What happens to chat history when someone leaves the firm?

Once their account is deleted, Teams shows their name as Unknown User, permanently. With a retention policy in place, Microsoft says their chats move to an inactive mailbox that an admin can still search. A decision that also went to the client by email doesn’t depend on any of this.

Should we just make every client decision in email?

There’s no need. Chat is a good place to work something out with a colleague. The record only needs the outcome, and one reply to the client’s thread carries it.

Ready for a calmer inbox?

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.

Private beta

What you're joining

It runs on the mail you have

Point sits on top of Gmail or Outlook. Your address, your history and your contacts stay exactly as they are, so there is nothing to migrate.

You set how much Point does

Out of the box everything waits for your review, replies included. You hand over only what you trust, one kind of work at a time.

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.