Seeing your team's WhatsApp without the Business API

Ask most vendors how to get a record of your team’s WhatsApp and the answer is a migration: move your numbers to the WhatsApp Business API, route conversations through a new inbox, retrain the team. Sometimes that is the right call. But it answers a question you did not ask. You wanted an archive, and you were offered a new way of working.

What the API route actually asks of you

The Business API is Meta’s official channel, and official matters: it is the version with a formal contract behind it. But it is built around programmatic messaging, and adopting it changes how your team works. The number moves off the phone app: conversations live in whatever inbox or CRM sits on the API, reps answer from that tool instead of from WhatsApp, and the way your customers’ messages reach a human is now a product decision made by whichever vendor you chose. For a support operation running templated notifications at volume, that trade is often worth it. For 8 reps who sell in ordinary chats from a handset, it means retraining the team and changing the thing that was working, the part your customers chose.

The companion-device route

There is a second way, and you already use it: it is how WhatsApp Web works. A company-owned number can register an additional device, and that device receives the conversation like any other. WAOversight links numbers exactly this way: one QR scan per number, about a minute each, nothing installed on any phone, no number change, no new inbox. The team keeps working in WhatsApp; the archive fills up behind them from the moment the link is made.

What lands in the archive is the part worth being picky about. Every message is written to an append-only log before it is acknowledged, so a crash cannot lose one. Deleted messages keep their original text with both timestamps, edited messages keep every version, and each number’s records form a hash chain you can verify, because a record that can be quietly rewritten is a draft, not an archive. The security page sets out how that record is protected, who can read what, and why every read of it is itself on the record.

The honest tradeoffs

The companion-device connection is not the official API, and you should hear the costs from the vendor rather than discover them:

• Sessions can drop. A companion link is a live session, and a phone that stays offline too long degrades it. Relinking is a QR scan, but the gap is real, which is why capture lag and session uptime should be published numbers, not adjectives. We publish ours monthly, per number, with the measurement method published in full.
• The ban risk is not zero. An unofficial connection carries a risk the official API does not, and any vendor who tells you it is zero has told you something about themselves. It is small, it is managed, and it is disclosed. Our reliability page covers it in detail, because it is the page to read before trusting any other page.
• Capture starts at linking. History from before the link is not in the archive. The API route has the same property; nobody’s archive reaches back in time.

And the tradeoff in the other direction: if you are in a formally regulated industry with supervision requirements, financial services record-keeping for instance, the enterprise compliance archivers built on official channels exist for that, and you should buy one. This approach is built for the much larger group of teams whose problem is operational, not regulatory: they sell on plain WhatsApp, customers like it that way, and until now the choice was a disruptive migration or no record at all.

How to decide

One question does most of the work: would moving your team off the WhatsApp phone app cost you something? If no, and conversations are already structured, high-volume and template-shaped, the API route gives you official standing and you should take it. If yes, and your reps sell in ordinary chats and your customers message a person rather than a queue, then companion-device archiving gets you the record without touching the workflow, and the diligence question becomes reliability: ask for the published uptime, the published capture lag, and what happens to a message when a session drops. A vendor with good answers will have written them down before you asked.