CONNECTED BUSINESS OPERATIONS
Connect a WhatsApp number with a controlled handover
Pair the right number through the configured gateway, check its connection state and establish ownership before customer conversations begin.
Connect a number through an authorised setup
Optional gateway configuration and number pairing precede conversation use.
Check outcome
A clear responsibility in your daily work
A phone number can represent a business, a department or one person's relationships. Connecting it should begin with that distinction. Tsumira's optional connection flow pairs the account through the configured gateway and gives the team a specific account to inspect.
Prepare the number and owner
Confirm that the person responsible for the number can complete pairing and understands how it will be used. Choose company or personal ownership before setup; technical access to a device does not settle the business's sharing policy. 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.
- Agree the account type before pairing.
Complete the pairing flow
Use the available connection controls and complete the device-pairing steps. Check the account's reported connection state rather than assuming that opening the setup screen establishes a usable session. A failed or disconnected session needs attention before relying on it. 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 the actual connected state.
Check the setup boundary
Pairing material belongs in the authorised setup flow, not in a public page.
Optional feature-gated module; configured gateway and number pairing required.
Test the intended scope
After pairing, inspect a representative conversation with the intended user. For company use, review explicit grants; for personal use, confirm the owner's private access. Keep the pairing decision separate from deciding who may read or reply. 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.
- Test access with the real intended user.
A concrete workflow
Prepare the context
Name the responsible owner and choose company or personal use. Confirm the module and gateway are ready before using a customer-facing number.
Review the decision
Complete pairing, inspect connection status and resolve any setup problem before making the account part of a team workflow.
Check the result
Check a permitted conversation and sender identity. Only then introduce the number into customer communication and document the responsible colleague.
An illustrative working example
Illustrative working example
A coordinator prepares a company support number for two employees. The owner completes pairing, then the administrator reviews access grants. One employee checks a customer conversation and the sender identity. If the connection is unavailable, the team keeps using its established contact process rather than assuming messages can already be handled in Tsumira.
Questions about this topic
What is needed before pairing?
The optional module must be enabled and its gateway configured. The number's responsible owner must also be available to complete the pairing process.
Does pairing share every chat with the company?
No. Access depends on company or personal account rules and relevant sharing decisions. Pairing and granting colleagues access are different steps.
Does this imply a particular WhatsApp cloud API?
No. This workflow uses the configured WhatsApp gateway and device pairing. Do not infer a separate provider integration or approved bulk-messaging capability from the connection screen.
How do we know setup is complete?
Inspect the actual connection state and test an allowed conversation with the intended user. A completed form or a visible account name alone is insufficient evidence.
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: Prepare the authorised operator’s gateway setup checklist without exposing pairing secrets.
Google Drive
Workflow concept: Review the preparation step before using an external source: Name the responsible owner and choose company or personal use. Confirm the module and gateway are ready before using a customer-facing number.
Microsoft Teams
Workflow concept: Check the actual destination before sharing this result: Complete pairing, inspect connection status and resolve any setup problem before making the account part of a team workflow.