A corporate messenger where a conversation turns straight into a result
A decision made in ChatX can be traced back to the conversation it grew out of.
Stage: Working prototype
- Monitor
- Tablet
- Phone
Working today: messaging and tasks, calls with consented recording, meeting transcripts and the org structure. Next: checks with real services and a pilot inside a company. Full scope of work: section 06.
Summary
- Discussion happens in chat, the task sits in a tracker, approval goes by email. One decision is spread across several systems.
- A month later, no one can show where it was taken or how it ended.
- ChatX keeps the whole chain, from a remark in chat to an accepted outcome.
01 — Diagnosis
The decision lives in the conversation; the task answers for it
Work runs across several services: a messenger, a tracker and meeting recording. Each does its own job, and nothing connects them.
-
A gap between conversation and task
The decision is taken in discussion and logged separately in the tracker. Only the person who created the task knows the link.
-
A meeting leaves no trace
Agreements stay in participants’ memories. A month later, a dispute over the wording of a decision cannot be settled.
-
Access follows chats, not structure
Access depends on which chats a person has been added to. The company’s structure changes; access stays the same.
Result: the company cannot reconstruct how a decision was reached, and repeats the mistake in the next cycle.
02 — Approach
One chain instead of scattered services
-
A link, not a copy
A task is created from a message and keeps a link to it. A meeting summary leads to the exact second of the recording. Nothing is carried over by retelling.
-
The server checks permissions
Access is set by a person’s role in the company structure, not by who is in a chat. The interface does not decide what to show.
-
Consent and human confirmation
Recording starts only with every participant’s consent. No task is created automatically: the system suggests, and a person decides.
03 — Scope
From decision to accepted outcome
Each step refers to the previous one, so the chain can be walked back from the outcome to the conversation.
- Conversation
- Meeting and recording
- Decision
- Task
- Execution
- Confirmation
- Acceptance of the outcome
04 — Org structure
The company is a tree, not a staff list
In most services, job title and department are text fields in a profile and have no effect on permissions.
-
Departments as objects
Company, department, division and team are nodes in a tree, not a caption under a name.
-
Responsibility is assigned
Every node has an owner and someone who changes its membership. Delegation is a separate permission.
-
Structure sets visibility
A closed department is visible only to its members; the membership of a branch is changed by the assigned manager or a delegate.
05 — Interface
The prototype in action
A video and screens of the working prototype: messaging, tasks, meetings. It is no longer a concept: you can follow the chain from conversation to task on screen. Phone first; on a computer the same flow appears in a denser layout.
06 — Stage
Working prototype, preparing for a pilot
Done
- Channels, groups, direct messages, voice notes, files, tasks, a calendar with invitations and search that respects access rights
- Audio and video calls; recording only with every participant’s consent
- Meeting transcript, summary and decisions with timestamps; a task is created only after a person confirms it
- Company structure: departments, roles, staffing positions, delegated management
- Automatic notifications to outside services, signed and retried, with a delivery log; access for other programs; a Telegram link
- Two-factor sign-in, an action log, instant updates, use from a phone, interface in Russian and English
- A company wiki with edit history; an in-chat AI assistant (a short overview of a conversation, reply suggestions); time tracking on tasks and a summary
In progress
- Checks with real services: email, calls, transcription, AI assistant, phone notifications
- Checking the Telegram link on a real bot
- Calendar: two-way sync with Google and Outlook (for now, read-only subscription)
Next
- A pilot inside a client company
- Automations: “if X, suggest Y” rules with a log
Looking for. Companies ready to move part of their work into ChatX, and an implementation partner.
07 — Participation
How to take part
I provide access to the system, migration of structure and data, and priority in the development queue.
I expect part of your real work to run in the system, and feedback as you go rather than at the end.
I show how the system is built and the roadmap in person.
Next: project details
Modules, scenarios, roles, what already works and what is next, a gallery and the way into the app.


