CONNECTED BUSINESS OPERATIONS
Keep personal WhatsApp conversations private by default
Connect a personal number without turning its conversations into a company-wide inbox, and share a conversation only through an explicit decision.
Personal number access starts with the owner
Private ownership and an explicit shared conversation are different boundaries.
No implicit access
A clear responsibility in your daily work
A consultant's personal number can contain both business relationships and private context. Tsumira treats the linked personal account as the owner's account. Workspace membership alone does not make those conversations available to colleagues.
Start with owner-only access
The personal account's privacy boundary applies to conversation access and message discovery. Colleagues should not expect a connected personal number to behave like a shared company account. WhatsApp is an optional module and must be enabled for the workspace before a number can be connected through the configured gateway. Confirm the account's ownership, who is allowed to use it and whether it is a company or personal number before inviting colleagues into the conversation.
- Personal accounts are private to their owner by default.
Share a conversation consciously
If collaboration on a particular customer chat is needed, use explicit sharing rather than treating every conversation as shared. Review the purpose and audience of that decision with the account owner. Access follows the linked account and conversation rules. Personal numbers are private to their owner by default; company numbers use explicit access grants. Internal discussion and external customer messages have different audiences. Review the destination and sender identity before sending any message.
- Conversation sharing is a separate action.
Keep private and shared scopes apart
Sharing a selected conversation is not the same as opening the owner’s entire number.
Only the selected scope
Explicit conversation sharingKeep AI within the same boundary
Search and AI assistance follow the requesting person's permissions. Summarising a chat or asking for a reply draft does not provide a shortcut into someone else's private message history. People send messages deliberately. Bulk sending and AI sending are not supported. Where available, AI can search permitted messages, summarise a chat or propose reply text; it does not gain wider access than the person using it, and a draft still needs human review and sending.
- AI assistance does not bypass personal access rules.
A concrete workflow
Prepare the context
Confirm personal ownership and explain to the owner which account is being linked and how privacy differs from a company number.
Review the decision
Pair the account, then check that an unrelated colleague cannot use it as a shared inbox or search its private messages.
Check the result
For a genuine collaboration need, decide whether to share the relevant conversation and verify the intended audience before continuing.
An illustrative working example
Illustrative working example
A consultant receives a customer's question on a personal number. The conversation remains private while she reads it and prepares a response. When a coordinator needs to assist on that particular matter, they agree an explicit conversation share. The rest of the consultant's account does not become a team knowledge base.
Questions about this topic
Does an administrator automatically gain personal chat access?
Personal accounts are private to the owner by default. Administrative responsibility for the workspace is not a blanket description of access to every private conversation.
Can I share just a relevant conversation?
Explicit conversation sharing exists for collaboration. Treat that as a separate access decision and inspect the intended participants rather than assuming account-wide sharing.
Can colleagues find private messages through AI?
No. Search and AI read access follow the user's permissions; AI does not expose the owner's private history to other workspace members.
When should we use a company number instead?
Choose a company account when the business deliberately needs a shared customer identity with administrator-managed access grants. Personal and company ownership solve different responsibilities.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Notion
Workflow concept: Document personal-number ownership without widening private conversation access.
Google Drive
Workflow concept: Review the preparation step before using an external source: Confirm personal ownership and explain to the owner which account is being linked and how privacy differs from a company number.
Slack
Workflow concept: Check the actual destination before sharing this result: Pair the account, then check that an unrelated colleague cannot use it as a shared inbox or search its private messages.