Run multiple WhatsApp Web accounts in one dashboard

Open WhatsApp Web for a support phone and it works. Open it again for a sales phone and the first session is in the way. People solve this with a separate Chrome profile, a private window, an old laptop, or a phone left unlocked on the desk. Each of those is another place to forget. A message sits unread because it arrived in the browser you were not looking at.

The limit is not your ability to scan a QR code. The limit is that each WhatsApp Web session is a full browser context tied to one number, and those contexts do not share a list. You can be logged into several, and you still cannot see them as one set of lines. Chato is that list. Each number remains a Linked devices session on its own phone. The dashboard is where you read and reply.

You do not install a desktop app. You sign in to Chato in a normal browser, create a session, and scan. The next number is another session, not another browser profile. Name them so the sidebar reads the way your work reads: support, the shop, the client, the after-hours line.

On the phone that owns the number, open WhatsApp and use Linked devices, the same screen you would use for WhatsApp Web. Scan the code Chato shows. That phone stays part of the session. If the code expires before you scan, refresh it on the same session. Do not create a second empty session and then wonder which one is live.

Keep the phone online. If it is off, out of battery, or logged out of WhatsApp, the browser link pauses, just as WhatsApp Web does. Chato does not host the number in the cloud in place of the phone, and it does not convert the line into an official API account. The history stays on WhatsApp. You are looking at it from the dashboard.

Disconnect a session when that number should leave Chato. The WhatsApp account on the phone continues. Unlinking is a dashboard action, not a deletion of the chats on the handset. During the seven-day trial you can connect one session, with no card, and see the inbox before you add the others.

After the second scan, both numbers are in the same account. Switching is a click on the session, not a hunt through browser profiles. Chats do not mix. The support number's customers stay on the support session. You can search inside the session you have open, send text, and send images, video, and PDFs up to 16MB.

People who message any of the linked numbers show up in one contact list, so you can find a person without remembering which tab they used. The conversation you open is still the session they wrote to. Reports sit beside that: which sessions are online, how many messages each has handled, today's volume against the longer total, and average reply time per number. A tab you forgot to open cannot hide a slow line, because the line is in the list even when you are answering a different one.

Naming the session is worth doing on the day you scan. Six months later, a sidebar of phone numbers is harder to trust than a sidebar that says shop, after-hours, and the client whose building you manage. You can keep the handset's own profile name as well. The point of the label in Chato is the job, not a second identity on WhatsApp. Customers still see the WhatsApp account they already message.

If a tool outside WhatsApp needs to drop a note into the workspace, the External API can add a thread that is visibly not a WhatsApp chat. That thread is not delivered on WhatsApp. It keeps a website form or a CRM ping from being confused with a customer who wrote on a linked number.

A common workaround is to let a colleague use the same browser profile, which means they have the whole logged-in Web session and you cannot take it back cleanly. Chato shares one session to a Google email. You pick view-only or view-and-send. They sign in with their own Google account. Until they do, the invite stays pending. When they should stop, you revoke the share and the session disappears for them.

They do not receive your other numbers unless you share those too. A colleague covering the shop line does not inherit the client line. There is no per-chat assignment inside a session: send access means they can reply to the chats on that number. There is no role list and no department tree. The control you have is which numbers you shared, and whether the other person may send.

You are not charged for the colleague. €5 per month, or €48 per year, is the price of the connected number. Two people on one WhatsApp Web-style session are one account. A third number is a third account, whether one person or several open it.

If you need approved template messages, a number that stays online without a phone, or the official WhatsApp Business Platform, scanning QR codes will not get you there. Chato will not pretend otherwise. The page about an inbox without the Business API spells out that boundary.

If what you actually have is two or ten WhatsApp apps, and WhatsApp Web is how you already work, the missing piece is a single list. Connect the first number, confirm the chats look right, then add the next. The phones stay where they are. The browser stops being a row of profiles and becomes one dashboard.

The how-it-works page is the scan itself, step by step. Pricing is per number after the trial. The longer explanation of many numbers in one place, including reports and what sharing does not include, sits on the features page.