A supplier dispute lands on the desk of the person who handles accounts. The other side says the agreed price was different from what showed up on the invoice, and they want it settled one way or the other. The proof is a thread from eight months back, the one where the revised quote was sent and confirmed. Legal asks for it to be kept, just in case this goes further. Nobody in sales or finance has any reason to remember one thread among thousands.
A fortnight later, IT runs the mailbox cleanup it runs every quarter, clearing anything past a year old to keep the server light. The rule does not know a dispute exists. It only knows a date.
Nobody finds out whether that thread survived the cleanup until the day someone outside the company asks to see it.
Why we build it this way
A hold is a promise that one thread, from this point, will not be deleted. Most companies keep that promise in the wrong place: a compliance tool or a spreadsheet, separate from the mail server, that has to be told, mailbox by mailbox, which message now matters. It is only as current as the last person who remembered to update it, and the cleanup rule running on the actual mail has never heard of it.
The usual fix is to train people to flag things. That fails the way every manual control fails — it depends on someone under pressure remembering a word, "hold," they may never have used before.
A hold that lives somewhere other than the mail itself is an instruction, not a guarantee.
We think a hold only means something if it is enforced at the same place that already reads every thread to answer questions about it. Workspace's one index already knows which thread exists, who sent it and what refers to it. Teaching that same place to refuse a delete on a marked thread costs nothing extra. Building a second system to watch the first one is where the gap always starts.
How it works, roughly
When a thread or a file needs to be preserved — a dispute, an audit, a notice from outside the company — a named person marks it inside Workspace. From that point:
- The thread and anything attached to it stop being eligible for the routine cleanup that clears everything else on schedule
- Nobody can delete it, including whoever placed the hold, until the hold itself is lifted by a person who is identified
- Lifting a hold is recorded the same way every other action in Workspace already is, so there is a record of who released it and when
If someone tries to delete a held thread anyway, they are told why it refuses, rather than left wondering if the delete button is broken.
A year of this is an inbox where nothing that mattered to a dispute or an audit disappeared because a cleanup rule did not know better. What gets held is still a person's decision, start to finish — someone names the thread, someone later releases it — and the record of both stays on the box in your own building, not in a vendor's support ticket.
Read about Varahi Workspace →