One number per session
One WhatsApp number links to one session in the workspace. And once a session is linked to a number, it doesn’t accept another one. Together, the two rules stop the same chats from arriving twice.
Rule 1: one number, one session
WhatsApp lets you link a number to several devices, but Corteksa stops it from being linked to 2 sessions in the same workspace. Otherwise the team would get the same chats twice, and 2 people would reply to them.
When the code is scanned with a number that’s already in use, the number is disconnected straight away, the session goes back to Scan QR, and the person linking it gets a notification such as “The number 966512345678 is already linked to the Sales session. Scan with a different number.” The disconnection is recorded in the activity log.
When someone asks for a pairing code for a number that’s already in use, the request is refused straight away, with the name of the session that has the number.
Another workspace can link the same number. And deleting a session frees its number.
Rule 2: a session keeps its number
After the first link, the session remembers its number. If it’s logged out and the code is then scanned with a different number, the scan is refused and the new number is disconnected. The session’s members get a notification, and the person who scanned gets a Wrong number scanned notification.
To link a different number, create a new session.
WhatsApp Cloud and Meta channels
An account or number that’s linked in another workspace is refused, because one account belongs to one workspace only.
If something goes wrong
A real example
A new employee tried to link the sales number to a second session, so he could see the chats on his own account.
- The scan was refused, and he got a notification with the name of the existing session.
- The manager added him as a member of the existing session instead.
The number stayed in one session, and the employee now sees the chats his permissions allow.