For businesses running more than one WhatsApp number
All your WhatsApp numbers in one shared team inbox
MultiChats is a shared team inbox for businesses that run several WhatsApp numbers. It connects every number to one console, gives each agent only the accounts they are assigned, and mirrors the whole conversation history into a database you control.
Runs on your own PostgreSQL, cache and object storage — the conversation data never has to leave your infrastructure.
The problem
Three numbers, three phones, no record
A business that grows past one WhatsApp number usually solves it with more handsets. It works until it doesn't: nobody knows who replied, history lives on a device that walks out with an employee, and none of it reaches the systems that run the business.
Sharing one phone doesn't scale
Two people cannot answer at once, and WhatsApp Web mirrors a single device — so the phone becomes the bottleneck and the single point of failure.
History belongs to the handset
Replace the phone, lose the thread. Nothing is searchable across numbers, and an audit means scrolling somebody's device.
Your systems never see it
Orders, receipts and complaints arrive in a chat app your CRM cannot read, so somebody re-types them — or nobody does.
What it does
One console for every conversation
The console is the product; the API and the webhook are how it fits the rest of your stack.
Every number, one inbox
Connect as many WhatsApp numbers as you run. Each one is linked by scanning a QR code from the console, then all of their conversations land in the same list — no switching phones, no shared handset on a desk.
A team, not a login
Workspaces hold your numbers and your staff. Admins see everything in the workspace; a member sees only the accounts assigned to them. Every reply is attributed to the person who sent it.
History that stays yours
Messages, contacts, groups and media are mirrored into your own PostgreSQL database as they arrive. Conversations remain searchable after a phone is replaced or a session is re-linked.
A webhook for your backend
Every inbound message and every reply your team sends is forwarded to an endpoint you control, so your CRM, bookkeeping or bot logic reacts to conversations without polling anything.
A REST API for sending
Send text, media, voice notes, locations and contact cards programmatically with an API key. Queued sends are executed by the server that owns the number, and you get a delivery receipt back.
Run it close to your numbers
The channel engines are regional: a number registered in one country can be driven from a server in that region, while the console and the data stay in one place.
How it works
Three steps to a shared inbox
- 1
Link a number
Open the console, add an account and scan the QR code with the phone that owns the number — the same handshake as WhatsApp Web. The session stays linked; nobody has to keep a browser tab open.
- 2
Invite the team
Create a workspace, invite staff with a code, and assign each person the numbers they are responsible for. A member only ever sees their own accounts.
- 3
Wire it to your systems
Point the webhook at your backend to receive every message, and use an API key to send from your own code. Both are per-workspace settings, not a support ticket.
Questions
Frequently asked questions
The short answers. Longer ones live on the pages linked from each section.
What is MultiChats?
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.
How is this different from WhatsApp Business or WhatsApp Web?
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.
How many WhatsApp numbers can one team connect?
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.
Can two agents reply to the same conversation?
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.
Does MultiChats store our conversations?
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.
Can it connect to our CRM?
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.
Do we need to change our phone numbers or re-register them?
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.
Is MultiChats self-hosted or a hosted service?
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.
See it with your own numbers
Tell us how many numbers you run and what you need them to reach — we will show you the console and the API on a call.