WhatsApp Business number ownership: who keeps the chats when someone leaves

Whoever controls the SIM card and the account login owns the number in practice, and that is rarely the company. This is the uncomfortable core of WhatsApp Business number ownership: the thing your customers message all day is anchored to a physical SIM and a verification code, not to a company record.

WhatsApp ties one account to one phone number, confirmed by a code sent to that SIM. There is no admin sitting above the account, no company directory, no "owner" field a manager can reassign. If the number is registered on a rep's personal phone with their personal SIM, then for every practical purpose it is theirs.

That gap between who pays for the relationship and who controls the account is where the trouble starts. The company thinks it owns the number because it owns the customers. WhatsApp only knows the SIM and the login.

WhatsApp Business number ownership means control of two things: the SIM that receives the verification code, and the device session that is logged in. Hold both and you hold the number. Hold neither and you are locked out, no matter whose customers are on the other end.

It helps to separate three layers that people blur together. There is the phone number itself, which the mobile carrier issues. There is the WhatsApp account registered to that number. And there is the chat history, which lives on the device and in that account's backup.

A company can pay the phone bill and still control none of the layers that matter. If a salesperson registered the WhatsApp Business app on their own handset, the account and the chat backup sit with them. Paying for the SIM does not give you the login, and the login is what reassigns nothing automatically.

If the number is a personal account on their phone, they keep the number, the full chat history, and every live conversation. This is the personal-device lock-in that founders discover at the worst possible moment, usually the week a top rep resigns.

Picture the common setup. A four-to-eight person company starts on the founder's or a rep's personal WhatsApp. Leads, order threads, and follow-ups all land there. The team forwards screenshots into a group chat to stay in the loop. It works, until the person holding the phone is gone.

When they leave, the conversations leave with the device. The new rep cannot see what was promised last week. The customer keeps messaging a number that now reaches an ex-employee. The company cannot recover the thread, cannot answer in context, and in the worst case cannot reach the contact at all. Nothing about paying the salary or the phone bill changes that.

This is not a rare edge case. It is one of the most predictable failures of running a business on a personal handset, and it is the reason "conversations stay with the team, not a person" is worth taking literally.

Recovery depends entirely on whether you control the account, and from the outside, you usually do not. There is no support ticket that hands a company someone else's logged-in WhatsApp account, so it pays to be honest about what is and is not retrievable.

Chat history is the hardest part. WhatsApp backups are encrypted and tied to the account holder's own cloud, so a leaving employee's WhatsApp Business backup typically sits in their personal Google or Apple account, not anywhere the company can reach. Moving an account between phones relies on the chat transfer feature, which only works for the person who is already signed in. Both paths assume you are the account holder. If you are not, they are closed.

So the realistic answer is blunt. If the account is personal and the person will not cooperate, assume the history is gone and the number may be too. The fix is not recovery after the fact. It is never letting the number live on a personal account in the first place.

You can change the number or move it to a new phone, but only if you still control the account, and the WhatsApp Business app has no concept of company-level ownership transfer. The controls exist for the account holder, not for an employer trying to take a number back.

Inside the app, the account holder can move the number to a new phone or run the change-number flow to swap in a different SIM. Both actions need an active, logged-in session on the original account. There is no button a manager can press to reassign an account they were never signed in to.

This is the trap with a "company WhatsApp number" that is really a personal account in disguise. It looks like a business asset on the org chart. It behaves like the personal property of whoever holds the login. If you want to transfer a WhatsApp Business number cleanly when staff change, the account has to belong to the business from day one, which is exactly what the next layer is for.

On the WhatsApp Business Platform, the number registers to a WhatsApp Business Account your company owns in Meta Business Manager, which moves number ownership off the personal handset for good. This is the buyer-education point most teams miss until lock-in bites: the app and the platform are two different ownership models.

The platform, also called the Cloud API, is built around accounts a business administers. You can migrate the number from the app onto a WhatsApp Business Account, and from there it lives inside a Business Manager that the company controls and assigns access to. When a number was set up through a partner, Meta even documents how to transfer ownership of the WhatsApp Business Account between businesses. The unit of control becomes the business account, not a SIM in someone's pocket.

We have to be clear about the limits. None of this lets you seize an account someone else legitimately controls, and Clapvo does not control Meta or its enforcement. What the platform changes is the starting point: set the number up under a business account you own, and a resignation stops being an ownership crisis. For the full breakdown of when to use the app versus the platform, see our app vs API guide.

A shared workspace solves the part the platform alone does not: keeping the live conversations, notes, and ownership visible to the whole team instead of trapped in one logged-in session. Owning the account in Business Manager is necessary. It is not, by itself, a way for five people to work the same number without stepping on each other.

This is the limit of the WhatsApp Business app even before anyone quits. It was built for one business identity, not a team sharing a session, which is why trying to run three or four agents off one number gets messy fast. We walk through that in detail in the post on multiple users on one number.

Clapvo sits on top of the business-owned number and turns it into a workspace. The whole team works one shared inbox in the browser, with assignment, private notes, and message templates, so the conversation history belongs to the workspace and not to whoever happened to send the last reply. Chats no longer sit on a personal phone. When a rep leaves, their open threads are already visible to the manager and reassignable to the next person, the same way a team inbox handles every other handoff.

You can cut most of the lock-in risk in a few concrete steps, and none of them require waiting for a crisis. The goal is simple: get the number off personal accounts and into something the business controls.

First, stop registering business numbers on personal SIMs and personal handsets. Treat any number that earns revenue as a company asset from the start. Second, move the number onto a business-owned account, either the WhatsApp Business Platform directly or a workspace that runs on it, so control lives in Business Manager rather than on a device. Third, put the team on a shared inbox with role based permissions, so no single person is the only one who can see a customer thread. Fourth, decide offboarding before you need it, so you know who reassigns conversations and revokes access the day someone gives notice.

To be straight about it, this reduces risk. It does not give you a magic recovery button for a number that is already gone, and it does not give anyone control over Meta's decisions. What it does is make the next resignation a routine handoff instead of a lost-customer event.

Right now, if the number lives on a personal phone, the rep owns it, whatever the org chart says. Ownership follows the SIM and the login, not the payroll, and that is the whole problem in one sentence.

The way to change the answer is to change where the number lives. Put it on a business-owned account and keep the conversations in a workspace the team shares, and ownership finally matches reality: the company holds the number, the team holds the history, and one person walking out the door does not take your customers with them.

Clapvo is built for exactly that. It prices per WhatsApp connection, not per seat: $15 a month (or R$89), including one WhatsApp connection and five team members, with a seven-day free trial and no credit card required. You can see what is included on the Clapvo features page and the full plan on the pricing page.