Try Omnifox free 7 days free. No credit card required.
Guides

The WhatsApp Number Belongs to the Company, Not the Rep: How to Take Back Control

When a rep leaves, the chats leave with them. How to move customers to a company-owned number without losing history, using coexistence and the API.

September 06, 2026
The WhatsApp Number Belongs to the Company, Not the Rep: How to Take Back Control
In this article

    The "sales WhatsApp" at many small companies is a number a rep registered on their own phone three years ago, printed on their business cards, and shared with every customer they have ever spoken to. It works until the rep hands in their notice. Then the awkward truth surfaces: the WhatsApp number belongs to the company only in theory. In practice it belongs to whoever holds the phone, and so do the chats, the contacts and the relationships.

    This is not a story about bad reps. It is structural: WhatsApp ties a number to a device and a person, and nothing in the free app lets a business administer that number the way it administers an email account. The fix is moving the number to something the company controls, without losing the history that makes it valuable. Below is a phased plan companies in the US and UK have used to take the number back without drama, including what to do if the rep has already left. Where employment or data protection law comes into it, we keep it general; check with your own counsel.

    Why this happens, and why it is not obvious until it hurts

    WhatsApp's model is one number, one phone, one person. The Business app adds a profile and a catalog, not administration. So when a company "assigns" WhatsApp to a rep, the number is registered by the rep, often with their own SIM; the two-step verification PIN is known only to them; backups go to their personal cloud account; and customers save the number under the rep's name. None of that is visible from the company's side. The number appears to belong to the business because the profile says so. It does not.

    Phase 1: inventory what you actually have

    Before moving anything, write down the real situation for each number used with customers:

    Question Why it matters
    Whose name is the SIM contract in? Whether the company can keep the number at all
    Whose phone is it on, and is it BYOD? Whether you can require the app to be removed
    Who knows the 2FA PIN? Needed to re-register the number on the API
    Where do backups go? Chats may exist only in a personal cloud account
    Which Meta account is linked? Business tools may be tied to a personal login
    How many active chats in the last six months? How much history you stand to lose
    Is the number printed anywhere? Cards, signage, ads, website, Google Business Profile

    You will usually find that the most important number is the one with the least documentation. Move that one first.

    Phase 2: set up a company-owned number on the API

    The goal is a number registered to the company's verified Meta business portfolio, connected to the official WhatsApp Business Platform, and used by the team from a shared inbox where every login is individual and every conversation is logged. Two starting points:

    • Keep the existing number. If the SIM is the company's (or the rep agrees to transfer it) and the number has no ban history, connect it via WhatsApp coexistence. The number keeps working in the WhatsApp Business app and, at the same time, in the API. During pairing, which Meta runs in its own flow, up to six months of chats and contacts are imported.
    • Use a new company number. Cleaner if the existing number is contractually the rep's, has a strike with Meta, or the PIN is lost. You start empty and migrate customers gradually.

    One trade-off: in coexistence mode, WhatsApp voice calls are not handled inside Omnifox; if they matter, plan to migrate fully to the API later. Either way, before connecting you need a verified portfolio, an approved display name and a company payment method; the checklist before you connect a WhatsApp API number covers those.

    Phase 3: tell customers and migrate them gradually

    Customers care that the person they trust still answers, so the notice should come from the rep, sound like the rep, and make the change feel like an upgrade. If you kept the number through coexistence, most customers need no notice at all. If you introduced a new company number, send this from the old one, inside active conversations (within the 24-hour window) or as an approved template for the rest:

    Hi Karen, it's James at Brightwater Kitchens. Quick heads-up: from next week I'll be answering from our company WhatsApp, +44 20 xxxx xxxx, so you can reach me or a colleague whenever I'm out on site. Save the number and just say hi there when you get a chance. Nothing else changes.

    Then, over three to six weeks:

    1. Update the touchpoints (website, Google Business Profile, ads, email signatures, cards).
    2. Set the old number's away message to point to the company number.
    3. Keep the old number reachable, but reply from the new one.
    4. Track how many active conversations have moved and follow up with the rest.
    5. Retire the old number from business use, or keep it as a redirect only.

    Phase 4: put an internal policy in place

    Keep the number the company's with a short written policy, which also matters for data protection:

    • The company administers the number. Portfolio, SIM contract, 2FA PIN and billing are held by the company, documented, and not tied to one person's login.
    • Access is per user. Each rep logs in to the shared inbox with their own account; access is granted and revoked centrally.
    • Conversations are logged. Every message is attributed and stored against the contact in the CRM, not on a device.
    • Personal WhatsApp is not used with customers. State it plainly, and give reps a good alternative.
    • Consent is recorded. Marketing goes only to contacts with a recorded opt-in. TCPA in the US and UK GDPR and PECR in the UK apply to WhatsApp as to SMS in general terms; confirm with your counsel.

    With Omnifox the practical side is already in place: multiple users on one WhatsApp number, individual logins, automatic assignment, and a CRM record per contact with the history from every channel.

    Phase 5: what to do if the rep already left

    This is the hard case, and it is common. The rep is gone, the phone went with them, and customers keep texting a number you do not control.

    • Ask, politely and in writing, for the number or the SIM. Many reps cooperate when it is framed as handing over customer contacts. Whether you can require it depends on the contract and whose name the SIM is in; check with counsel before making it a demand.
    • Do not try to register the number yourself. If the SIM is not yours, attempting it may lock the number for both of you.
    • Set up the company number now. Every day without one, customers keep building a relationship with the ex-rep.
    • Reach customers through the channels you still have (email, SMS, Instagram, website) with a short notice that the company's WhatsApp has changed.
    • Rebuild the contact list from CRM notes, email threads and invoices.
    • Fix the structure (Phase 4) for every rep who remains.

    Frequently asked questions

    Can a company legally take a WhatsApp number from an employee?

    It depends on whose name the SIM contract is in and what the employment agreement says. Get advice from your counsel before making demands. The practical route is to move customers to a company-owned number rather than fight over the old one.

    Will customers lose the chat history if we move the number?

    Not if you keep the same number through coexistence: up to six months of chats and contacts are imported when the number is paired with the API. If you switch to a new number, the history stays on the old phone, so export what you need first.

    Can the rep keep using WhatsApp on their phone after the change?

    With coexistence, yes: the number stays in the WhatsApp Business app and is also connected to the API, so the team answers from the shared inbox while the phone keeps working. WhatsApp voice calls are not handled in the platform in that mode.

    How do we stop reps from using personal WhatsApp with customers?

    Give them a better tool and a clear rule. A shared inbox with automatic assignment and the full customer history is easier than a personal phone, and a one-page policy makes the expectation explicit.

    Take the number back before you need to

    The best time to move the sales WhatsApp to a company-owned number is before anyone resigns. Coexistence lets you do it without changing the number or losing six months of history, and a shared inbox with per-user access keeps it the company's afterwards. Omnifox handles both. Start a 7-day free trial and run Phase 1 this week.

    Ready to try it in your business?

    Bring WhatsApp, Instagram, Messenger, email and calls into one inbox, and let AI handle the first reply. Set it up today.

    7 days free. No credit card required.

    Comments (0)

    No comments yet. Be the first to share your thoughts.

    Leave a comment

    Your email is never published. Comments are moderated before appearing.

    Markdown supported. HTML is stripped.

    Read more

    Message us on WhatsApp