Frequently asked questions

MultiChats is a shared team inbox for businesses that run several WhatsApp numbers. It connects each number to one console where a team answers together, mirrors the conversation history into your own database, and exposes both a REST API for sending and a webhook that forwards every message to your own backend.

The WhatsApp Business app is built for one number on one phone, and WhatsApp Web mirrors that single device in a browser tab. MultiChats is built for the other situation: several numbers, several agents, and a business that needs the conversation data in its own systems. Each number is linked once by QR code and then answered by whichever team members you assign to it.

There is no fixed product limit. Each connected number runs its own browser session on a server, so the practical ceiling is the memory of the machines you run — roughly 2 GB per active number — and numbers are distributed automatically across the servers in your deployment.

Yes. Conversations are shared within a workspace and update in real time, so a reply typed by one agent appears immediately for everyone else looking at that chat. Each stored message records which staff member sent it, which is what makes per-agent reporting and audit possible.

Yes, in a PostgreSQL database that belongs to your deployment. Messages, chats, contacts and media metadata are mirrored as they arrive so that history survives a re-linked session, and media files are written to object storage in the region that received them.

Yes, through two links that need no work on our side. A webhook forwards every inbound and outbound message to an endpoint you own, and a customer panel can render your CRM's own data next to the conversation, so an agent sees the customer record without leaving the chat.

No. You link the numbers you already use by scanning a QR code from the console, the same way you would link WhatsApp Web. Nothing about the number, its history on the phone, or its contacts changes.

Both models run the same software. The platform is deployed as a set of services — an API, background workers and one or more regional channel engines — against your own PostgreSQL, Redis-compatible cache and object storage, so it can run in your cloud account or be operated for you.