They are three layers, not three competing products. The WhatsApp Business API is how software connects to WhatsApp. A shared inbox lets several people work from one chat list. A WhatsApp CRM keeps each conversation as a record with an owner, a history and an outcome. Many tools sell all three under one name, which is why comparisons confuse.
The three, defined
| Layer | What it is | What it does not do on its own |
|---|---|---|
| WhatsApp Business API (Cloud API) | Meta’s official connection that lets a platform send and receive messages for your number | Give your team a screen, assign chats or track anything |
| Shared / team inbox | One chat list several people can work from, usually with assignment and labels | Enforce ownership, count working-hours deadlines or record outcomes |
| WhatsApp CRM | A system that stores contacts, conversations, tasks and outcomes, connected to WhatsApp | Work without the API underneath it |
Everything beyond the free WhatsApp Business app needs the API underneath. The app supports one primary phone plus up to four linked devices, with labels but no assignment or response clock. We cover that in where a shared number breaks.
Three questions that decide it
Instead of comparing feature lists, answer these about your own business:
- 01Who owns an enquiry? If “whoever answers first” is fine, a shared inbox is enough. If one named person must be responsible, you need ownership enforced by access, not just a label.
- 02What is the clock? If you promise a first reply, you need a deadline counted in working hours. Counting wall-clock time or restarting at reopening gives the wrong answer; the response time calculator shows by how much.
- 03What must be on record? If you need to show what was quoted, who handled it and how it ended, you need a CRM-style record, not chat history.
Which one for which situation
| Your situation | What you need | Watch for |
|---|---|---|
| One or two people, low volume, no promises on response time | The free Business app | Everyone sees every chat; nothing assigns it |
| A team answering one number, speed matters, no formal record | API with a shared inbox | Assignment that is advisory; no working-hours clock |
| Quote-based or multi-day work where one person must own each enquiry | API with a CRM that enforces ownership and deadlines | Whether access really follows ownership |
| Mass broadcasts and a chatbot for simple questions | API with a broadcast and bot platform | Meta’s per-message charges for templates |
Questions to ask any vendor
- 01Can an employee see a chat that is not assigned to them? If yes, ownership is advisory.
- 02How is the first-reply deadline counted? Ask for the Saturday 17:40 example: a 60-minute promise, closing at 18:00, closed Sunday. The fair answer is Monday 09:40.
- 03What does “sent” mean? Staff pressing send, or the provider confirming it went.
- 04Does the AI reply on its own? Decide whether you want that.
- 05Whose WhatsApp account is it? You should hold it, and be able to leave with it.
We built Provixon Connect for the third situation in the table: staffed, quote-based work where every enquiry needs an owner, a clock and an outcome. It is in pilot build. If you only need a shared inbox, other tools may suit you better, and we would rather say so.