CONNECTED BUSINESS OPERATIONS
Give the right team access to a company WhatsApp number
Share a company number through explicit account grants so customer conversations follow a defined team responsibility.
Company numbers need explicit access responsibility
Shared business communication is governed by access grants, not by everyone knowing a number.
A clear responsibility in your daily work
A shared number should be a conscious business resource. Tsumira distinguishes company accounts from personal accounts and lets administrators manage who may use a company number rather than relying on everyone having access to the same phone.
Grant access deliberately
Choose the colleagues who need the number for their work. An account's connection does not create unrestricted company-wide visibility; explicit grants define the intended access boundary. 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.
- Administrators manage company-number grants.
Review the actual audience
Check access using a representative member account, including whether the person may read or send in the relevant scope. Membership of the same workspace should not be treated as an automatic right to every connected number. 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.
- Verify access for the intended member.
Review the company-number grant
Access is deliberately granted; a company number does not make every conversation universally visible.
| Role | Explicit grant |
|---|---|
| Administrator | Manages grants |
| Member A | Granted |
| Member B | Not granted |
Maintain a clear sender identity
When several employees serve one customer, the company number remains a shared identity with individual responsibilities behind it. Agree who handles the current question and review the external destination before replying. 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.
- Coordinate ownership before replying from the shared account.
A concrete workflow
Prepare the context
Identify the number's business purpose and the small group of employees who actually need access.
Review the decision
Have an administrator grant the appropriate access, then inspect the account and conversation with an intended team member.
Check the result
Review grants when responsibilities change and check that the account's owner and customer-facing usage remain clear.
An illustrative working example
Illustrative working example
A consultancy gives its coordination team access to a company appointment number. Consultants retain separate personal accounts. When a coordinator changes role, an administrator reviews the shared-number grant rather than distributing a device login to another colleague or assuming all customer conversations should become public to the workspace.
Questions about this topic
Who manages company-number access?
Administrators manage explicit account grants. Agree which business role approves access and verify the resulting scope with a representative user.
Do company accounts expose personal numbers?
No. Company grants concern the shared company account. Personal-number privacy follows its separate ownership and conversation-sharing rules.
Can a viewer send customer messages?
Read access and sending rights are not interchangeable. Check the user's permitted role and account scope before assigning customer-response responsibilities.
Does shared access enable campaigns?
No. Company-number access supports deliberate human conversation handling. Bulk sending and AI sending are not available.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
HubSpot
Workflow concept: Clarify company-number responsibility before planning customer communication handoffs.
Google Drive
Workflow concept: Review the preparation step before using an external source: Identify the number's business purpose and the small group of employees who actually need access.
Slack
Workflow concept: Check the actual destination before sharing this result: Have an administrator grant the appropriate access, then inspect the account and conversation with an intended team member.