One WhatsApp number, your whole team

A WhatsApp account lives on one phone, so on its own one person holds the phone and everyone else waits. whatsappx.si connects the number to a workspace that any number of teammates sign in to with their own accounts.

There are two ways to connect:

1. Scan a QR code from the WhatsApp or WhatsApp Business app you already use. The workspace becomes one of the account's linked devices, like WhatsApp Web, and recent chat history syncs in. One scan covers the whole team: teammates sign in to whatsappx.si, not to WhatsApp, so they do not each use a linked-device slot. WhatsApp's standard linked-devices feature allows up to four linked devices, which work while the phone is offline but log out if the phone is unused for more than 14 days (WhatsApp Help Center).
2. Connect through Meta's official WhatsApp Business Platform (Cloud API) with Meta Embedded Signup inside the app. This is not tied to a phone, supports several Meta numbers per workspace, and is the route we recommend for higher volume, approved templates and automation at scale.

Either way, the team works from the same list of conversations. Owners and admins see every chat and decide who handles it; agents reply in the chats assigned to them.

Assignment attaches one teammate's name to a conversation. Owners and admins see who has each chat, and agents see only the chats assigned to them. That removes the two usual problems of a shared phone:

• Double replies. Two people answer the same question minutes apart, sometimes differently. With assignment, the chat has one owner and the rest of the team leaves it alone.
• Dropped chats. A message sits unanswered because everyone assumes someone else has it. Unread counts show what is waiting, and an unassigned chat with an unread count is an obvious gap for an owner or admin to fill.

Owners and admins can reassign a chat at any time, for example when a teammate goes off shift. Unread counts are shared, not personal, so marking a chat as read clears it for everyone who can see it, and new messages arrive live, with images and documents shown inline.

For example, a three-person support team could have one admin who assigns each new chat to whichever agent is free and reassigns anything untouched for an hour, so each agent's list stays short. A small sales team could instead make every salesperson an admin, so everyone sees all leads, and use assignment only to show who owns each one.

A workspace is the boundary for everything: its connected numbers, members and roles, contacts, automations and settings. Data in one workspace is kept separate from every other workspace, and whatsappx.si supports multiple workspaces per account. That is useful when:

• Two brands or clients should not see each other's chats. For example, an agency could run one workspace per client, with the client's own staff invited as agents and the agency's staff as admins in each.
• Separate teams use separate numbers. For example, a company could keep a sales number and a support number in different workspaces so neither team sees the other's conversations.

One whatsappx.si account can belong to several workspaces, so you do not need a separate sign-in for each.