Chats and Comments
Chats in LadVen OS help quickly coordinate with a person, group, department, or task participants. Comments keep the decision next to the work object: task, document, client, opportunity, or project.
The main rule: a discussion may start in chat, but any decision that affects deadline, owner, result, file, or client must remain in the work context.
Where to Find It
Main areas:
- Chats (
/chat) - conversation list, search, unread messages, and mentions; - Conversation (
/chat/:conversationId) - messages, files, replies, reactions, polls, calls, and participants; - Chat integrations (
/chat/integrations) - external channel settings for administrators; - comments inside tasks, CRM, documents, and other work cards.
When to use
- use a direct chat when the question concerns one person;
- use a group or department chat for team coordination;
- use a task chat when the discussion belongs to a specific result;
- leave a comment in a task, CRM card, or document when the message must remain part of work history;
- attach a file or link when context is unclear without it;
- use a call when voice is faster, then record the outcome in text.
Working in a Conversation
In a conversation, watch the title, participants, latest messages, unread marks, and mentions. If there are many messages, search in messages and open the found fragment in its original context.
Replies preserve the chain. Reply to a specific message when discussing a decision, file, question, or correction. Do not start a new thread if the right message already exists.
Messages, Files, and Polls
A message should be short and lead to action. If a file is needed, attach it immediately and name it clearly. If the team must choose an option, use a poll instead of a long chain of votes in text.
Do not send private data, tokens, passwords, internal links, or client files to a chat unless participant access is checked. For documents and client materials, use the linked card and access rights.
Calls
A call is useful for fast alignment, but it does not replace a written trace. After a call, record the outcome in the task, CRM card, or document: what was decided, who owns it, and when it is due.
If the call belongs to a client or task, open the linked context before or right after the conversation.
Comments in Work Cards
Use a comment when the message must stay next to the work. In a comment, record:
- what changed;
- who must act;
- which file or version is used;
- why the deadline, status, or owner changed;
- what counts as the finished result.
If the discussion started in a private chat, move the final decision into the work card comment.
Manager Control
Managers should check:
- important decisions that remain only in private chat;
- tasks with active discussion but no final comment;
- mentions without response;
- files sent to chat instead of a linked document or task;
- calls without a recorded outcome;
- external channels and integrations where client information can appear.
Recommendations
- Write so the recipient understands the action without another clarification.
- Reply in the right thread or to the specific message.
- Mention a person only when action is really required from them.
- Do not replace task comments with private messages.
- Do not publish sensitive data in shared chats.