WhatsApp group summaries for business, and the memory they leave out
Tracebrain is an AI second brain for companies: it connects to the tools and conversations where the company's work already happens, keeps what was decided, promised, paid and delivered, by client, by contract and by project, and answers, from the app or from any AI assistant, where the company can earn more, with the evidence behind each answer, in a memory the company owns. WhatsApp is one of the sources a company can connect, and this page is about that one; the company memory page is about the product.
This page is for businesses that run client work in WhatsApp groups and have started to ask for a summary of them. It says what WhatsApp's own summaries do, why a summary is the wrong shape for a team, and what a team actually needs from months of group messages.
What WhatsApp's own summaries do
WhatsApp announced Message Summaries in June 2025. We read the announcement on WhatsApp's blog on 2026-10-19, and it says four things worth knowing:
- They summarize unread messages. You open a chat with a pile of messages you have not read, ask for a summary, and get a few lines on what is happening before you read the details.
- They run on Meta AI, privately. WhatsApp says the summary is made without Meta or WhatsApp seeing your messages or the summary, and that nobody else in the chat sees that you asked for one.
- They are off by default. Each person turns them on, and a setting called Advanced Chat Privacy chooses which chats may be used for AI features at all.
- They are not everywhere yet. The rollout started in select markets, with more languages and countries to follow. The announcement does not list them.
For one person catching up on a busy group after a meeting, that is useful. It answers "what did I miss in the last two hours".
Why a summary is the wrong shape for a team
A business asks a different question of its groups: "what do we owe this client, and what do they owe us". A summary of unread messages cannot answer it, for reasons that have nothing to do with how good the model is.
- It starts from zero every time. A summary covers what is unread in one chat at the moment you ask. Last Tuesday's promise was read last Tuesday, so it is in nobody's summary today.
- It belongs to one person. Each summary is made on one phone for one reader, and nobody else sees it. Two colleagues in the same group get two summaries of two different sets of unread messages.
- It sees one chat. A client group, the direct chat with the client's manager and the team's internal group are three chats. The price is agreed in one, the deadline moves in another, and no summary joins them.
- It keeps nothing. The point of a summary is that you can stop reading. Nothing in it is filed by client, dated or handed to the next person who works on the account.
- It leaves with the phone. When the person who ran a client leaves, the direct chats leave in their account. What was agreed there was never written down anywhere the company owns.
A summary is stateless by design: each one forgets the last. A team needs the opposite, a record that grows.
An example: one client, over two months
An invented cleaning company in Kraków looks after three office buildings for an invented property manager. The team has a WhatsApp group with the client, an internal group of its own, and the usual direct chats.
- Week 1, client group. The property manager, Marta, asks for windows on the second building to be added to the monthly round. The team lead, Paweł, says yes, for 900 zł a month from October.
- Week 2, direct chat. Marta asks Paweł to skip the 1 November visit, because the building is closed for the holiday. Paweł agrees.
- Week 4, internal group. The supervisor, Ola, says the client still has not paid the September invoice.
- Week 6, direct chat. Marta promises to pay September together with October, by 10 November. Paweł promises a revised schedule without the holiday visit.
- Week 8. Paweł is on leave. Ola runs the account for two weeks.
Ola can ask WhatsApp to summarize the client group. She gets the last few days of unread messages: a question about keys and a photo of a broken handle. The window price was settled seven weeks ago, the skipped visit and the payment date are in a direct chat she is not in, and the overdue invoice is in her own group, read long ago.
Here is what a memory kept by client holds of the same two months:
Marta Kowal, office buildings
- Week 1: windows on building 2 added to the monthly round, 900 zł a month from October.
- Week 2: no visit on 1 November, the building is closed.
- Marta: September and October paid together by 10 November.
- Paweł: a revised schedule without the holiday visit.
- September invoice unpaid.
- Revised schedule not sent yet.
- Marta Kowal: the client's property manager
- Paweł Nowak: team lead on the account
- Ola Wiśniewska: supervisor
Ola does not need to scroll anything. The price, the skipped visit, the payment date and the schedule Paweł still owes are on one card, each with the week it was said. Her first message to Marta writes itself.
What a business needs from its WhatsApp groups
Five things, in the order their absence costs money:
- One place per client and per project, fed by every chat that mentions them: the client group, the direct chats and the team's own group, whoever on the team had the conversation.
- Promises with names and dates. Who promised what to whom, and by when, so an open promise is visible before it is late.
- Decisions and payments, kept after they are read. A price agreed in week 1 is still the price in week 8.
- The time a message was sent, not when someone read it. A promise made on Wednesday belongs to Wednesday, even if it was read on Friday.
- It stays when people leave. What a conversation settled belongs to the company, even when the phone it happened on does not.
A bot added to a group meets part of the first point and none of the rest: it sees that group, from the day it joined, and none of the direct chats where the payment date was agreed.
What Tracebrain does today
Each member connects their own WhatsApp as a linked device, the way WhatsApp Web connects, and chooses in the setup wizard whether their groups are read beside their one-to-one chats. Both are read read-only. WhatsApp hands a new linked device about three months of history once, at the scan, and every new message after that. Every person they talk to gets a note, and so does every group: everyone who writes in it gets a person note, and a nightly pass reads the busiest groups for the projects and promises in them. Every night gets a review of what was decided, promised and paid, the open promises become tasks, and projects get notes of their own, with their people, their groups and their decisions. In a company's shared memory all of that is written into one set of notes, whoever on the team had the conversation. Claude, ChatGPT or any MCP client can ask the memory questions through the MCP server. How the linked device works, and how to unlink it, is on the WhatsApp connector page.
What it does not do yet, said plainly: the shared memory for a company is in early access, and its price is being set with the first design partners rather than sold from the pricing page. Everything above is live today for one person, and for the companies in early access.
The same argument for teams on Telegram is on Telegram as a team's knowledge base, and what leaves with a person who quits, with a handover sheet to download, is in the knowledge lost when employees leave. The company memory page compares the company brains by the apps they read. To see your own client chats as a memory, start with the people you talk to: Tracebrain has a seven-day free trial for one person, and the pricing page has the details and the way into early access for a company.