Your business WhatsApp is sitting on someone’s phone
The problem is not that you lack software. The problem is that the number your business runs on is registered to one device, held by one person, and nobody else can see what happens on it. This page compares the two ways to fix that, including the parts of the official route that will annoy you.
- Who answered last night, and who was never answered at all — today you cannot tell
- When that person leaves, the conversations and the customer relationships leave too
- Official: stable and supported, but templates and a 24 hour window
- Unofficial: unrestricted, but it runs on a handset that has to stay switched on
Short answer
The number your business runs on is registered to one handset, held by one person, and nobody else can see what happens on it. That is the actual problem, and it is an ownership problem before it is a software problem.
There are two ways to resolve it. An official connection moves the number onto Meta’s infrastructure, and the whole team works from one inbox. An unofficial connection leaves the number on a physical handset and attaches a system to it from the outside. The first one constrains you with published rules. The second constrains you with almost nothing, and that is precisely its problem.
What is actually happening today
You do not need software to see this. You need five questions about your own business:
Who answered the customer who wrote at eight in the evening? How many enquiries came in this week, and how many were never answered at all? If the person holding the phone is away tomorrow morning, who picks up the conversations they were in the middle of? If they leave the company, what is left with you of the relationships they built on that number? And a customer who never got a reply — how would you ever know they were there?
In most businesses there is no answer to any of them, and it is not because the team is careless. It is because the number lives on a device, and the device belongs to a person. A customer who is not answered does not complain. They go somewhere else, and you find out a month later, if at all, looking at a sales figure you cannot explain.
That is the problem. The two routes below are two ways of solving it, and they do not leave you carrying the same risk.
The two ways to connect a business number to a team
Compared on what actually differs in daily operation.
| Official (Meta Cloud API) | Unofficial (handset + SIM) | |
|---|---|---|
| What it actually runs on | Meta’s infrastructure | A physical handset that has to stay powered and connected |
| If the phone is dropped, runs flat, or loses signal | Not applicable — there is no handset in the path | Your business messaging stops until somebody attends to it |
| Business-initiated messages | Through templates approved in advance | Unrestricted, no approval |
| Replying after the customer writes | Free-form for 24 hours | Free-form always |
| Where the team works | In the system, not the WhatsApp app | In the system, not the WhatsApp app |
| Relationship to the official API | It is the official API, documented by Meta | Not the official API — its own vendors describe it that way |
| Support path when something breaks | Documented platform, published rules | Whoever supplied the handset |
WhatsApp’s Business Terms reserve the right to “limit, throttle, suspend, or terminate Company’s account”, and add that a terminated company may not open another WhatsApp business account without express written permission. That is WhatsApp’s own document, governing the Business Services.
What the official connection actually costs you
The official route is not free in terms of flexibility, and it is better to know this before rather than after:
- ▲A business-initiated message requires a template approved in advance. You cannot simply write to a customer whatever you want, whenever you want.
- ▲The 24 hour window. Once the customer writes, you can reply free-form for 24 hours. After that you are back to templates.
- ▲A new template goes through approval. It is not instant.
- ▲The team works from the system, not from the WhatsApp app. Anyone used to replying from the phone changes habit.
The question is not which is more convenient today
The unofficial connection is more convenient. That is not in dispute — no templates, no window, no approvals. Measured over the first month, it wins.
The question is what you are building on. That number is the asset. The customers are attached to it, the history sits in it, and the trust in it was built over years. An unofficial connection stakes that asset on a physical handset in a drawer and on a relationship with WhatsApp that is not a documented one.
If your business intends to still be here in three years, the convenience of the first month is not the parameter you are choosing on.
Questions people ask before they decide
Do I lose my existing number?+
No. Coexistence connects your existing number without giving up the WhatsApp Business app, and syncs chat history and contacts across.
We already run an unofficial system. What now?+
You can move. The first thing to establish is what state the number is in today and what connecting it officially requires.
What is the difference between the WhatsApp Business app and the API?+
Three ways to run one number, compared on devices, history, groups, limits and cost.
Can more than one person answer without any of this?+
Up to a point. The free app supports linked devices, and that is genuinely enough for some teams.
Sources, checked June 2026
Sources
The WhatsApp Business Terms govern the Business Services and Cloud API, and are quoted here for what they say.
Checked on 2026-08-24
Who wrote this
marv.Inbox team
Product and support team, marv.Inbox
We build marv.Inbox and we run our own customer conversations inside it, on the same WhatsApp number the buttons on this page open.
Compare it live, not on a feature grid
Open the interactive demo and judge ownership, SLA timers, and handoff for yourself before you shortlist.