Nobody sets out to make team chat the company archive. It happens anyway. The decision to change supplier was made in a thread. The reason the export runs at 02:00 instead of midnight is in a channel from two years ago. The customer's odd invoicing arrangement was explained once, in a DM, by someone who has since left.
That makes message history less of a feature and more of a record. And records behave badly when someone else controls how far back you are allowed to look.
Chat became the record without anyone deciding
Documents are written on purpose. Chat is written in passing, which is exactly why it is valuable: it captures the reasoning at the time, before anyone tidied it up. The wiki page says what was built. The thread says why, what was tried first, and who objected.
Most teams only notice this when they go looking for something and find a gap. By then the gap is permanent.
What history is actually used for
It is worth being specific, because "we might need it one day" is easy to dismiss.
- Onboarding. A new person reads the last few months of a project channel and learns more about how the team works than any handbook will tell them. Who decides what, which topics are sensitive, which jokes are running.
- Answering "why did we…". Why this vendor, this pricing, this odd exception in the code. The answer is usually a search away, if the messages still exist.
- Customer and support context. Someone in support needs to know what was promised to a customer eighteen months ago. Sales has moved on; the conversation has not.
- Audits and disputes. When an auditor, a lawyer or an unhappy client asks what was agreed and when, "we can't see messages that old" is not a comfortable answer.
- Continuity when people leave. Knowledge walks out of the door with people. What they wrote in shared channels stays, as long as it is kept.
The hidden cost of losing it
Some free plans only show recent messages. Others delete older ones after a set period. The first is a paywall; the second is a shredder. Both are commercially understandable. Both turn your own archive into something you rent back.
The cost rarely shows up as a line item. It shows up as:
- Repeated discussions, because nobody can find the original one.
- Decisions quietly reversed, because the reasoning is gone and the new person in the room does not know it existed.
- Time spent asking colleagues to remember things instead of reading them.
- Pressure to upgrade not because you need new features, but because the old messages are behind the paid tier.
That last one is the subscription-hostage problem. If paying is the only way to read what your own team wrote, the price is no longer a price for software. It is a price for access to your past.
What to ask a vendor before you commit
These questions are dull, which is why they are rarely asked. Ask them anyway, and get the answers in writing if the plan page is vague.
| Question | Why it matters |
|---|---|
| Is message history limited on any plan? | Limits on a free tier often become the reason you upgrade, whether or not you need anything else. |
| Is anything deleted, or only hidden? | Hidden messages come back when you pay. Deleted ones do not. |
| What happens if we downgrade? | You want to know that moving to a cheaper plan does not remove data. |
| Can we export, and on which plan? | An export is your exit. Check what it covers: channels, DMs, files. |
| Does search still work well after years? | Keeping messages is half the job. Finding them is the other half. |
| Where is the data stored? | Relevant for audits, contracts and data-protection questions. |
If you are comparing hosting location as well, the EU-hosted team chat guide covers the questions worth asking there.
How to keep history useful rather than a landfill
Full history is only an asset if you can use it. Years of unstructured chatter is a landfill with a search box. A few habits make a large difference.
Use threads for anything with a beginning and an end
A question, its discussion and its answer belong together. In a thread, they stay together and can be found as one unit. In the main channel, they are interleaved with lunch plans.
Pin what people will look for
Each channel has a handful of messages people keep asking about: the process, the contact, the link to the current plan. Pin them. It takes a second and saves the same question being asked every month.
Keep a decision log
Decisions are the most valuable thing in the archive and the hardest to find, because they look like any other message. Marking them explicitly, in the place they were made, turns history into something you can scan. The decision log guide explains a lightweight way to do this.
Learn the search filters
Most people type a word and scroll. Filtering by who wrote it, which channel, whether it had a file, and a date range turns a vague memory ("Ana said something about the contract in spring") into a short list.
Let short-lived channels end
Events, incidents and small projects deserve their own channel, and that channel deserves an end date. Archiving it keeps the history searchable while taking it out of everyone's sidebar. A channel that closes itself on a set date is tidier than one somebody remembers to close.
How Tandly handles history
Tandly keeps full message history and search on every plan, Free included. The Free plan covers up to 10 active members and 5 GB of storage; nothing about it hides older messages. Downgrading from a paid plan never deletes data. Admin export of channels and files is part of the Business plan. The full breakdown is on the pricing page.
To keep that history usable, Tandly has threads, pins and bookmarks, a decision log in every channel, and full-text search with filters: from:, in:, has:, is:thread, before:, after: and during:. Temporary channels can archive themselves on a date you choose, with a reminder to the creator the day before. Messages and files are stored in the EU.
Questions people ask
Isn't old chat mostly noise?
Much of it, yes. The point is not that every message matters, but that you cannot know in advance which ones will. The cheap message about why a supplier was dropped becomes important the day someone suggests using them again. Good search and a few habits keep the noise from getting in the way.
Should we set a retention period anyway?
Possibly, for legal or policy reasons, and that is a decision your organisation should make deliberately. The problem is having a retention period chosen for you by a pricing tier. Your policy, your call.
We already have a wiki. Isn't that enough?
A wiki holds what someone decided to write down. Chat holds what actually happened, including the reasoning that never made it into the wiki. They complement each other. Losing either leaves gaps.
What if we want to leave later?
Check export before you start, not when you are leaving. If you are moving from another tool now, the guide to moving team chat in an afternoon covers bringing your history with you.