COMMUNICATION IN CONTEXT
Keep the conversation where the work can explain it.
Discuss supported customer, project and business records in their own conversations, with direct and group chat for discussions that do not belong to one record.
The work record gives the conversation its subject
Replies stay connected to the work people are discussing.
A useful message needs more than a channel name
A question about a quote makes more sense beside the quote than in an unrelated general chat. Tsumira’s conversation system gives supported business records their own communication context. People can follow the work and the discussion together. Direct and group rooms also support conversations that are about people or coordination rather than one particular record, without requiring the team to create a fictional project just to talk.
Choose the right home for the discussion
A supported customer, deal, task, file or other record can have a connected conversation under its module’s rules. The subject identifies the work being discussed. Use that context for questions whose meaning depends on the record. Use direct or group chat when the conversation is not about one business object. The distinction helps a colleague find the discussion later without memorizing who first mentioned it or which general channel they used.
- Conversations for supported records
- Direct and group chat rooms
- Subject-specific context
Keep replies and material in the same context
Supported message replies, mentions, reactions and attachments help a discussion develop without detaching it from the work. A concise reply can answer the actual question instead of creating another independent message with no obvious reference. Files still follow their own attachment and sharing checks. Edit and withdrawal behavior follows the applicable message rules; the existence of a thread is not a promise that every message is forever immutable.
- Replies, mentions and reactions
- Contextual supporting attachments
- Applicable message lifecycle rules
A reply belongs to this subject
A linked file or record does not become visible to everyone.
Let record access govern the conversation
The owning module decides whether the person may see the underlying subject. That authority applies when the communication surface reads or changes the thread. Linking a record from another place does not mean everybody can join its discussion. This is particularly important for private files, personal messages and customer material. When access changes, an old link should not become a permanent back door into the conversation.
- Owning record’s access authority
- Current checks on conversation operations
- No blanket access from a link
A concrete workflow
Identify the work
Open the relevant business record, or choose direct/group chat when no single record is the subject.
Ask in context
Write the question where the facts and related work can be inspected.
Continue the same thread
Use replies and permitted supporting material to keep the discussion understandable.
Return through the record
Before acting later, read the current business state together with the relevant conversation.
An illustrative working example
Illustrative workflow: clarify a quote revision
A colleague has a question about the scope of a specific quote revision. They discuss it through the supported record context, where the team can inspect the relevant work rather than pasting fragments into a general chat. Another colleague replies with the clarification. When the quote is reviewed later, the conversation can be understood alongside its actual record and current access rules.
Questions about this topic
Does every discussion need a project?
No. Direct and group rooms support conversations that do not belong to a single business record. Choose the context that fits.
Can I read a private record’s thread from an old link?
A link does not grant access. The owning module’s current authority is checked for the conversation.
Does attaching a file make it public?
No. Attachments and file sharing retain their applicable checks. A conversation reference does not remove those boundaries.
Are messages guaranteed never to be edited or withdrawn?
No such blanket claim is made. Supported message editing or withdrawal follows the applicable lifecycle and permissions.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
