PEOPLE, CUSTOMERS & CONTEXT
Talk where the work can move forward.
Combine direct and group conversation with supported record discussions, customer communication and AI assistance that people can inspect.
A separate chat stream cannot explain every business conversation
Some discussion belongs with a customer, task or file. Other discussion is simply between colleagues. Tsumira combines those needs through supported record conversations and direct or group rooms. People can reach each other without losing the business context that makes a message useful. External customer communication and company connections add their own explicit audience rules rather than making every internal conversation public.
Explore each function
See what each capability does, how it works and where it fits into your team’s workflow.
Conversations on records
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.
Internal notes and customer mail
Use internal notes for the team and the supported external lane for customer communication, with recipients and permissions checked before sending.
Message delivery status
Distinguish queued, sending, sent and supported provider outcomes, instead of treating a saved draft or successful request as proof of delivery.
Targeted mentions
Use supported mentions to direct attention within a conversation, while preserving the subject’s audience and current access rules.
Unread and notifications
Use personal unread and notification state across supported conversations, with room-level choices and current record visibility.
AI summaries and reply drafts
Ask AI to summarize accessible thread context or prepare a reply draft, then check the source and edit the result before external communication.
AI in team conversation
Address Tsumira in a supported conversation and use the accessible context for questions, exploration and a reviewable next draft.
Discussion to a work draft
Use accessible conversation context to prepare supported task or document work, then review the actual output and destination before applying it.
Company-to-company collaboration
Establish an accepted company relationship, choose partner conversations and share supported work through deliberate agreements instead of opening the whole workspace.
Choose a record or room that fits the conversation
Ask about a particular supported customer, opportunity, task or file in its connected context. Use direct or group rooms when no one record is the subject. Replies, mentions and supported material keep the discussion understandable. The owning record’s access still governs its conversation, so a reference or notification does not create a blanket right to private content. The thread’s message lifecycle follows its actual edit and withdrawal rules.
- Supported record conversations
- Direct and group rooms
- Context-aware replies and material
Separate audiences and actual communication outcomes
Internal team discussion and supported customer communication are different actions. Review recipient, text and attachments before the external send path. A message’s delivery can move through queued, sending and sent, with later provider evidence where supported. Personal unread and notification context help the team return to relevant work, while room preferences control attention. None of those states is proof that another person understood or accepted a business proposal.
- Internal and external audience boundaries
- Delivery information with the message
- Personal attention and room preferences
Use AI and partner collaboration within their scope
Address Tsumira in a supported conversation to explore an issue, summarize accessible context or prepare a specific work draft. People review the factual result and next action. Full presentation creation and automatic live meeting outputs remain separate development directions. For another Tsumira company, Connect provides accepted relationships, selected partner channels and explicit supported-resource sharing. AI participation and company connection do not remove the permission or audience boundary.
- Contextual AI questions and drafts
- Visible current versus planned capabilities
- Explicit company-to-company collaboration
A concrete workflow
Open the relevant context
Choose the business record or direct/group room for the discussion.
Reach the right people
Ask a focused question, use supported mentions and keep the actual audience clear.
Prepare the next answer
Discuss internally or request a specific AI draft, then check the underlying facts.
Continue through the right action
Use the appropriate reviewed communication or business workflow and read its actual outcome.
An illustrative working example
Illustrative workflow: coordinate a customer revision
A customer revision raises a delivery question. The team discusses it on the supported record, mentions the specialist and asks AI for an outline of open points. After checking the actual messages, the account owner prepares a separate customer response and reviews its recipient. If another connected Tsumira company participates, only the selected channel and explicitly shared scope form that partner conversation.
Questions about this topic
Is this only a general team chat?
No. It includes direct and group rooms alongside supported record-specific conversations, keeping the business context close where available.
Does internal discussion automatically reach the customer?
No. Supported external communication has a separate audience, recipient and delivery action.
Can an old mention or notification open private content?
No extra access is implied. Current subject and related-record authority still apply when information is read.
Can AI or Connect replace all human review?
No. AI output needs factual and action review, and partner collaboration requires accepted relationships, explicit audience and sharing scope.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Slack
Workflow concept: Plan migration of relevant discussions with object context and clear access boundaries.
Microsoft Teams
Workflow concept: Prepare a team communication handover with explicit people and responsibilities.
Gmail
Workflow concept: Review external customer messages separately from internal collaboration.