Perspectives
Personal vs company numbers — pick company numbers, then sync
Personal numbers give you reps you cannot onboard, audit, or offboard. Six reasons to issue company numbers — WhatsApp Business on a virtual SIM — and sync those.
May 27, 2026·6 min read
Sales Lead, TimelinesAI·May 27, 2026·6 min read
What's wrong with running sales on personal numbers?
Three things, in order of how painful they are when you discover them. First, you cannot offboard a rep cleanly — the account is in their name, the chats are on their phone, and on the day they leave they take the customer relationship with them. Second, every rep with a personal number connected to a shared admin tool has the same complaint: "my manager sees my plumber, my wife, my kid's school." That's why agents refuse to connect, and why 30–50% of seats on a personal-number setup quietly never get used. Third, when you decide to add marketing throughput — broadcasts, templates, opt-in flows — the WhatsApp Business API migration requires a number the company controls. Personal numbers shut that door before you reach it.
Company numbers fix all three. The reasons below are the operational details.
How do personal and company numbers compare?
| Property | Personal number | Company number (WhatsApp Business on virtual SIM/eSIM) |
|---|---|---|
| Ownership | The rep | The company |
| Provisioning cost | Free | ~$2–$20/number/month (Zadarma, Seamasty, local eSIM) |
| Hardware needed | Rep's phone | Rep's phone (Business app runs alongside Messenger) |
| Offboarding when rep leaves | Customers go with them | Number stays, hand to next rep |
| Privacy for the rep | Bad (admin sees personal chats) | Good (personal life lives on Messenger account) |
| Trust signal at first contact | Personal profile | Business profile (name, hours, catalog) |
| CRM sync via TimelinesAI / similar | Yes | Yes |
| Future migration to WABA | Not possible cleanly | Routine |
| WhatsApp anti-spam risk on outbound bursts | High | Same anti-spam floor, but company is the one warming the number |
Reason 1 — Aren't company numbers expensive?
No. WhatsApp Business is a free app. Virtual numbers from Zadarma, Seamasty, CloudTalk, or a local eSIM provider run a few dollars a month. For a 20-rep team that's a hundred dollars or so per month of numbering cost — the same order of magnitude as one mid-tier SaaS seat. The one thing not to do is provision Twilio numbers for WhatsApp registration; in our experience Twilio numbers get instantly banned when you try to register them on WhatsApp. Pick a VoIP provider that has explicit WhatsApp support, or buy local SIM/eSIM.
Reason 2 — Do reps need a second phone?
No. Any modern Android or iOS phone runs WhatsApp Messenger and WhatsApp Business side by side. Two icons, two accounts, two phone numbers, one device. Personal life lives in the Messenger account on the rep's personal SIM. Work life lives in the Business account on the company-issued number. The rep does not pay for a second phone, and they do not have to surrender their personal account to the company.
Reason 3 — What happens when a rep leaves on a personal-number setup?
They leave with the customers. The WhatsApp account, the number, the chat history, the unread threads — all of it lives on the rep's personal phone and personal Meta account. You cannot legally compel them to delete chats. You cannot transfer the account. You can ask nicely and hope, or you can hire a lawyer. As Ishay put it on a February 2026 sales call: "Личные номера — это прайвеси, это проблемы, вы не можете потребовать человека удалить, у вас нет контроля." Translation — personal numbers are a privacy issue, you cannot demand the person delete anything, you have no control.
Personal numbers are a privacy issue. You cannot demand the person delete anything. You have no control.
With company numbers the playbook is simple. Day one of new rep: hand them the number. Day last of old rep: reset the WhatsApp account on that number, hand it to the next person, customer keeps the same thread.
Reason 4 — Why do reps refuse to connect personal numbers anyway?
Because their admin sees the plumber, the wife, the kid's school. Number hiding inside a tool like TimelinesAI works at the workspace level, but at the team level the manager who reviews their reps' WhatsApp performance is also looking at their reps' personal lives. We've been asked for a "role without chat access" feature continuously since early 2025, and so has every competitor — nobody has shipped it. (We cover the gap honestly in The role-without-chat-access feature nobody has shipped.) Until that feature exists, the cleanest fix is upstream: don't have personal chats on the number you sync.
Reason 5 — Does a company WhatsApp Business number actually look more professional?
Yes — and the gap is real in markets where buyers are wary of unknown numbers. WhatsApp Business gives you a verified business profile with company name, description, hours, website, address, and a catalog. The first message a buyer sees doesn't come from "Roman" — it comes from "Acme Sales (Lisbon)" with a logo and a category. In Turkey, UAE, LatAm, and Spain that signal converts. (I personally run my own outreach off a UK WhatsApp number rather than my Ukrainian personal one, because country-code signaling at first contact is half the trust battle for international sales.)
Reason 6 — What about migrating to the WhatsApp Business API later?
When your marketing motion outgrows 1-to-1 conversations and you need broadcasts, template approvals, and 24-hour conversation windows, you'll migrate the brand's marketing surface to the WhatsApp Business API. That migration requires the number to be company-owned and verifiable through your Meta Business Manager. Personal numbers cannot be migrated to WABA cleanly — Meta requires the migrating phone number to be free of an existing WhatsApp account that's not yours. Company-issued numbers make this routine; personal numbers make it a year-long unwind.
So the migration matrix looks like this: personal numbers + sync = today only. Company numbers + sync = today and tomorrow.
What this means for your setup
If you're standing up a new WhatsApp sales motion, skip the personal-number step entirely. Provision company numbers from your local VoIP / eSIM provider, install WhatsApp Business on each rep's phone, and sync those numbers to your CRM through a gateway like TimelinesAI (or any of the alternatives). If you already have reps running on personal numbers, plan a 30-day swap window: provision new company numbers, run the old and new in parallel, message each customer once from the new number ("I'm reachable on this number going forward — same person"), and retire the old. The customer keeps the conversation. The company keeps the number.
For why personal-style (QR-linked) numbers are still the right architecture for sales conversations — versus the WhatsApp Business API — see Personal numbers vs WhatsApp Business API — pick personal if you sell. For why QR-linked is the right way to connect those numbers at all, see QR vs Coexistence — pick QR. Cluster hub: /perspectives/topic/personal-numbers-privacy-waba/.
More perspectives
Personal numbers vs WhatsApp Business API — pick personal if you sell
Sales is 1-to-1 conversation. Templates, 24-hour windows, and per-message pricing make WABA the wrong tool for reps. Use WABA only for marketing and service.
Cyril Zakirov
QR vs WhatsApp Coexistence — pick QR
Coexistence has no CRM sync, no groups, no calls, no attachments, no broadcasting, no OBA — 14 reasons QR-linked WhatsApp wins for any sales team.
Cyril Zakirov
The role-without-chat-access feature nobody has shipped — and why your reps won't connect
Across every WhatsApp-CRM tool, including ours, no vendor has shipped manager visibility without chat-content access. A meaningful share of seats stay silently unconnected.
Cyril Zakirov