The conversation belongs where the work is.

The decision is in the chat. The record knows nothing about it.

An invoice is disputed. It gets resolved partly in a channel, partly in a direct message, partly in a call nobody wrote down. The decision is to reduce the amount. Four months later the auditor asks why, and the reasoning sits in a channel with 4,000 messages, where the person involved no longer works. The knowledge was never gone. It was simply attached to a tool rather than to a record.

One tool fewer, and the context survives.

Work it out with your own numbers. The smaller part is the licence for a separate chat tool, which at 40 employees reaches four figures a year quickly enough. The larger part is invisible: the minutes that go every day into reconstructing the link between a message and the record it concerned, and the cases where that no longer works because the person has left. If a decision has ever had to be made twice in your company because the original reasoning could not be found, you know the cost of that pattern better than any metric does.

Who this is built for.

The team module is built for Swiss companies with ten to eighty employees whose work is spread across several places: office and building site, workshop and field service, practice and administration. Typically trades and construction, technical services, fiduciary, consulting and healthcare practices, so anywhere several people contribute to the same matter and hardly anyone sits at a desk all day.

It pays off most for people who hold conversations that should stay among those involved: a disputed invoice, a personnel question, a complaint with a name attached. Because an administrator cannot open someone else's conversation, such discussions do not have to move to a private phone, and they stay attached to the record they belong to.

What managing directors and team leads ask first.

Can management or an administrator read along in our conversations?

No. The people who belong to a conversation see it, and that holds for administrators too: an administrator account manages users and settings, it does not open someone else's conversation. That is how it is built, and it is not a switch somebody flips later. Whoever joins reads from the point they joined, not backwards.

Does the AI evaluate our conversations or use them for automation?

The team module is deliberately not connected to the Routines automation, the only module besides the whistleblowing channel. No recurring chain reads conversations, summarises them or carries anything from them into another module. The reason is simple: content that a machine processes further is no longer confidential. The chat assistant has no access to these conversations either. To find something again you search within the team module itself — across the conversations you are a member of, with a jump to the point in the thread.

What is the difference from a group chat on a phone?

The link to the record. A conversation hangs off the project, the ticket or the document, and whoever opens the record finds the discussion next to it. On top of that, the content sits in the business system rather than on private devices: if someone leaves the company, the reasoning behind a decision stays where the record is.

Does it work on a phone, out on the building site?

Yes. Conversations, mentions and the bell look the same on a phone as at the desk, and a reply on the move is one sentence, dictated or typed. Anyone who is mentioned sees it on the bell, everything else waits until someone opens the list. A photo from the site then hangs on the same conversation as the decision that follows from it.

Where do these conversations sit, and what does an AI model get to see?

Your data is hosted in Switzerland. Before anything is sent to an external AI model, our Sensitive Data Guard masks or blocks personal, contract and financial data, only the released, non-identifying content is forwarded, under no-training agreements. In the team module one thing is added: conversation content never enters that chain at all. No message from a conversation is given to an AI model — the search runs inside the module, on your own data.

What happens to the conversations when someone leaves the company?

The account is deactivated, and the conversations on the project, ticket or document remain with the other participants. A successor is added to the conversation and reads from the point she joined, so she does not inherit access to everything that person ever wrote. Decision and reasoning stay on the record where they were made.

If nobody reads along, how do we evidence a decision in an audit?

Those are two different things: the course of the conversation is confidential, the decision has to be traceable. The people involved record the outcome on the matter itself, as a note on the document, as a status change on the ticket or as a task in the project. That is where the audit chain takes hold, with person and timestamp, while the discussion stays where it was held.

Do we have to train our employees for this?

Little. Anyone who has used a chat before finds their way around conversation, mention and bell without instructions. The one new habit is to start a discussion on the right record instead of in a general channel. In practice one rule is enough: if it concerns a project, a ticket or a document, that is where it gets discussed.