The company chat that stays in the company

One place to talk at work, with your Kamzan login and no phone numbers. Direct messages, groups and channels; the files already in Files; a call that opens kMeeting. And, for those who need it, end-to-end encryption as a declared choice, not a slogan.

Work chats do not belong on WhatsApp

The “Office” group on a personal phone, the client’s contract forwarded in a private chat, the colleague who leaves and takes the history with them: that is how work messages slip out of the company’s control, and nobody decided it.

kTalk lives inside Kamzan. You sign in as in every other product, the directory is the company’s, messages are encrypted at rest on servers in Europe like documents in Files. Administrators decide how long messages last, who can create groups and channels, and whether to turn on end-to-end.

Four colleagues at a table in a bright office with laptops and tablets, talking to each other

What you do with it

  • Direct messages and groups

    One-to-one chats, groups of up to 500 people, invitation links that expire, read receipts and presence: your colleagues’ chat stays in the company, not on personal phones.

  • Channels and topics

    Channels where only administrators and moderators write and everyone else reads, plus forum-style topics inside groups and channels: announcements get through, discussions stay in order.

  • Writing and organising messages

    Reply with a quote, mention a colleague or the whole group, correct with version history, pin what matters and find it again with search: the chat stays in order even when it moves fast.

  • Polls, scheduled and disappearing messages

    Decide fast with a poll of up to 12 options, schedule the reminder that repeats every week, let the chat that should not stay disappear on its own: three ways to make time work for you.

  • Files, voice and Kamzan Files

    In kTalk every attachment is encrypted with its own key, photos get a thumbnail and PDFs can be read without downloading them. Voice messages with a waveform, documents attached from Files and saved to Files, chats linked to a file or a folder.

  • Calls with kMeeting

    From a direct message or a group you start a call: it rings for your colleagues, and whoever accepts joins an end-to-end encrypted kMeeting room reserved for the conversation’s members. kMeeting must be active.

  • Security and encryption

    Every kTalk chat is encrypted at rest with your company’s key. With the end-to-end extension (MLS, RFC 9420) new conversations can be read only by participants’ devices: safety verification, multiple devices, backup with a code. What changes between the two modes.

  • Company control

    With kTalk the company decides how long to keep messages, blocks deletion when needed, chooses with user types who creates groups, uploads files or starts calls, and exports chats in full. Notifications without content in emails, installable app, 7 languages.

End-to-end, if you choose it

By default messages are encrypted at rest with the company key, like documents in Files: the server protects them, and that is why it can search them, show them in notifications, export them for the administrator and preserve them for compliance.

With the “Chat with E2EE” extension, new conversations are encrypted between participants’ devices with MLS (RFC 9420), implemented by us on standard primitives: the server only sees ciphertext. Each user verifies the others’ key fingerprints, and an encrypted history with zero-knowledge backup follows whoever changes device.

What changes — and it is right to know beforehand

  • No server-side message search: the server cannot read.
  • Notifications show no text preview.
  • On a new device the history comes from the backup, not from the server.
  • Administrator export and legal preservation are not possible: each user exports from their own device.
  • No scheduled messages and no editing of messages already sent.

Conversations already open stay as they are: upgrading a thread written in the clear would give a false guarantee on old messages.

Frequently asked questions

Can the Kamzan administrator read chats?

In server mode not in the ordinary course, but they can export conversations and preserve them for compliance when the law requires it: the same logic as documents in Files. With end-to-end on they cannot even if they wanted to: the keys live on users’ devices, and each user exports from their own session.

Do I need a phone number?

No. You sign in with the company’s Kamzan access and the directory is your colleagues. On the phone kTalk installs from the browser as an app and receives notifications.

Can I write to someone outside the company?

No: kTalk is the chat between colleagues of the same company, and only people with the company’s Kamzan access join a conversation. To meet clients and suppliers there is kMeeting, where a meeting can be opened to guests.

Are calls part of kTalk?

No, and we do not claim they are: the call button opens kMeeting, the product built for that. If the company has no kMeeting, the button is not there.

Can I turn on end-to-end later?

Yes: from the moment the extension is active, new conversations are born encrypted. Those already open stay in server mode, because a thread written in the clear does not become secret afterwards.