Channels
Public — open to the whole workspace, private — only to members. Structure discussions by department, project, and stream.
Chat with task context — inside Struktura
Channels, threads, @user, @table, @record mentions. Messages attach to records and land in their timeline. The module is in active development — we're preparing the launch.
demo-стенд · Чат «Команда продаж»
Демо-стенд скоро поднимется.Здесь будет настоящая публичная ссылка на «Чат «Команда продаж»» из продукта.
Module status
The module is in active development
Release is planned for Q2 2026. What's described below is what we're preparing for launch, not what's available today. Subscribe to the announcement to get a beta invite and early access.
What's planned
First-version features
The scope we're working on. The final feature list may be refined after closed beta testing.
Threads
Separate discussions inside messages. Details don't pollute the main channel, and the whole thread stays at hand.
@user, @table, @record mentions
Call a colleague, reference a table or a specific record right from a message. The link expands into a preview with up-to-date field values.
Record attachment
Any message can be pinned to a table card — it automatically lands in the record's timeline and stays in its history.
Archive search
Full-text search across messages, files, and threads. Filters by channel, author, date, and linked table.
Files and reactions
Attachments, image and document previews, emoji reactions on messages. Files live next to the rest of the base's data.
Scenarios
How it will work
Discussion right next to the record
Open a deal or task card — next to it is a thread for that specific record. No need to scroll Telegram for what was said about a client: the conversation lives with the data.
- Thread is tied to the record, not a separate channel
- A new participant sees the whole task conversation at once
- When the task closes the discussion remains in the record's archive
Department channel with its own funnel
Sales has a #sales channel, support has #support. Messages connect to the department's tables and dashboards, and an @table mention expands into a preview right in chat.
- Channels are only visible to those who need them
- Access is configured by workspace roles
- Connect automations: new record → message in channel
@Mention of a client in a support task
The manager writes in the task thread: '@record #1284 — client asks to reschedule'. The record automatically highlights for the owner, and its timeline gets a new activity entry.
- A mention highlights the record and notifies the owner
- Change and discussion history is visible on one card
- No need to duplicate context from the messenger to the CRM
FAQ
Common chat questions
When is the release planned?
We're targeting Q2 2026. The exact date depends on closed beta testing — subscribe to get an early-access invite.
Will there be a mobile app?
At launch chat will work in Struktura's web version (adaptive UI) and in the desktop app. Native mobile clients (iOS/Android) are planned for the next stage after public release.
Can I import history from Slack or Telegram?
We're working on Slack import (workspace export) — it will be in the first version. Telegram is harder due to messenger API limits: we're discussing what's realistic to do.
Will there be end-to-end encryption (E2EE)?
End-to-end encryption is not planned at launch — it's incompatible with server-side search, @record mentions, and the record-timeline attachment. Data is protected by standard encryption in transit (TLS) and at rest, and channel access is by workspace roles.
Will there be message limits?
On the free plan we expect an archive-size limit (last 90 days); on paid plans — full archive without limits. We'll lock the exact numbers closer to release — subscribe and we'll send the final terms.
Want to get into the beta?
We're gathering an early list — we'll send an invite as soon as we open closed testing. No spam: one invite email and one on release day.