Google Drive backup
Your conversations, in your own Google Drive.
Connect the workspace's Drive once and the conversations you choose are archived into it as dated transcripts and files — history first, then everything new, about a minute after it arrives.
The record of what you agreed is on a phone you do not own.
Everything the business promised this year is in a chat app on somebody's handset. They leave, or drop it, or reinstall — and the only account of what was said goes with them. WhatsApp's own backup does not help: it is personal, it belongs to one Google account, and it restores to one phone. It was never meant to be a company archive.
One Drive for the workspace
An owner or admin connects a single Google account and the whole workspace archives into it. Not one per person — an archive that belongs to whoever set it up is an archive that leaves when they do.
It can only see the folder it made
The connection asks for access to files it creates and nothing else. Your documents, your photos, everything already in that Drive: invisible to it. The trade is that it makes its own folder rather than filing into one of yours, because it genuinely cannot see yours to offer you the choice.
A folder per chat, a file per day
Each conversation gets a folder, with a folder per year and month inside it and a plain-text transcript for every day that had messages. Attachments sit in a media folder beside them. It reads like an archive because it is shaped like one.
It keeps up by itself
A sweep asks which conversations have moved since they were last written and archives those, about a minute behind. There is nothing to run, nothing to schedule, and no export anybody has to remember.
Per chat, and per kind
Archiving is switched on one conversation at a time, not for everything at once, and you choose what travels: text, photos, video, voice notes, documents, stickers. Old history is backfilled with a percentage, so a three-year-old chat tells you how far it has got.
When you would use it
- A salesperson leaving with three years of customer conversation on their handset.
- An auditor, an insurer or a client asking for the record of what was agreed.
- A dispute where the evidence is a chat nobody can produce any more.
- Wanting the company's own copy of its own conversations, somewhere it controls.
See it running
Six seconds, showing this one thing.
Questions people ask
Which plan is this on?
Every plan — it is not a Pro feature and not a paid add-on. What it does need is permission: connecting the Drive and switching a conversation on are export-level actions, so an owner or admin does them and agents cannot.
Can it read the rest of my Drive?
No, and that is a permission rather than a promise. The connection holds per-file access to files it created, which is the narrowest scope Google offers for writing. It cannot list, open or change anything it did not put there — so the honest answer to "what can this integration see?" is "the folder it made".
What is actually in a transcript?
Plain text, one line per message: a timestamp, an arrow for the direction, who wrote it and what they said, with any attachment named inline. Internal notes are in there too, marked with a bullet — an archive of a conversation that left out half of it would not be worth keeping, so archive a chat only if you are content for the whole of it to be written down.
What happens if I disconnect it?
Archiving stops, and the conversations say why rather than going quiet. Disconnecting also forgets what had already been uploaded, so connecting a different Google account rebuilds the whole archive there instead of resuming from that day and leaving the history missing.
Does it re-upload everything every time?
No. Yesterday's file is finished the moment the day ends and is never rewritten, and an attachment is uploaded once and remembered. The only transcript any pass touches is today's, which is small.