Join the LadVen OS testing programRequest a demo
Skip to main content

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​

Where to Find It — conceptual guidance, not UI evidence

Main areas:

  • Chats (/chat) - conversation list, search, unread messages, and mentions;
  • Conversation - 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​

When to use — conceptual guidance, not UI evidence

  • 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​

Working in a Conversation — conceptual guidance, not UI evidence

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.

Messages from a service account without its own photo use the LadVen OS mark instead of initials; if that account has a configured photo, the portal keeps it. This distinguishes a system response from an employee message without changing permissions or event authorship.

Message times, day labels, linked-record dates, and read times use the language and format selected for the portal. The time zone can differ separately: if a time looks unexpected, check the device or account time zone.

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​

Messages, Files, and Polls — conceptual guidance, not UI evidence

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.

Forwarding and pins​

Forwarding and pins — conceptual guidance, not UI evidence

Select a useful message and choose Forward to send it to another chat. You can select several messages, find the target chat, and send a copy with the original author and text. Forwarding does not grant access to the original file or object: the recipient still sees only what their permissions allow.

Pin important messages so participants can find them again. Shared pins require the chat permission; in a private or external chat, the pin list may be unavailable. Unpin outdated decisions and keep the current status in the task or other work card.

Pins have extra limits: direct and task chats can use them when the permission is granted, while an ordinary group requires a chat administrator role. An external participant cannot manage shared pins even when the message itself is visible. If a pin is hidden or the action is denied, this is an access restriction, not a missing message.

Calls​

Calls — conceptual guidance, not UI evidence

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.

Call capabilities​

Call capabilities — conceptual guidance, not UI evidence

The call panel can offer audio or video, microphone and camera controls, and screen sharing. The controls depend on call permissions and browser permissions: screen sharing is available only after you join an active call and in a compatible browser. Recording appears only when your organization’s call policy enables it; start and stop it manually, and use only one start-stop cycle per call. Confirm that recording controls are available before promising a recording to participants.

Start, join, end, microphone/camera, SIP invite, and transfer controls can be absent because of call permissions or conversation policy. An incoming call can be dismissed when joining is unavailable; after a connection error, check the call state before retrying so you do not create a second call.

Comments in Work Cards​

Comments in Work Cards — conceptual guidance, not UI evidence

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​

Manager Control — conceptual guidance, not UI evidence

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​

Recommendations — conceptual guidance, not UI evidence

  • 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.

AI helper in the message composer​

AI helper in the message composer — conceptual guidance, not UI evidence

The composer settings menu can run the current text through AI without sending it to the chat. Available actions are Fix typos, Make it business-like, Shorten text, Soften wording, and Structure it. The result arrives as a streaming preview: choose Apply to replace the draft or Hide to keep the original. AI never sends the message automatically and does not verify facts, permissions, or decisions for you.

If AI is unavailable, returns no improvement, or times out, keep the original draft and edit it manually. Do not paste secrets, client data, or amounts into the helper; AI access and policy are checked separately from the right to write in the chat.

When an AI answer includes linked work entities, an entity card may show the readable task or CRM opportunity title with Used: Yes or No access. This describes source visibility, not answer correctness, and it does not change the record. Never use a raw ID as evidence: treat the answer as a draft and check the linked record yourself.

For a read-only check, use only synthetic records: the task Check delivery window — demo and the opportunity Rebranding — demo. Show one card with Used: Yes and the other with No access; do not substitute real names, IDs, or secrets. Current UI caveat: a CRM card in the No access state may show a neutral CRM opportunity instead of Rebranding — demo; until the source issue is fixed, this state is source-blocked and must not be promoted to evidence.

Editing, drafts, and polls​

Editing, drafts, and polls — conceptual guidance, not UI evidence

  • The author of a regular text message can edit it for 30 minutes. System messages, files, and other non-text records are not editable.
  • Hiding a message removes it from the current feed and pinned-message list; it is not a way to correct the decision. Record the outcome in a new entry in the work context.
  • A draft is stored separately for each conversation in the browser: text, reply target, selected files, and poll settings can be restored when you return. It is not a shared archive.
  • If sending fails, the outgoing item enters an error state with Retry and Discard. A retry may upload attachments again, so check that a duplicate was not created.
  • Check each outgoing bubble separately: in a grouped run, one message can fail even when adjacent messages look delivered. The Sending, Queued, or Not delivered badge applies only to that message.
  • Distinguish two failures: an optimistic unsent outbox item offers Retry and Discard; an already-created server message with delivery status queued/failed keeps only the Not delivered badge and has no retry or discard action.
  • A poll can allow multiple choices and revoting. By default, the author or an administrator closes it and results show counts only; enable member closing or voter visibility when needed.

Business Scenarios​

Business Scenarios — conceptual guidance, not UI evidence

Related Sections — conceptual guidance, not UI evidence

Last updated on