Tosven is in pilot. Early access conversations are open for the first companies. Apply

Team chat

Conversations that carry the record, not a copy of it

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.

4
kinds of conversation: general, topic, direct message, customer room
1
shared room for each customer, opened from the customer record
0
figures or titles copied into a message when a record is shared
24 h
lifetime of the link a customer needs before writing in a room

Chat that knows what an invoice is

Read the documentation

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

One list for the team, the customers and the agents

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

Built for work that ends in a record

01

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.

02

Direct messages

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.

03

Customer room

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.

04

Record cards

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.

05

Per-reader permissions

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.

06

Agents as members

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.

07

Unread and mentions

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.

08

Reply with quote and search

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.

09

Retention and legal hold

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

Three conversations, step by step

01

One invoice card, three readers, no stale message

Support asks in the Billing channel whether Vesta Logistics Oy has paid an invoice. Sample data.

  1. 09:02Laura VirtanenAsks whether the customer has paid and attaches the card for INV-2026-0418.
  2. 09:03Sara NyströmSees the card with status Overdue and the open amount, because she has ledger read rights.
  3. 09:04Jonas BergReads the same message. His card shows the invoice key and status, without figures.
  4. 11:20Sara NyströmMatches payment PAY-2026-0391 to the invoice in Ledger. Nobody edits the message.
  5. 11:21Laura VirtanenOpens the channel again. The same card now reads Paid, and she answers the customer.
02

A customer writes in the shared room

Sanna Lind at Nordlys AB has a question about an invoice and no account in Tosven. Sample data.

  1. 10:00Antti KorhonenOpens the Nordlys AB room from the customer view. A link goes to Sanna Lind's verified address.
  2. 10:14Sanna LindFollows the link and reads the room. No account and no password are involved.
  3. 10:16Sanna LindRequests a fresh write link, valid for 24 h, and asks to move the invoice date to 01.11.2026.
  4. 10:31Antti KorhonenReplies in the room. The send button reads that the customer will see the message.
  5. 14:05Sara NyströmLinks Sanna's message to INV-2026-0418 as accounting correspondence. It is kept with the books.
03

An agent reports, a person decides

The morning's collections work appears in General before the team starts. Sample data.

  1. 07:58Collections agentPosts one line in General: a reminder is proposed for Vesta Logistics Oy, with the decision card.
  2. 08:00Ledger agentPosts the daily digest for Kaarna Group: 6 decisions waiting, with a link to the queue.
  3. 08:05Elina KoskinenOpens the queue from the message and signs the reminder there. Nothing is signed in chat.
  4. 08:06Collections agentSends the reminder. The chip on its 07:58 message now reads Signed for every reader.
  5. 08:20Mikko LehtonenReads General. One message tells him what was proposed and that it has been signed.

Sample data

Record cards

A message stores a reference. The reader's rights decide the rest

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.

  • With read rights: title, record key and a live status chip
  • Figures appear only for readers with rights to the ledger
  • No rights, deleted and malformed all look the same to that reader
  • Card kinds today: invoice, customer, decision card and agent digest
Customer room

A room the customer can use without becoming a user

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.

  • Links follow the contact: a retired or erased address stops working
  • The seller can revoke and renew a link, with a reason
  • Record cards are off in customer rooms, so internal data stays internal
  • No marketing in rooms. The room is for service communication
Agents in channels

Agents report in the channel and wait in the queue

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.

  • An agent reads a channel only while its manager is a member
  • If the manager leaves the channel, the agent's next read is empty
  • One digest message per company per day, not a stream of alerts
  • All channel text is treated by agents as untrusted content
Privacy and retention

Clear rules for who can read and how long it is kept

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.

  • Edits and deletions keep the prior text in an append-only history
  • Lowering a retention period shows the count it erases before saving
  • Erasing a person detaches the author and keeps the fact of the message
  • No read receipts and no presence indicators, by design

In the field · Engineering and design consultancy

Project conversations that stay attached to the project's money

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.

With separate tools

  • Invoice status is asked in chat and answered from memory
  • Client emails sit in one engineer's inbox while they are on site
  • Screenshots of amounts circulate in channels with broad membership
  • A dispute about an invoice is reconstructed from three mail threads

In Tosven

  • The invoice card in the project channel shows the current status
  • Each client has one room that the whole account team can read
  • Figures appear only for readers with ledger rights
  • The client's message is linked to the invoice it concerns

A working day

Sample data
  1. 07:58The Collections agent posts in General that a reminder is proposed for Vesta Logistics Oy, with its decision card.
  2. 09:02Laura Virtanen asks in Billing about INV-2026-0418 and attaches the card. Status reads Overdue.
  3. 10:16Sanna Lind writes in the Nordlys AB room through her link and asks to move an invoice date.
  4. 11:21The payment is matched in Ledger. The card in Billing reads Paid, in the same message as before.
  5. 15:30Jonas Berg confirms a site visit in the project channel and mentions Antti Korhonen, who sees a badge at once.

Status

Where it stands today

Live in pilot
  • General, topic channels and direct messages with unread, mentions and mute
  • Record cards for invoices, customers and decision cards, resolved per reader
  • Agent messages with live chips and one daily digest per company
  • Text-only customer room through an emailed link, opened from the customer view
  • Reply with quote, channel search, edit history and a daily email digest
  • Retention periods per company, legal hold and audited access to direct messages
On the way
  • Record cards for deals, quotes, orders and other record types
  • File attachments in channels and customer rooms
  • Threads, at the first real request from a pilot customer
  • Push notifications and instant delivery without polling
  • A notification email to the customer when the team replies in a room

Frequently asked

Questions and answers

hello@tosven.com

Why not keep using the chat tool we already have?

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.

What does someone without permission see on a record card?

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.

Does the customer need an account to use the room?

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.

Can administrators read direct messages?

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.

What is not in Channels yet?

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

Be among the first companies.

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.