Channels
One General channel for the whole organisation and topic channels that are open or invite-only. Reading always requires membership, and a channel a person cannot read does not appear to exist.
Team chat
Channels is team chat inside the business system: channels, direct messages and a shared room with each customer. A record placed in a message stays live and shows each reader only what their permissions allow.
In most companies the conversation about an invoice happens in one tool and the invoice lives in another. Someone pastes an amount, a status or a screenshot, and from that moment the message is out of date and visible to people who should not see it. In Tosven a message holds a reference to the record. The card is resolved for each reader, at the moment they read it.
The same applies to customers and to agents. Each customer has one room, opened from the customer record, where the customer writes through a link without an account. Agents are members of channels like colleagues: they post a short line that points to a decision card, and the card shows its current state. Signing still happens in the decision queue, never in chat.
Channels
The list is grouped in a fixed order, so nobody rearranges it and nobody gets lost. A number means somebody needs you: a direct message, a mention or a customer. Ordinary channel activity shows as bold text only.
Sample data · conversation list
One General channel for the whole organisation and topic channels that are open or invite-only. Reading always requires membership, and a channel a person cannot read does not appear to exist.
Private conversations between two people. Owners and administrators have no implicit read access. Access for a legal request goes through a controlled export with a stated reason, and every use is logged.
One room per customer for service communication. The customer reads and writes through an emailed link, without a user account. Their messages are visually marked as external.
Attach an invoice, a customer or a decision card to a message. The message stores a reference only, so the card always shows the current status of the record.
Each reader gets their own view of a card. With read rights: title, key and status. With ledger rights: figures. Without rights: a neutral chip that names only the kind of record.
Agents post under their own identity: a line that links one decision card, and one daily digest per company. An agent reads a channel only while its human manager is a member.
Unread state is one read marker per member, not a counter that drifts. Mark as unread, mute a channel, and still be notified when someone mentions you by name.
Reply to a specific message with its text quoted, without starting a separate thread. Search the internal channels you belong to. Edits keep the earlier version on record.
Each company sets how long internal chat is kept, from 6 to 120 months. A room message linked to an invoice is retained with the accounting records. A legal hold freezes deletion.
In practice
Support asks in the Billing channel whether Vesta Logistics Oy has paid an invoice. Sample data.
Sanna Lind at Nordlys AB has a question about an invoice and no account in Tosven. Sample data.
The morning's collections work appears in General before the team starts. Sample data.
Sample data
When a record is attached, the message keeps its type and its id, and nothing else. No title, amount or status is copied. Each time someone reads the message, the card is resolved under that person's permissions. Notifications, previews and email digests never resolve a card at all. They carry a plain placeholder, so a restricted figure cannot leak through a side channel.
The room replaces the scattered email thread about one customer. The customer opens it from a link sent to an address that is verified as theirs. Reading and writing are separate: a read link lasts up to 90 days, and writing needs a fresh link valid for 24 hours. Customer text is shown as plain text and is never treated as a verified statement.
An agent in a channel is a member with its own identity, not a person's borrowed account. It posts references: a line that links a decision card, or the daily digest. The chip on that line follows the card, so the channel shows whether it was signed or replaced. There is no approve button in chat. The decision queue stays the one place where signatures happen.
Membership decides visibility. A channel someone is not a member of cannot be told apart from one that does not exist. Direct messages are visible to their two participants only. Internal chat follows a retention period chosen per company. Customer room messages are erasable by default and become accounting records only when a person links them to a posted invoice or credit note.
In the field · Engineering and design consultancy
An engineering and design consultancy runs many projects at once, each with its own team, its own client contact and its own billing rhythm. With separate tools, the project discussion sits in a chat application, client questions arrive by email to whoever the client remembers, and the invoice status is known only to finance. Project leads ask the same question every week: has the client paid, and may we continue the next phase.
In Tosven each project team has a topic channel and each client has one room. A project lead attaches the invoice card to a message, and it answers the payment question for as long as the message exists, to the people allowed to know. Client questions about an invoice arrive in the room, where the accountant can link them to the invoice. Collections reminders are announced in General with their decision cards.
Works with
The customer room is opened from the customer's 360 view and follows the contacts recorded there.
Governed AI agentsAgents post decision card links and a daily digest. Signing happens in the decision queue.
Accounting and financeInvoice cards read their status from the ledger, and room messages can be linked to posted invoices.
Status
A separate chat tool cannot know who may see an invoice, so people paste figures into it and the copy goes stale. In Channels the message holds a reference, the card is resolved for each reader, and the status is current. Customer rooms, agent messages and retention follow the same permissions and audit trail as the rest of the system.
They see a neutral chip that names only the kind of record, for example an invoice. It does not show the title, the key or the company, and it looks the same whether the record is restricted, deleted or invalid. Notifications, list previews and email digests never contain record data. They show a fixed placeholder in place of the card.
No. The customer opens the room from a link sent to an address recorded as theirs in Customers. A read link is valid for up to 90 days. To write, the customer asks for a fresh link that is valid for 24 hours. Links stop working when the contact is retired, blocked or erased, and the seller can revoke one at any time.
Not implicitly. A direct message is visible to its two participants. For a legal request there is a controlled export that requires a stated reason, notifies the owners, expires automatically and writes a log entry for every use. The same rule is shown to users in the product, so the privacy promise and the technical behaviour are the same thing.
Threads, reactions, file attachments, presence indicators and push notifications are not part of the pilot. Reply with quote stands in for threads. Record cards cover invoices, customers and decision cards today, with more record types to follow. Agents post references and digests. They do not hold open conversations in channels, and nothing can be approved from a chat message.
Early access
Tosven is in pilot. Tell us about your company and the tools you use today in a few sentences, and we will say plainly whether it is a fit.
sales@tosven.com · No card details and no commitment.